Re: [openssl-dev] [openssl.org #4477] [PATCH] enc command enhancement and small fixes

Please consider that position vacant! ;) I've no idea when I manage to get it (AEAD in enc) done, if at all. Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.   Original Message   From: Michel via RT Sent: Thursday, March 24, 2016 19:48 Reply To: r...@openssl.org Cc:

[openssl-dev] [openssl.org #4477] [PATCH] enc command enhancement and small fixes

Hi, While I was at it (allowing wrap/unwrap mode), I finally decided to remedy some unnecessary restrictions of the 'enc' command. The general idea is to allow to decrypt a file using the original passphrase even when it is not internally salted (hence produced by another software), in which

Re: [openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

> I will make this work with our perl-based test framework. Whao, I will feel like a member of your gang now ! ;-) -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4472 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

> I will make this work with our perl-based test framework. Whao, I will feel like a member of your gang now ! ;-) -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

> the 3 'raw128*.dec' should be the same as 'raw128.dat' > the 2 'raw192*.dec' should be the same as 'raw192.dat' > and finally, 'raw256-256.dec' should be the same as 'raw256.dat'. And not surprisingly, all the tests pass :) I will make this work with our perl-based test framework. > FYI I

Re: [openssl-dev] [openssl.org #4476] PATCH: fix cast-alignment of "struct lhash_st *"

>> > $ git diff include/openssl/lhash.h >> > diff --git a/include/openssl/lhash.h b/include/openssl/lhash.h index >> > 2edd738..5da5054 100644 >> > --- a/include/openssl/lhash.h >> > +++ b/include/openssl/lhash.h >> > @@ -180,7 +180,7 @@ void lh_node_usage_stats_bio(const _LHASH *lh, BIO >> >

[openssl-dev] [openssl.org #4475] RE: [openssl.org #4476] PATCH: fix cast-alignment of "struct lhash_st *"

> Not necessarily. A union might be more comprehensive. Better point :) -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4475 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 #4476] PATCH: fix cast-alignment of "struct lhash_st *"

On Thu, Mar 24, 2016 at 06:41:34PM +, Salz, Rich via RT wrote: > This looks like a good change. > > > This clears what looks to be hundreds of alignment related warnings like > > below. > > > > $ git diff include/openssl/lhash.h > > diff --git a/include/openssl/lhash.h

[openssl-dev] PATCH: fix cast-alignment of "struct lhash_st *"

This looks like a good change. > This clears what looks to be hundreds of alignment related warnings like > below. > > $ git diff include/openssl/lhash.h > diff --git a/include/openssl/lhash.h b/include/openssl/lhash.h index > 2edd738..5da5054 100644 > --- a/include/openssl/lhash.h > +++

[openssl-dev] [openssl.org #4476] PATCH: fix cast-alignment of "struct lhash_st *"

This looks like a good change. > This clears what looks to be hundreds of alignment related warnings like > below. > > $ git diff include/openssl/lhash.h > diff --git a/include/openssl/lhash.h b/include/openssl/lhash.h index > 2edd738..5da5054 100644 > --- a/include/openssl/lhash.h > +++

[openssl-dev] [openssl.org #4475] PATCH: fix cast-alignment of "struct lhash_st *"

This clears what looks to be hundreds of alignment related warnings like below. $ git diff include/openssl/lhash.h diff --git a/include/openssl/lhash.h b/include/openssl/lhash.h index 2edd738..5da5054 100644 --- a/include/openssl/lhash.h +++ b/include/openssl/lhash.h @@ -180,7 +180,7 @@ void

Re: [openssl-dev] [EXTERNAL] Re: [openssl.org #4473] Compile errors when compiling with C++ compiler

On 24/03/2016 17:55, Sands, Daniel wrote: On Thu, 2016-03-24 at 01:08 -0400, Jeffrey Walton wrote: I see some stuff going on that's not allowed in C++, but its dodgy in C. For example: crypto/asn1/asn_mime.c: In function ‘ASN1_VALUE* SMIME_read_ASN1(BIO*, BIO**, const ASN1_ITEM*)’:

Re: [openssl-dev] [EXTERNAL] Re: [openssl.org #4473] Compile errors when compiling with C++ compiler

On Thu, 2016-03-24 at 01:08 -0400, Jeffrey Walton wrote: Lack of relevance. C++ is NOT C. There many subtle and not so subtle differences. OpenSSL is written in C. Use a C compiler. 'make -k' is telling me its a little more than (ir)relevance. I see some stuff going on that's not allowed

Re: [openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

Hi Rich, Thanks for your interest in this matter. the 3 'raw128*.dec' should be the same as 'raw128.dat' the 2 'raw192*.dec' should be the same as 'raw192.dat' and finally, 'raw256-256.dec' should be the same as 'raw256.dat'. FYI I will soon report a new/updated patch with other bugs and

Re: [openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

Hi Rich, Thanks for your interest in this matter. the 3 'raw128*.dec' should be the same as 'raw128.dat' the 2 'raw192*.dec' should be the same as 'raw192.dat' and finally, 'raw256-256.dec' should be the same as 'raw256.dat'. FYI I will soon report a new/updated patch with other bugs and

Re: [openssl-dev] [openssl.org #3676] Resolved: [PATCH] Export ASN1 templates for DH and ECDH groups

> Will the missing export for DHparameters still be fixed for 1.1? It was: commit 599eccfcbf8d77eb7c89b6338fdc39a7531a9f82 Author: Rich Salz Date: Wed Mar 9 20:56:43 2016 -0500 -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] [openssl.org #3676] Resolved: [PATCH] Export ASN1 templates for DH and ECDH groups

> Will the missing export for DHparameters still be fixed for 1.1? It was: commit 599eccfcbf8d77eb7c89b6338fdc39a7531a9f82 Author: Rich Salz Date: Wed Mar 9 20:56:43 2016 -0500 -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3676 Please log in as guest with

[openssl-dev] [openssl.org #4472] [PATCH] alllowing wrap mode using enc command

I did the trivial conversion to Unix shell and run the script. At the end, which files are supposed to compare to be identical? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4472 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

[openssl-dev] [openssl.org #4441] Re: VIA C7-D processor: Hang in 30-test_afalg.t

Kernel bug; closing as requested. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4441 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] [openssl.org #4474] Overflow optimizations being taken by GCC

$ ./config -Wstrict-overflow ... $ make ... crypto/asn1/a_strex.c: In function ‘do_print_ex.constprop.3’: crypto/asn1/a_strex.c:385:12: warning: assuming signed overflow does not occur when simplifying conditional to constant [-Wstrict-overflow] if (len < 0) ^

Re: [openssl-dev] [openssl.org #4441] AutoReply: Re: VIA C7-D processor: Hang in 30-test_afalg.t

This turned out to be a kernel bug. The userland crypto interface was known to have some problems, and the kernel checked in changes to the 2.6 kernel in January 2016. Distro's were cherry picking them for 2.8-4.5, but some needed ones got missed (q.v.). According to and comment 3 at

Re: [openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

> So I guess I should ask... Is using OpenSSL in a C++ program supported > configuration? Sure, as much as anything is "supported" in an open source project. That's not a flip answer. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4473 Please log in as guest with password guest

Re: [openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

On Thu, Mar 24, 2016 at 3:41 AM, Richard Levitte via RT wrote: > Vid Thu, 24 Mar 2016 kl. 07.23.46, skrev levitte: >> Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: >> > I'm not sure if this is a supported configuration, but I'm guessing >> > there are going to be

Re: [openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

On Thu, Mar 24, 2016 at 3:41 AM, Richard Levitte via RT wrote: > Vid Thu, 24 Mar 2016 kl. 07.23.46, skrev levitte: >> Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: >> > I'm not sure if this is a supported configuration, but I'm guessing >> > there are going to be

[openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

Vid Thu, 24 Mar 2016 kl. 07.23.46, skrev levitte: > Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: > > I'm not sure if this is a supported configuration, but I'm guessing > > there are going to be users in the filed who find themselves in it, > > like

Re: [openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

On Thu, Mar 24, 2016 at 3:23 AM, Richard Levitte via RT wrote: > Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: >> I'm not sure if this is a supported configuration, but I'm guessing >> there are going to be users in the filed who find themselves in it, >> like

Re: [openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

On Thu, Mar 24, 2016 at 3:23 AM, Richard Levitte via RT wrote: > Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: >> I'm not sure if this is a supported configuration, but I'm guessing >> there are going to be users in the filed who find themselves in it, >> like

[openssl-dev] [openssl.org #4473] Compile errors when compiling with C++ compiler

Vid Ons, 23 Mar 2016 kl. 23.47.19, skrev noloa...@gmail.com: > I'm not sure if this is a supported configuration, but I'm guessing > there are going to be users in the filed who find themselves in it, > like http://stackoverflow.com/q/36188982. The actual issue there is that we haven't wrapped

[openssl-dev] Master thesis: implementation of a new ciphersuite into OpenSSL -- feedback wanted

Hi, Last year I successfully finished my Master studies at Czech Technical University by a thesis defense about implementing a new CAESAR ciphersuite (specifically with NORX, but not restricted to it) into OpenSSL. I was supervised by prof. Wu Hongjun from Nangyang Technological University,