From Sarah.Blair at webinartv.us Wed Mar 6 18:01:17 2024 From: Sarah.Blair at webinartv.us (Sarah Blair) Date: Wed, 06 Mar 2024 18:01:17 +0000 (UTC) Subject: [Social] Are you going to do a follow-up for the webinar on December 4? Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 15 15:51:32 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 15 Mar 2024 15:51:32 +0000 (UTC) Subject: [Social] Zoom Plans Cancellation Confirmation Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 15 16:00:50 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 15 Mar 2024 16:00:50 +0000 (UTC) Subject: [Social] Zoom Plans Cancellation Confirmation Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 15 16:06:07 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 15 Mar 2024 16:06:07 +0000 (UTC) Subject: [Social] Code for signing in to Zoom Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 15 16:12:11 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 15 Mar 2024 16:12:11 +0000 (UTC) Subject: [Social] Zoom Account Sign In Assistant Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 15 16:13:17 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 15 Mar 2024 16:13:17 +0000 (UTC) Subject: [Social] 050126 is your Zoom verification code Message-ID: <4o2LdqHWTSaAdJunreZ3AQ@geopod-ismtpd-14> An HTML attachment was scrubbed... URL: From billing at zoom.us Fri Mar 15 16:19:31 2024 From: billing at zoom.us (Zoom Video Communications, Inc.) Date: Fri, 15 Mar 2024 16:19:31 +0000 (UTC) Subject: [Social] Payment Processed for 7043649664 Message-ID: <1586984064.360076.1710519571667@7edfec7eaf64>
Your payment has been successfully processed and applied to your account.
 
Zoom Logo Header
 

Payment processed

 

Thank you for your payment.

Please review your payment amount below. We have attached a PDF detailing your order and terms of your subscription.

Account Number: 7043649664
Payment Method: Credit Card
Payment Date: 03/15/2024
Amount: 849.90 US Dollar

To help keep your subscription active, add a backup payment method.

Add backup
 

Support and training




live demo icon

Live demos

Request a 1-1 live demo with a Zoom product specialist to ask questions, learn how Zoom can meet your requirements and review ways Zoom can help your organization.

 
training icon

Live training webinars

Our Zoom trainers host free and interactive live training webinars weekly. Register for an upcoming webinar and get up to speed in less than an hour.

 
support icon

Contact support

Questions? Doubts? Visit our Help Center anytime or take a free course on our Learning Center. If you need more help, submit a ticket, we'll be happy to help you.

 

Need additional help, resources or training?

 
Visit the Zoom Help Center   
 

Visit zoom.us
1-888-799-9666
55 Almaden Blvd., San Jose, CA 95113
© 2024 Zoom - All Rights Reserved

 

You're receiving this email because you signed up for a Zoom account.

 
 
