Re: RFC: Bring back S/MIME support for IPP Encrypted Jobs and Documents?
"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Hi Ira, Can you also add ipptool updates / IPP Everywhere Self-Certification toolset updates to the agenda? Want to discuss for ~5 minutes. Smith > On Apr 21, 2021, at 8:22 AM, Ira McDonald <[email protected]> wrote: > > Hi Mike and Smith, > > Excellent - I'll add this to IPP WG agenda for tomorrow - will send agenda this afternoon. > > Cheers, > - Ira > Ira McDonald (Musician / Software Architect) > Chair - SAE Trust Anchors and Authentication TF > Co-Chair - TCG Trusted Mobility Solutions WG > Co-Chair - TCG Metadata Access Protocol SG > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music / High North Inc > http://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic> > http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc> > mailto: [email protected] <mailto:[email protected]> > (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > On Wed, Apr 21, 2021 at 8:31 AM Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected] <mailto:[email protected]>> wrote: > Wow, thanks for finding this! I’m sure that enterprises would prefer using S/MIME. We should definitely review this and work to restore S/MIME in TRUSTNOONE if we believe it is appropriate. > > Cheers, > Smith > --- > Smith Kennedy > [email protected] <mailto:[email protected]> > > >> On Apr 21, 2021, at 4:28 AM, Michael Sweet via ipp <[email protected] <mailto:[email protected]>> wrote: >> >> All, >> >> Somehow we missed this, but the IETF published an update to S/MIME in April of 2019: >> >> https://tools.ietf.org/html/rfc8551 <https://tools.ietf.org/html/rfc8551> >> >> Among other things, this update addresses the EFAIL cryptographic vulnerability in S/MIME by adding support for some new cipher suites with Galois/Counter Mode (GCM) instead of the old (insecure) Cipher Block Chaining (CBC) mode. >> >> Using S/MIME bring the advantage that it shares most of the infrastructure that is already in place for TLS, particularly when it comes to trusting a third party. PGP depends on the "web of trust" for this and may not be as attractive to some. >> >> Thoughts? >> >> ________________________ >> Michael Sweet >> >> >> >> _______________________________________________ >> ipp mailing list >> [email protected] <mailto:[email protected]> >> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp> > _______________________________________________ > ipp mailing list > [email protected] <mailto:[email protected]> > https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp> _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAmCAPvsACgkQqskbKLDW 1N0iWg//YfjnQjuxnA0CZ0I9nY2sZO60SoHyD5rg/IK6VxDYxB+E6cJy6/3Ln2bL E6stuWf5BP7/joE3cNPgSkwSaCrc7eunl0z47WWGGv0kb3Lf3OSjcKj8wZG3ziKA p+F+QTc9MC0WhbV80Vsjiw0yGWnbwRThq7DqtUoaCLjAJxrtCs7VOCzxpy11rU9Y 9ecOXupBssO8m0Oq++AbC/r8Rgy5liOozJ1ezlcxbqkh4ElzA73di/EEJdls8C9W 8DZDExZfCBmafQyhomYXYOzZggngb4x4/Ji/nomPlk416LjbhNq7kGgXWdqpj/c4 2zNl8qUJT7Ksqjlt4zDcGxzn0JWfs+ulAqWT+KTjUXWoRR/xIMjdMY0GmpHlEtEF xHxh6hrE3/XoWLU8z/oS2/a/Vyp2LcnniUmX8mYvGvXNPl+DwEwQDts1rI+E9fvV clAyE42Em4SXfEzfSb11V5D09eRPCHL9GGW69VEiz0z/w8KsD9Wr9jMIwJadsX8q VPsWrGzu77Rk9zQSXvlLuDALx6XYfhUOvAGU7sgGGxC3vBraczTCsD5dVdqGrNR5 t9PZTDIXWOUCzOk7unLalXFLfEUKb7OMiCzsGSKMt3WSjt1pUlLjjFj+lMM8693w 84xjtrkjMycsLmnzeRQkWcupY9ZgobJsI2C6+f+qODWIXlQ8oxA= =mDz7 -----END PGP SIGNATURE-----