On Wed, Jun 06, 2018 at 09:45:10AM +0200, Richard Levitte wrote:
> Yup. It seems that BMPString evolved from UCS-2 into UTF-16 at some
> point
The only thing that evolved from UCS-2 to UTF-16 that I know of is
Microsoft Windows. NT used UCS-2, 2000 changed that to UTF-16.
Kurt
On Wed, Jun 06, 2018 at 11:23:55AM -0400, David Benjamin wrote:
>
> Is there a spec citation for this, or some documented experiments against
> other implementations' behavior? (What do Microsoft and NSS do here?) I was
> pondering something similar recently, but things do seem to point at UCS-2
Oh, I didn't realize that document existed. Although it doesn't say that it
is overriding the BMPString restrictions. It says it "does not add any
*further* restrictions to the input passwords of these methods, however it
is RECOMMENDED to use (big-endian) UTF-16 NFC form". That reads to me as
https://tools.ietf.org/html/draft-mavrogiannopoulos-pkcs5-passwords-02#section-4
https://tools.ietf.org/html/draft-mavrogiannopoulos-pkcs5-passwords-02#section-5.2
> On Jun 6, 2018, at 11:23 AM, David Benjamin wrote:
>
> Is there a spec citation for this, or some documented experiments against
On Wed, Jun 6, 2018 at 3:45 AM Richard Levitte wrote:
> In message <4dca9a91-1487-4bfc-8a4e-b79fad473...@dukhovni.org> on Tue, 5
> Jun 2018 18:37:21 -0400, Viktor Dukhovni
> said:
>
> openssl-users>
> openssl-users>
> openssl-users> > On Jun 3, 2018, at 4:45 AM, Richard Levitte <
>
In message <4dca9a91-1487-4bfc-8a4e-b79fad473...@dukhovni.org> on Tue, 5 Jun
2018 18:37:21 -0400, Viktor Dukhovni said:
openssl-users>
openssl-users>
openssl-users> > On Jun 3, 2018, at 4:45 AM, Richard Levitte
wrote:
openssl-users> >
openssl-users> > Yeah, I just learned that myself.
