Re: [openssl-dev] [openssl.org #4587] openssl on arm linux run err!

Hi: Makefile part I have modified the compiler to remove "- m64" option.Compile completed smoothly.According to what you say, I use the apps/in the program.Also appear a mistake, print is as follows: /mnt/flash/nfs/apps # ./openssl s_server & /mnt/flash/nfs/apps # Error setting EC curve

[openssl-dev] [openssl.org #4593] [PATCH] pod: fix nits related to spacing around commas and assignments

Also update the nit checker to catch missing spaces in prototypes as that is where the majority of errors were located. --- crypto/bn/README.pod | 10 +- doc/apps/ec.pod | 2 +- doc/apps/ecparam.pod | 2 +-

Re: [openssl-dev] Feedback on BIO API changes in 1.1

On 27/06/16 21:56, Timothy B. Terriberry wrote: >> Did you see BIO_meth_set_write etc ? > > I did. I also saw that exactly no code in OpenSSL itself uses this API. Not strictly true. s_server uses it as does asynciotest. We also use the similar RSA_METHOD functions and DSA_METHOD functions in

Re: [openssl-dev] prefer headers from source tree

Hey, good point, and good simple patch. Applied and committed to master. Cheers Richard In message <576efcab.5010...@roumenpetrov.info> on Sun, 26 Jun 2016 00:50:35 +0300, Roumen Petrov said: openssl> Hello, openssl> openssl> Build of master branch fail of on

Re: [openssl-dev] Feedback on BIO API changes in 1.1

> > That sounds like a bug we need to fix. Perhaps something like > > int BIO_meth_new_index([int flags?]) > But I think even just some advice on _how_ to pick a value here would be > sufficient. As long as the space is sufficiently sparse, picking a static > value > with reasonably low

Re: [openssl-dev] [openssl.org #4589] Resolved: simplifying writing code that is 1.0.x and 1.1.x compatible

> But obviously I was expecting too much... Sorry you're not pleased. Not sure what to say -- you get what you pay for? Maybe someone will come up with a "openssl-102-compat" package? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4589 Please log in as guest with password

Re: [openssl-dev] Feedback on BIO API changes in 1.1

Salz, Rich wrote: This feedback is very useful. 1) There is no accessor for the "num" field in the BIO struct. This is typically used to store a file descriptor or similar value. As can be seen by its explicit access in BIO_dup_chain(), there may be legitimate reasons to get at its value,

Re: [openssl-dev] [openssl.org #4589] Resolved: simplifying writing code that is 1.0.x and 1.1.x compatible

> But obviously I was expecting too much... Sorry you're not pleased. Not sure what to say -- you get what you pay for? Maybe someone will come up with a "openssl-102-compat" package? -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] [openssl.org #2919] Incorrect return code and printing of modulus in dsa module

The exit value was fixed some time ago (not sure). The -modulus flag is documented as printing out the public key :) -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2919 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] [openssl.org #4589] Resolved: simplifying writing code that is 1.0.x and 1.1.x compatible

On 06/27/2016 10:25 PM, Rich Salz via RT wrote: > According to our records, your request has been resolved. If you have any > further questions or concerns, please respond to this message. No, it wasn't resolved. You completely missed / ignored the point, which you can read again in the subject

[openssl-dev] [openssl.org #2777] OpenSSL 1.0.1 TLS Version Handling Errors

please open a new ticket if this is still an issue with current (at least 1.0.2, ideally master) sources. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2777 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

[openssl-dev] [openssl.org #4589] simplifying writing code that is 1.0.x and 1.1.x compatible

Look at the wiki, in particular https://wiki.openssl.org/index.php/1.1_API_Changes#Adding_forward-compatible_code_to_older_versions closing ticket. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4589 Please log in as guest with password guest if prompted -- openssl-dev mailing

Re: [openssl-dev] Feedback on BIO API changes in 1.1

This feedback is very useful. > 1) There is no accessor for the "num" field in the BIO struct. > This is typically used to store a file descriptor or similar value. As can be > seen > by its explicit access in BIO_dup_chain(), there may be legitimate reasons to > get at its value, even if you

Re: [openssl-dev] [openssl.org #4587] openssl on arm linux run err!

> Guess problem is caused by the CPU architecture.The same example, arm > and x86 result is different.hope to receive your reply very much! Yes it probably is. What did you change to make it compile? The demo's are mostly old and broken, and in the next release most of them are gone. Looks in

[openssl-dev] Feedback on BIO API changes in 1.1

I recently attempted to convert libopusfile to the new 1.1 API changes (in response to this Debian bug report: , if you want to see what broke). I realize that this late in the release cycle, people are unlikely to want to make additional backwards-incompatible

Re: [openssl-dev] arch (ARM) capabilities

> I want something more programmatic, more general. > I want to deliver a piece of software that will run on ARM architectures and > will issue a warning or something like that if the user does not have an > OpenSSL library set to work with ARM Crypto Extension. What does "set to work" mean?

Re: [openssl-dev] arch (ARM) capabilities

>> Is there an option when making an app that uses OpenSSL to verify >> that is uses Crypto Extensions (like checking a flag or something >> like that) ? > > With x86_64, ciphers like aes-128-cbc are much faster with AES-NI, > so a simple benchmark: > > openssl speed aes-128-cbc openssl speed

Re: [openssl-dev] arch (ARM) capabilities

I want something more programmatic, more general. I want to deliver a piece of software that will run on ARM architectures and will issue a warning or something like that if the user does not have an OpenSSL library set to work with ARM Crypto Extension. From:

Re: [openssl-dev] arch (ARM) capabilities

I want something more programmatic, more general. I want to deliver a piece of software that will run on ARM architectures and will issue a warning or something like that if the user does not have an OpenSSL library set to work with ARM Crypto Extension. From: Hubert Kario

Re: [openssl-dev] arch (ARM) capabilities

On Monday 27 June 2016 12:37:39 Catalin Vasile wrote: > Hi, > > Is there an option when making an app that uses OpenSSL > to verify that is uses Crypto Extensions (like checking > a flag or something like that) ? With x86_64, ciphers like aes-128-cbc are much faster with AES-NI, so a simple

Re: [openssl-dev] [openssl.org #4592] [docs] SSL_set_app_data() returns 'int', not 'void'

You missed SSL_CTX_set_app_data :) I'll fix this as part of another doc fix which is being reviewed now. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4592 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] [openssl.org #4587] openssl on arm linux run err!

Is this using 1.0.1? Please try to do it with 1.0.2 or master. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4587 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] arch (ARM) capabilities

Hi, Is there an option when making an app that uses OpenSSL to verify that is uses Crypto Extensions (like checking a flag or something like that) ? Cata -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] [openssl.org #4586] RSA_memory_lock ?

removed the function. the secure-heap does most of this, anyway now. :) -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4586 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] [openssl.org #4591] asynctest: double free or corruption on hppa

On 26/06/16 15:44, Kurt Roeckx via RT wrote: > Hi, > > My last upload of openssl to experimental show this on hppa: > *** Error in `./asynctest': double free or corruption (out): 0x007307d8 *** > ../util/shlib_wrap.sh ./asynctest => 134 > > # Failed test 'running asynctest' > # at

[openssl-dev] [openssl.org #4592] [docs] SSL_set_app_data() returns 'int', not 'void'

Hey! SSL_set_app_data() is a macro that actually uses the SSL_set_ex_data() function. SSL_set_ex_data() returns an int. Yet, the docs say SSL_set_app_data() returns void. I'd suggest a fix for this like the following. diff --git a/doc/ssl/ssl.pod b/doc/ssl/ssl.pod index 589fc2d..ac2664d

Re: [openssl-dev] [openssl.org #4235] Crash on ssleay_rand_bytes - global variable is not protected

OK thanks for your support. On 26 June 2016 at 19:36, Rich Salz via RT wrote: > When it crashes, is k negative? I believe we already fixed this in master. > with > commit 0f91e1dff4ab2e7c25bbae5a48dfabbd1a4eae3c (RT 2630). > > -- > Ticket here: