I also believe that we shouldn’t be relying on locale, it is a Pandora’s box we
don’t want to open.
Even claiming that OpenSSL is UTF-8 compliant is probably a stretch (e.g. the
isXXX functions aren’t).
Saying we accept unsigned eight bit byte inputs and process them unmodified is
as far as I’d
> On Jun 1, 2018, at 6:47 PM, Richard Levitte wrote:
>
> Ah, forgot one important detail: it is well understood that *all*
> file based objects will get the same requirements, right? That goes
> for anything protected through PKCS#5 as well (good ol' PEM
> encryption, PKCS#8 objects and
In message <20180602.004350.1602483119932820478.levi...@openssl.org> on Sat, 02
Jun 2018 00:43:50 +0200 (CEST), Richard Levitte said:
levitte> In message <7c04edbc-9d70-42ea-9ec9-6e6c4fbb8...@dukhovni.org> on Fri,
1 Jun 2018 18:23:48 -0400, Viktor Dukhovni said:
levitte>
levitte>
> On Jun 1, 2018, at 6:16 PM, Richard Levitte wrote:
>
> (I'm currently looking into alternatives where a UI_METHOD can present
> several variants of the same pass phrase, thus making it possible for
> the application to virtually say "hey, try one of these" instead of
> "hey, try this
In message <14b35465-b944-492f-9c09-4a243d1aa...@dukhovni.org> on Fri, 1 Jun
2018 17:57:46 -0400, Viktor Dukhovni said:
openssl-users>
openssl-users>
openssl-users> > On Jun 1, 2018, at 5:51 PM, Kurt Roeckx wrote:
openssl-users> >
openssl-users> > That would then just mean that the apps
> On Jun 1, 2018, at 5:51 PM, Kurt Roeckx wrote:
>
> That would then just mean that the apps need to do the correct
> thing and convert it to UTF-8.
Module legacy files, with a passphrase in some other encoding.
For those the applications will have to provide the right
non-UTF8 octet string,
On Fri, Jun 01, 2018 at 01:20:17PM -0500, Benjamin Kaduk wrote:
> On Fri, Jun 01, 2018 at 12:23:39PM +, Salz, Rich wrote:
> > >I think that the gist of the difference of opinion is whether it's OK
> > to use locale dependent functions such as mbstowcs in libcrypto or
> > not.
> >
> On Jun 1, 2018, at 5:26 PM, Salz, Rich wrote:
>
> So maybe I should just create a PR to update INSTALL with the Mac recipe?
I just use:
./Configure --prefix=/some/where [options] shared darwin64-x86_64-cc
--
Viktor.
___
In message <1bd96940-3b3b-4758-938a-01e576306...@akamai.com> on Fri, 1 Jun 2018
21:26:12 +, "Salz, Rich" said:
rsalz> >Regarding the original question, it's "supported" insofar that we
have
rsalz> osx among the Travis builds (at least usually... there have been
rsalz> times
>Regarding the original question, it's "supported" insofar that we have
osx among the Travis builds (at least usually... there have been
times when the osx backlog has been so great that we've temporarly
disabled it).
So maybe I should just create a PR to update INSTALL with
On Fri, Jun 01, 2018 at 06:52:21PM +, Salz, Rich wrote:
> Our INSTALL doesn’t mention it. We have config’s for it. I think we should
> say we support it and update the various docs. Thoughts?
The PR associated with the thread around
On Fri, Jun 01, 2018 at 12:23:39PM +, Salz, Rich wrote:
> >I think that the gist of the difference of opinion is whether it's OK
> to use locale dependent functions such as mbstowcs in libcrypto or
> not.
>
>
> Thanks for the summary.
>
> I am against use locale-dependent
>I think that the gist of the difference of opinion is whether it's OK
to use locale dependent functions such as mbstowcs in libcrypto or
not.
Thanks for the summary.
I am against use locale-dependent functions in libcrypto.
___
> I think that the gist of the difference of opinion is whether it's OK
> to use locale dependent functions such as mbstowcs in libcrypto or
> not.
>
> The main arguments against allowing such functions in libcrypto is
> that we should push applications to run with an UTF-8 input method
>
Hi,
PR #6341 (https://github.com/openssl/openssl/pull/6341) is stuck in a
battle of opinions that doesn't seem to get anywhere, so for all
practical purposes, it's currently blocked.
I think that the gist of the difference of opinion is whether it's OK
to use locale dependent functions such as
15 matches
Mail list logo
