123 via RT | 28 Jun 03:49 2016
Picon

Re: [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
3069895744:error:0306E06C:bignum routines:BN_mod_inverse:no inverse:bn_gcd.c:525:
3069895744:error:0307706E:bignum routines:BN_mod_lshift_quick:input not reduced:bn_mod.c:289:
3069895744:error:1408502B:SSL routines:ssl3_ctx_ctrl:reason(43):s3_lib.c:3795:

[1]+  Done(1)                    ./openssl s_server

    Also, under the x86 no problem.Now how to solve this problem?

At 2016-06-28 02:42:35, "Salz, Rich via RT" <rt <at> openssl.org> wrote:
>> 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
apps/s_client.c, for example.  This is currently not likely to get fixed without a lot of detail.
>
>-- 
>Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4587
>Please log in as guest with password guest if prompted
>
(Continue reading)

Mike Frysinger via RT | 28 Jun 00:46 2016
Picon

[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 +-
 doc/crypto/BF_encrypt.pod                    |  4 ++--
 doc/crypto/BIO_ctrl.pod                      | 12 ++++++------
 doc/crypto/BIO_f_buffer.pod                  |  8 ++++----
 doc/crypto/BIO_f_ssl.pod                     | 24 ++++++++++++------------
 doc/crypto/BIO_find_type.pod                 |  2 +-
 doc/crypto/BIO_new.pod                       |  2 +-
 doc/crypto/BIO_push.pod                      |  2 +-
 doc/crypto/BIO_s_bio.pod                     | 12 ++++++------
 doc/crypto/BIO_s_fd.pod                      |  4 ++--
 doc/crypto/BIO_s_file.pod                    |  4 ++--
 doc/crypto/BIO_s_mem.pod                     |  6 +++---
 doc/crypto/BIO_set_callback.pod              | 16 ++++++++--------
 doc/crypto/BN_BLINDING_new.pod               |  2 +-
 doc/crypto/BN_generate_prime.pod             |  6 +++---
 doc/crypto/DH_generate_parameters.pod        |  2 +-
 doc/crypto/DSA_generate_parameters.pod       |  2 +-
 doc/crypto/EVP_BytesToKey.pod                |  4 ++--
 doc/crypto/EVP_DigestInit.pod                |  4 ++--
 doc/crypto/EVP_OpenInit.pod                  |  4 ++--
 doc/crypto/EVP_PKEY_encrypt.pod              |  2 +-
 doc/crypto/EVP_PKEY_keygen.pod               | 12 ++++++------
 doc/crypto/EVP_PKEY_set1_RSA.pod             | 16 ++++++++--------
 doc/crypto/EVP_SignInit.pod                  |  2 +-
 doc/crypto/EVP_VerifyInit.pod                |  2 +-
(Continue reading)

Rich Salz via RT | 27 Jun 22:52 2016
Picon

[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: https://mta.openssl.org/mailman/listinfo/openssl-dev

Thomas Waldmann via RT | 27 Jun 22:50 2016
Picon

Re: [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 line of this mail.

I didn't ask where to get the missing code from, I asked whether you
maybe want to make life simpler for people by adding this to 1.0.x
rather than having a thousand software developers copy and pasting it
into their projects.

But obviously I was expecting too much...

Cython (in our case) has no #if, so we will need a separate C module
just for what was forgotten in 1.0.x (or 0.9.8) back then.

-- 

GPG ID: FAF7B393
GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393

-- 
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4589
Please log in as guest with password guest if prompted

--

-- 
openssl-dev mailing list
(Continue reading)

Rich Salz via RT | 27 Jun 22:43 2016
Picon

[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: https://mta.openssl.org/mailman/listinfo/openssl-dev

Rich Salz via RT | 27 Jun 22:25 2016
Picon

[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 list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Salz, Rich via RT | 27 Jun 20:42 2016
Picon

Re: [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
apps/s_client.c, for example.  This is currently not likely to get fixed without a lot of detail.

-- 
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

Timothy B. Terriberry | 27 Jun 18:21 2016

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: 
<https://bugs.debian.org/828480>, 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 changes, but you may find 
some of this useful, nonetheless. Feel free to disregard it, also, as it 
is just one developer's opinion.

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 are not writing your 
own new BIO implementation.

2) The API documentation for BIO_meth_new() says that "type" should be a 
unique integer, but provides no way to ensure this is true.

Particularly, when using this from a library, I have no way to ensure 
that some number I choose here does not conflict with that chosen by 
some other library in the same application, or with the application 
itself. Furthermore, the values used by OpenSSL for its own internal BIO 
implementations appear to have some structure which the code relies on, 
but which is not documented. Not really having any way to do what the 
documentation asks for, I've simply chosen to pass in BIO_TYPE_NULL, and 
live with the fact that anything that relies on this being unique (not 
much, that I can tell) will not work correctly.

3) I'm not sure the conversion of BIO_METHOD to an opaque struct is 
(Continue reading)

Salz, Rich via RT | 27 Jun 15:58 2016
Picon

Re: [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: https://mta.openssl.org/mailman/listinfo/openssl-dev

Salz, Rich via RT | 27 Jun 15:49 2016
Picon

Re: [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

Catalin Vasile | 27 Jun 14:37 2016

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


Gmane