Re: [EXTERNAL] Re: PKCS12 safecontents bag type deviation from spec
"Blumenthal, Uri - 0553 - MITLL" <[email protected]> Tue, 16 Jan 2018 18:32:46 -0500
| Newsgroups | gmane.comp.encryption.openssl.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============5725378354346044018== Content-Type: multipart/alternative; boundary="Apple-Mail=_A51DC6EA-0780-40BE-BE4A-66E900C60604" --Apple-Mail=_A51DC6EA-0780-40BE-BE4A-66E900C60604 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" I think the change is justified. =E2=80=94 Regards, Uri > On Jan 16, 2018, at 14:31, Sands, Daniel <[email protected]> wrote: >=20 > On Tue, 2018-01-16 at 14:50 +0000, Salz, Rich via openssl-dev wrote: >> OpenSSL defines it as a SET OF and the spec says it=E2=80=99s a = SEQUENCE >> OF. Ouch! Will that cause interop problems if we change it? (I >> don=E2=80=99t remember the DER encoding rules) >>=20 >>=20 >>=20 >=20 > Well, a SEQUENCE uses tag 16 while a SET uses tag 17, according to a > quick reference I found. So that could be an interoperability = concern. > But maybe this is the first actual use of nested safecontents, since > this difference flew under the radar for so long :) > --=20 > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev --Apple-Mail=_A51DC6EA-0780-40BE-BE4A-66E900C60604 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">I think the change is justified.<br class=3D""><div class=3D"">= <div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: = 12px; font-style: normal; font-variant-caps: normal; font-weight: = normal; letter-spacing: normal; orphans: auto; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; widows: = auto; word-spacing: 0px; -webkit-text-size-adjust: auto; = -webkit-text-stroke-width: 0px;"><font face=3D"Monaco" class=3D"">=E2=80=94= <br class=3D"">Regards,<br class=3D"">Uri</font></div> </div> <br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On Jan 16, 2018, at 14:31, Sands, Daniel <<a = href=3D"mailto:[email protected]" class=3D"">[email protected]</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = class=3D"">On Tue, 2018-01-16 at 14:50 +0000, Salz, Rich via openssl-dev = wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">OpenSSL = defines it as a SET OF and the spec says it=E2=80=99s a SEQUENCE<br = class=3D"">OF. Ouch! Will that cause interop = problems if we change it? (I<br class=3D"">don=E2=80=99t = remember the DER encoding rules)<br class=3D""><br class=3D""><br = class=3D""><br class=3D""></blockquote><br class=3D"">Well, a SEQUENCE = uses tag 16 while a SET uses tag 17, according to a<br class=3D"">quick = reference I found. So that could be an interoperability = concern.<br class=3D""> But maybe this is the first actual use of nested = safecontents, since<br class=3D"">this difference flew under the radar = for so long :)<br class=3D"">-- <br class=3D"">openssl-dev mailing = list<br class=3D"">To unsubscribe: <a = href=3D"https://mta.openssl.org/mailman/listinfo/openssl-dev" = class=3D"">https://mta.openssl.org/mailman/listinfo/openssl-dev</a><br = class=3D""></div></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_A51DC6EA-0780-40BE-BE4A-66E900C60604-- --===============5725378354346044018== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev --===============5725378354346044018==--