← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:07 | mbridge joined #koha | |
| 00:41 | davidnind | gveranis: I've added a comment to the bug - it seems to be working as expected for me for both main and 24.05.00. |
| 01:07 | mbridge joined #koha | |
| 02:07 | mbridge joined #koha | |
| 03:07 | mbridge joined #koha | |
| 04:03 | JBoyer joined #koha | |
| 04:04 | philor joined #koha | |
| 04:07 | mbridge joined #koha | |
| 05:07 | mbridge joined #koha | |
| 05:58 | thibaud_g joined #koha | |
| 06:06 | JBoyer joined #koha | |
| 06:07 | mbridge joined #koha | |
| 06:08 | mbridge | [mattermost] <dcook> @paulderscheid I'm glad I don't have to worry from a core perspective, although I still reckon that it would bypass Koha's per-user authorization system. (This is one of my many pet peeves.) |
| 06:08 | [mattermost] <dcook> @rudy.hinojosa It's not possible to see in the video that it's FIPS compliant. Plus, that's self-certified, rather externally-certified, so it doesn't really explain how it protects personal information. However... from your description, it sounds like it's just leveraging Koha's existing functionality, so I have no complaints about what you're suggesting here. Thanks for clarifying. | |
| 06:12 | [mattermost] <jpahd> Yes, I haven't tested it in depth yet. | |
| 06:12 | [mattermost] <jpahd> So much other stuff to do right now. | |
| 06:39 | thibaud_glt joined #koha | |
| 07:07 | mbridge joined #koha | |
| 07:59 | lds joined #koha | |
| 08:07 | mbridge joined #koha | |
| 09:07 | mbridge joined #koha | |
| 09:51 | JBoyer joined #koha | |
| 10:07 | mbridge joined #koha | |
| 11:07 | mbridge joined #koha | |
| 12:07 | mbridge joined #koha | |
| 12:58 | Dyrcona joined #koha | |
| 13:07 | mbridge joined #koha | |
| 14:07 | mbridge joined #koha | |
| 14:47 | mbridge | [mattermost] <rudy.hinojosa> @dcook Yes sir, you are correct. Once you have the program on hand, you can activate strict FIPS compliance through the group policy object in windows. Then the program has to be thoroughly tested. Any unhandled exceptions will occur, and details will hint that there was an issue using an obsolete cryptographic routine(s) etc. : https://chat.koha-community.or[…]qcrht6o/public?h= |
| 15:07 | mbridge joined #koha | |
| 16:07 | mbridge joined #koha | |
| 17:07 | mbridge joined #koha | |
| 18:07 | mbridge joined #koha | |
| 19:07 | mbridge joined #koha | |
| 20:07 | mbridge joined #koha | |
| 21:07 | mbridge joined #koha | |
| 22:07 | mbridge joined #koha | |
| 23:07 | mbridge joined #koha |
← Previous day | Today | Next day → | Search | Index