OASIS PKCS 11 TC

 View Only

Re: [pkcs11] Minutes PKCS11 TC Meeting of 31-Jan-2024

  • 1.  Re: [pkcs11] Minutes PKCS11 TC Meeting of 31-Jan-2024

    Posted 02-06-2024 03:07
    Dieter, Thank you again for the review of the minutes, Tim has confirmed that the second version that was in the chat was the version he intended not the version in the email. Sorry I missed the chat window while I was trying to take minutes. I have updated the minutes to reflect this email thread. Great catch. Regards Greg == Greg Scott E: greg.scott@cryptsoft.com M: +61 406 255 166 On 6 February 2024 at 11:58:35âam, Tim Hudson ( tjh@cryptsoft.com ) wrote: I changed mechanism->realisation to try to avoid people mistaking it to be a PKCS#11 mechanism. Either works but "realisation" is the change I proposed before making a motion. Tim. On Tue, Feb 6, 2024 at 11:55âAM Greg Scott < greg.scott@cryptsoft.com > wrote: Dieter, Thanks for your review of the minutes. I donât actually recall if I got the first or last revision of that from the chat. It was a very difficult meeting to follow. I think I took the text from Timâs email to the TC at https://www.oasis-open.org/apps/org/workgroup/pkcs11/email/archives/202401/msg00012.html So I have copied him on this to try and get his input before we reflect this back to the wider list and correct the minutes if necessary. Regards Greg == Greg Scott E: greg.scott@cryptsoft.com M: +61 406 255 166 On 5 February 2024 at 7:10:59âpm, Dieter Bong ( dieter.bong@utimaco.com ) wrote: Hi Greg,  Thank you for sharing the minutes.  Wrt. item #3 RNG flag, there was a 2 nd wording in the chat which stated â Implementations should not imply an interpretation about the security properties based on the CKF_HW_SLOT. The flag is intended purely as an indicator that the slot is a physical realisation . How the implementation that offers the physical slot implements mechanisms (software/firmware/hardware) is unrelated to this flag. â instead of â Implementations should not imply an interpretation about the security properties based on the CKF_HW_SLOT. The flag is intended purely as an indicator that the slot is a physical mechanism . How the implementation that offers the physical slot implements mechanisms (software/firmware/hardware) is unrelated to this flag â i.e. âphysical realisationâ vs. âphysical mechanismâ.  I had noted âphysical realisationâ as latest wording. Do you still have access to the chat to verify which wording was most recent?  Thanks, Dieter  From: pkcs11@lists.oasis-open.org < pkcs11@lists.oasis-open.org > On Behalf Of Greg Scott Sent: Friday, February 2, 2024 6:02 AM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] Minutes PKCS11 TC Meeting of 31-Jan-2024   Hi Folks,  I have managed to upload the minutes of the last meeting and they are at https://wiki.oasis-open.org/pkcs11/MeetingMinutes20240131 for review.  The Work Items for PKCS#11 V3.2 have also been updated at https://wiki.oasis-open.org/pkcs11/3.2WorkItems and those items which we approved being moved to PKCS#11 V3.3 have been entered at https://wiki.oasis-open.org/pkcs11/3.3WorkItems  Please let me know if you see something that needs to be corrected.  The next scheduled meeting is now 28-Feb-2024.  Regards, Greg  == Greg Scott E: greg.scott@cryptsoft.com M: +61 406 255 166 Utimaco IS GmbH Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0, www.utimaco.com Seat: Aachen â Registergericht Aachen HRB 18922 VAT ID No.: DE 815 496 496 Managing Directors: Stefan Auerbach, Martin Stamm, Hacan Tiwemark You will find our data protection information for customers and business partners here . This communication is confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Please inform us immediately and destroy the email.