Dear OpenSSL developers,
I'm looking at how to adopt Intel ADX instruction extension in OpenSSL. Below
man page mentions ADCX/ADOX instructions:
https://www.openssl.org/docs/manmaster/crypto/OPENSSL_ia32cap.html
but I can not find ADCX/ADOX related words/expressions from OpenSSL-1.0.2h
source
I have a Windows machine where Perl is installed in "C:\Program
Files\Perl64\bin\perl.exe".
When executing "perl Configure VC-WIN32", I get the following error
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
I've fixed the problem, by
> So let's try a better example. The password is "ĂŻ" (U+0102 U+017b),
> and the locale (not that it *should* matter) is ISO8859-2.
When it comes to locale in *this* case you should rather wonder what
does your terminal emulator program do and how does it interact with
your shell. Because these tw
On Mon, 2016-08-29 at 18:40 +0100, David Woodhouse wrote:
>
> So... let's have a password 'nałve', in a ISO8859-2 environment where
> that is represented by the bytes 6e 61 b3 76 65.
>
> First I should try the correct version according to the spec:
> 006e 0061 0142 0076 0065
>
> Then we try the
On Mon, 2016-08-29 at 15:25 +0200, Andy Polyakov wrote:
> First of all. *Everything* that is said below (and what modifications in
> question are about) applies to non-ASCII passwords. ASCII-only passwords
> are not affected by this and keep working as they were.
>
> >
> > >
> > > commit 647ac8d
On Po, 2016-08-29 at 14:27 +, Richard Levitte via RT wrote:
> On Mon Aug 29 12:27:59 2016, appro wrote:
> >
> > Or maybe ("maybe" is reference to "I don't quite grasp" above) what
> > we
> > are talking about is Configure reading CFLAGS and LDFLAGS and
> > *adding*
> > them to generated Makefi
On Mon Aug 29 12:27:59 2016, appro wrote:
> > With the current build system, user-defined CFLAGS are accepted as
> > any
> > unrecognized command line argument passed to Configure. This seems a
> > little dangerous to me since it means a simple typo could end up
> > getting passed to the C compiler
First of all. *Everything* that is said below (and what modifications in
question are about) applies to non-ASCII passwords. ASCII-only passwords
are not affected by this and keep working as they were.
>> commit 647ac8d3d7143e3721d55e1f57730b6f26e72fc9
>>
>> OpenSSL versions before 1.1.0 didn't co
> With the current build system, user-defined CFLAGS are accepted as any
> unrecognized command line argument passed to Configure. This seems a
> little dangerous to me since it means a simple typo could end up
> getting passed to the C compiler.
Is it more dangerous than interactive access? But o
I would like to join this request as maintainer of OpenSSL for Fedora
and Red Hat Enterprise Linux. It would clean up things for us as well.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
(You'll never know
10 matches
Mail list logo