-------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: INV248221966_A21847353_03152024.pdf Type: application/pdf Size: 668497 bytes Desc: not available URL: From no-reply at zoom.us Thu Mar 21 16:16:39 2024 From: no-reply at zoom.us (Zoom) Date: Thu, 21 Mar 2024 16:16:39 +0000 (UTC) Subject: [Social] Reminder: Writing your first Openssl application starts in 1 week Message-ID: An HTML attachment was scrubbed... URL: From claudio.cattaneo at kema.com Fri Mar 22 11:45:00 2024 From: claudio.cattaneo at kema.com (Cattaneo Claudio) Date: Fri, 22 Mar 2024 11:45:00 +0000 Subject: [Social] Support for "Trusted CA Indication" extension as per RFC 6066 Message-ID: Dear Sirs, I would like to kindly ask you a confirmation about the availability of support by OpenSSL for the "Trusted CA Indication" extension as defined in RFC 6066. As per https://github.com/openssl/openssl/issues/3029 it seems that there is no plan to add support for this specific TLS extensions. Nevertheless, it seems a highly desirable features in OT applications (ref IEC 63351-3). Could you please confirm/clarify what is the "current availability"/"plan to make available" this feature from OpenSSL perspective? Thank you in advance for your kind attention. Kind regards, Claudio Cattaneo Claudio Cattaneo Senior Engineer [cid:image001.jpg at 01DA7C56.BF7E2D40] KEMA Labs, a CESI brand CESI S.p.A. Via Rubattino, 54 - 20134 Milano (Italy) Ph. +393356397868 claudio.cattaneo at kema.com - www.kema.com [cid:image002.png at 01DA7C56.BF7E2D40] [cid:image003.png at 01DA7C56.BF7E2D40] IT - Questo messaggio ed i suoi allegati contengono informazioni di natura aziendale e sono classificate ad uso PUBBLICO-AZIENDALE-RISERVATO-RISTRETTO (vale l'opzione evidenziata) EN - This message and its attachments contain company information and are intended for PUBLIC-INTERNAL-RESERVED-RESTRICTED use (see underlined option) IT - Il contenuto di questo messaggio e ogni eventuale documento allegato ? rivolto unicamente alle persone cui ? indirizzato. Se avete ricevuto questo messaggio per errore, vogliate cortesemente avvisarci immediatamente rispondendo all'indirizzo e-mail. EN - This e-mail and any attachment hereto is intended only for the person or entity to which is addressed. If you have received this e-mail by mistake, please notify us immediately on this e-mail address. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3959 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 542 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 540 bytes Desc: image003.png URL: From nhorman at openssl.org Fri Mar 22 12:31:38 2024 From: nhorman at openssl.org (Neil Horman) Date: Fri, 22 Mar 2024 08:31:38 -0400 Subject: [Social] Support for "Trusted CA Indication" extension as per RFC 6066 In-Reply-To: References: Message-ID: On Fri, 2024-03-22 at 11:45 +0000, Cattaneo Claudio wrote: > > > Dear Sirs, > ? > I would like to kindly ask you a confirmation about the availability > of support by OpenSSL for the ?Trusted CA Indication? extension as > defined in RFC 6066. > As per https://github.com/openssl/openssl/issues/3029 it seems that > there is no plan to add support for this specific TLS extensions. > ? > Nevertheless, it seems a highly desirable features in OT applications > (ref IEC 63351-3). > ? > Could you please confirm/clarify what is the ?current > availability?/?plan to make available? this feature from OpenSSL > perspective? > ? > Thank you in advance for your kind attention. > ? > Kind regards, > Claudio Cattaneo > ? Claudio- ? ? ?Currently, no, there continues to be no plan to include the trusted ca indicator extension in openssl. ?the remaining extensions in RFC 6066 were implemented several years ago, but from what I am able to determine from the RFC, the trusted ca indication extension is meant primarily for use on constrained/lower capacity systems, which is not currently a driving target platform category for OpenSSL. ?If you believe there is another use case for this extension, or that this extension serves a significant purpose for your use case, I would encourage you to open a new issue, stating your case, and the engineering team will review and comment on its feasibilty. Thanks and regards Neil > > > > > Claudio Cattaneo > > Senior Engineer > > > > > ? > > > > > > > > > ? > > > > > KEMA Labs, a CESI brand > > > > > CESI S.p.A. > > > > > Via Rubattino, 54 - 20134 Milano (Italy) > Ph. +393356397868 > claudio.cattaneo at kema.com -www.kema.com ?? ? > > > > > ? > > > > > IT - Questo messaggio ed i suoi allegati contengono informazioni di > natura aziendale e sono classificate ad uso PUBBLICO-AZIENDALE- > RISERVATO-RISTRETTO (vale l'opzioneevidenziata) > EN - This message and its attachments contain company information and > are intended for PUBLIC?INTERNAL-RESERVED-RESTRICTED use > (seeunderlined option) > > > > > ? > > > > > IT - Il contenuto di questo messaggio e ogni eventuale documento > allegato ? rivolto unicamente alle persone cui ? indirizzato. Se > avete ricevuto questo messaggio per errore, vogliate cortesemente > avvisarci immediatamente rispondendo all'indirizzo e-mail. > EN - This e-mail and any attachment hereto is intended only for the > person or entity to which is addressed. If you have received this e- > mail by mistake, please notify us immediately on this e-mail address. > > > > > ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3959 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 542 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 540 bytes Desc: image003.png URL: From claudio.cattaneo at kema.com Fri Mar 22 13:00:01 2024 From: claudio.cattaneo at kema.com (Cattaneo Claudio) Date: Fri, 22 Mar 2024 13:00:01 +0000 Subject: [Social] R: Support for "Trusted CA Indication" extension as per RFC 6066 In-Reply-To: References: Message-ID: Dear Neil, thank you very much for your clear and prompt reply. It is really a pity for the Operation Technology field not to be able to avail of this functionality through OpenSSL. A typical (and deeply felt) use case that entails the use of the ?Trusted CA indication? extension is to be able to properly handle the possibility that one device be managed by different administrative domains. With this feature each client connecting to the device, from a specific administrative domain, will be able to require the server to authenticate by providing the certificate signed by the specific CA that the client considers as trusted. I will then consider your suggestion to open an issue for this topic. Kind regards, Claudio Cattaneo Claudio Cattaneo Senior Engineer [cid:image001.jpg at 01DA7C61.3AAA9260] KEMA Labs, a CESI brand Da: Neil Horman Inviato: venerd? 22 marzo 2024 13:32 A: Cattaneo Claudio ; social at openssl.org Oggetto: Re: [Social] Support for "Trusted CA Indication" extension as per RFC 6066 On Fri, 2024-03-22 at 11:45 +0000, Cattaneo Claudio wrote: Dear Sirs, I would like to kindly ask you a confirmation about the availability of support by OpenSSL for the ?Trusted CA Indication? extension as defined in RFC 6066. As per https://github.com/openssl/openssl/issues/3029 it seems that there is no plan to add support for this specific TLS extensions. Nevertheless, it seems a highly desirable features in OT applications (ref IEC 63351-3). Could you please confirm/clarify what is the ?current availability?/?plan to make available? this feature from OpenSSL perspective? Thank you in advance for your kind attention. Kind regards, Claudio Cattaneo Claudio- Currently, no, there continues to be no plan to include the trusted ca indicator extension in openssl. the remaining extensions in RFC 6066 were implemented several years ago, but from what I am able to determine from the RFC, the trusted ca indication extension is meant primarily for use on constrained/lower capacity systems, which is not currently a driving target platform category for OpenSSL. If you believe there is another use case for this extension, or that this extension serves a significant purpose for your use case, I would encourage you to open a new issue, stating your case, and the engineering team will review and comment on its feasibilty. Thanks and regards Neil Claudio Cattaneo Senior Engineer [cid:image001.jpg at 01DA7C61.3AAA9260] KEMA Labs, a CESI brand CESI S.p.A. Via Rubattino, 54 - 20134 Milano (Italy) Ph. +393356397868 claudio.cattaneo at kema.com -www.kema.com [cid:image002.png at 01DA7C5F.E0101A60] [cid:image003.png at 01DA7C5F.E0101A60] IT - Questo messaggio ed i suoi allegati contengono informazioni di natura aziendale e sono classificate ad uso PUBBLICO-AZIENDALE-RISERVATO-RISTRETTO (vale l'opzioneevidenziata) EN - This message and its attachments contain company information and are intended for PUBLIC?INTERNAL-RESERVED-RESTRICTED use (seeunderlined option) IT - Il contenuto di questo messaggio e ogni eventuale documento allegato ? rivolto unicamente alle persone cui ? indirizzato. Se avete ricevuto questo messaggio per errore, vogliate cortesemente avvisarci immediatamente rispondendo all'indirizzo e-mail. EN - This e-mail and any attachment hereto is intended only for the person or entity to which is addressed. If you have received this e-mail by mistake, please notify us immediately on this e-mail address. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 542 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 540 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3959 bytes Desc: image001.jpg URL: From no-reply at zoom.us Wed Mar 27 16:13:14 2024 From: no-reply at zoom.us (Zoom) Date: Wed, 27 Mar 2024 16:13:14 +0000 (UTC) Subject: [Social] Reminder: Writing your first Openssl application starts in 1 day Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Thu Mar 28 14:55:00 2024 From: no-reply at zoom.us (Zoom) Date: Thu, 28 Mar 2024 14:55:00 +0000 (UTC) Subject: [Social] Reminder: Writing your first Openssl application starts in 1 hour Message-ID: An HTML attachment was scrubbed... URL: From bc979 at lafn.org Thu Mar 28 15:50:29 2024 From: bc979 at lafn.org (Doug Hardie) Date: Thu, 28 Mar 2024 08:50:29 -0700 Subject: [Social] Questions Message-ID: When using client certificates, how does SSL_accept validate the provided certificate? If verify_callback is used, is the client certificate validated before the callback is called? -- Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 29 01:16:43 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 29 Mar 2024 01:16:43 +0000 (UTC) Subject: [Social] Thank you for attending Writing your first Openssl application Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 29 01:42:07 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 29 Mar 2024 01:42:07 +0000 (UTC) Subject: [Social] Thank you for attending Writing your first Openssl application Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 29 01:42:58 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 29 Mar 2024 01:42:58 +0000 (UTC) Subject: [Social] Thank you for attending Writing your first Openssl application Message-ID: An HTML attachment was scrubbed... URL: From no-reply at zoom.us Fri Mar 29 16:54:02 2024 From: no-reply at zoom.us (Zoom) Date: Fri, 29 Mar 2024 16:54:02 +0000 (UTC) Subject: [Social] Cloud Recording - Writing Your First OpenSSL Application Webinar Recording is now available Message-ID: An HTML attachment was scrubbed... URL: