Monday, 2025-02-03

*** mhen_ is now known as mhen03:00
xek#startmeeting barbican15:00
opendevmeetMeeting started Mon Feb  3 15:00:53 2025 UTC and is due to finish in 60 minutes.  The chair is xek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'barbican'15:00
xek#topic Roll Call15:01
rajivHeyy15:01
xekCourtesy ping for dmendiza[m] ade_lee d34dh0r53 Luzi tosky tobias-urdin jjung mharley lpiwowar15:01
xeko/15:01
xekAs usual our agenda can be found here:15:01
xek    #link https://etherpad.openstack.org/p/barbican-weekly-meeting15:01
rajivhope dmendiza[m] would be joining ?15:02
dmendiza[m]🙋15:02
rajiv:) 15:03
xek#topic Review Past Meeting Action Items15:03
xek#link https://meetings.opendev.org/meetings/barbican/2025/barbican.2025-01-27-15.08.html15:03
xekThere were no action items15:03
xek#topic Liaison Updates15:03
xek#link https://releases.openstack.org/epoxy/schedule.html15:05
xekI see we have an Oslo feature freeze Feb 10 - Feb 1415:05
xekwhich hat bitten us in the past, since castellan is in oslo15:06
xek#topic Open Discussion15:07
rajivHi Doug, i wanted your view on https://bugs.launchpad.net/barbican/+bug/2036506/comments/3415:08
dmendiza[m]looking ...15:09
dmendiza[m]rajiv: looks like they fixed their docs?  But yeah, it's either CKM_AES_CBC or CKM_AES_GCM15:11
dmendiza[m]GCM is preferred 15:11
rajivThales docs were updated after several follow-ups15:12
rajivi wanted to confirm here before proceeding with upgrades in production15:12
rajivsecond, Default was CKM_AES_CBC_PAD, if i change to CKM_AES_KEY_WRAP_KWP, will old keys be impacted ?     Old secrets can still be unwrapped using CKM_AES_CBC_PAD.     New secrets will be wrapped using CKM_AES_KEY_WRAP_KWP.15:12
rajivis the above correct ?15:13
dmendiza[m]I think so ... probably worth testing in a staging environment15:13
rajivi dint have any issues in QA, also the patch was implement > HSM firmware was upgraded > the barbican.conf wasnt upgraded but all operations work well. 15:14
rajivHence do i need to update the barbican.conf before or after upgrading the device firmware ?15:14
dmendiza[m]I would update the device firmware first15:16
rajivokay, to confirm, rollout the patch > update device firmware > deploy updated barbican.conf15:17
rajivapart enabling HSM device logging, is there a way to check the current key mechanisms used by barbican currently ?15:20
dmendiza[m]Barbican will use whatever is in the conf file for new secrets15:21
dmendiza[m]and the metadata from the secret for existing secrets15:21
dmendiza[m]I'm not sure we have any logging in any of the methods though.15:21
dmendiza[m]Could be a good patch to contribute to enable debugging, rajiv 15:21
rajivcool, noted :) do i need to raise a document request for CKM_AES_CBC or CKM_AES_GCM updated in docu ?15:22
rajivlastly, The only point to remember is CKM_AES_CBC and CKM_AES_CBC_PAD must not be used as wrapping mechanism as Luna HSM do not allow them to use as wrapping mechanism in FIPS mode and Barbican don’t support CKM_AES_GCM for wrapping. We have latest release firmware 7.8.7 and  both CKM_AES_CBC and CKM_AES_GCM are supported for Encryption/Decryption So I don’t think so both of them will be deprecated in FIPS mode for encryption/decryption.15:23
dmendiza[m]Yeah, that sounds right.  15:25
rajivthen the below barbican.conf should be good right ?15:25
rajivencryption_mechanism = CKM_AES_GCM hmac_key_type = CKK_GENERIC_SECRET hmac_keygen_mechanism = CKM_GENERIC_SECRET_KEY_GEN hmac_mechanism = CKM_SHA256_HMAC key_wrap_mechanism = CKM_AES_KEY_WRAP_KWP aes_gcm_generate_iv = True15:25
dmendiza[m]lgtm15:26
rajivaes_gcm_generate_iv. should be True, right ?15:27
dmendiza[m]I'm not sure ... I was looking over my notes, and I've tested it with aes_gcm_generate_iv=False15:29
dmendiza[m]What that does is let the HSM auto-generate the IV15:30
dmendiza[m]when set to True it is Barbican that pre-generates the IV15:30
rajivokay, based on the docu :15:30
rajiv# Generate IVs for CKM_AES_GCM mechanism. (boolean value) # Deprecated group/name - [p11_crypto_plugin]/generate_iv aes_gcm_generate_iv=True15:30
rajivhave we confirm kmip support be deprecated ? we are implementing https://github.com/sapcc/PyKMIP/blob/master/kmip/services/server/barbican.py15:35
dmendiza[m]It's untested, and probably won't work15:38
dmendiza[m]so yeah, not currently supported by the core team15:38
rajivthanks for answers :) 15:39
xekGreat :) Let's check the bug list...15:40
xek#topic Bug Review15:40
xekThere were no new bugs reported since our last meeting15:41
xekThat's it for today! See y'all next week!15:41
xek#endmeeting15:41
opendevmeetMeeting ended Mon Feb  3 15:41:40 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
opendevmeetMinutes:        https://meetings.opendev.org/meetings/barbican/2025/barbican.2025-02-03-15.00.html15:41
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/barbican/2025/barbican.2025-02-03-15.00.txt15:41
opendevmeetLog:            https://meetings.opendev.org/meetings/barbican/2025/barbican.2025-02-03-15.00.log.html15:41

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!