I don't know what you expect us to do. We don't use the LD variable.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4609
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Current 1.0.1, 1.0.2 and master don't handle malformed Client Key Exchange
messages correctly.
when a malformed message, or message with incorrect parameters is received
openssl server just closes the connection instead of sending an Alert
message
reproducer script:
On Fri Jul 08 09:33:01 2016, noloa...@gmail.com wrote:
> Hmmm... If I want to use ld.gold as my linker, the easiest path is to
> set LD=ld.gold. It makes perfect sense to some
Did it work for you when doing this?
./config -fuse-ld=gold
--
Richard Levitte
levi...@openssl.org
--
Ticket
On Fri, Jul 8, 2016 at 4:33 AM, Richard Levitte via RT <r...@openssl.org> wrote:
> On Fri Jul 08 07:47:14 2016, noloa...@gmail.com wrote:
>> $ ./config LD=ld.gold
>> Operating system: x86_64-whatever-linux2
>> Configuring for linux-x86_64
>> Configuri
On Fri Jul 08 07:47:14 2016, noloa...@gmail.com wrote:
> $ ./config LD=ld.gold
> Operating system: x86_64-whatever-linux2
> Configuring for linux-x86_64
> Configuring OpenSSL version 1.1.0-pre6-dev (0x0x1016L)
> target already defined - linux-x86_64 (offending arg: LD=ld.gold)
>
> And:
>
> $
$ ./config LD=ld.gold
Operating system: x86_64-whatever-linux2
Configuring for linux-x86_64
Configuring OpenSSL version 1.1.0-pre6-dev (0x0x1016L)
target already defined - linux-x86_64 (offending arg: LD=ld.gold)
And:
$ LD=ld.gold ./config
Operating system: x86_64-whatever-linux2
Configuring
On Thu Jul 07 21:29:09 2016, levitte wrote:
> On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> > /* Add to include/openssl/x509_vfy.h : */
> >
> > typedef int (*X509_STORE_CTX_get_issuer)(X509 **issuer, X509_STORE_CTX
> > *ctx, X509 *x);
> > typedef int
On Thu, Jul 07, 2016 at 09:40:24PM +, Richard Levitte via RT wrote:
> On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> > /* Add to include/openssl/x509v3.h */
> >
> > void X509_set_extension_flags(X509 *x, uint32_t ex_flags);
> > void X509_clear_extension_flags
On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> /* Add to some header file */
>
> CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *ctx);
>
> /* Add to some implementation file */
>
> /* Add to crypto/x509/x509_lu.c */
>
> CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *v)
> {
> return v->lock;
>
I think we should ask kurt to ask the original reporter what they need to do.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4602
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> /* Add to include/openssl/x509v3.h */
>
> void X509_set_extension_flags(X509 *x, uint32_t ex_flags);
> void X509_clear_extension_flags(X509 *x, uint32_t ex_flags);
>
>
> /* Add to crypto/x509v3/v3_purp.c */
>
> void X509_set_extension_flags(X509
On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> /* Add to include/openssl/x509_vfy.h : */
>
> typedef int (*X509_STORE_CTX_get_issuer)(X509 **issuer, X509_STORE_CTX
> *ctx, X509 *x);
> typedef int (*X509_STORE_CTX_check_issued)(X509_STORE_CTX *ctx, X509
> *x, X509 *issuer);
>
> void
On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> Hi,
>
> I received the following bug in debian:
> https://bugs.debian.org/829272
>
>
> I got a lot of bugs filed about packages FTBFS with openssl 1.1.0.
> I started to look at some of them, and many of them are due too
> structures having been
Closing this ticket - fixed in 1.1.0.
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4606
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
I found some dead code in apps/openssl.c which appears to be some legacy
configuration handling.
Patch to remove it is attached.
Pauli
--
Oracle
Dr Paul Dale | Cryptographer | Network Security & Encryption
Phone +61 7 3031 7217
Oracle Australia
--
Ticket here:
On 07/05/2016 02:42 PM, Rich Salz via RT wrote:
> this is for 1.0.2, right?
:; openssl version
OpenSSL 1.1.0-pre6-dev
:; git log
commit c2d551c01930df54bce6517cfecd214db6e98e80
Date: Wed Apr 27 14:47:45 2016 +0100
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please
On Tue Jul 05 22:38:44 2016, ncarb...@prodigitalsoftware.com wrote:
> Knowing that made all the difference, thank you. It wasn't clear since
> there's some evidence of "2.0" in the various downloads.
That's "openssl-fips" which is a FIPS module. Separate thing with its own
versioning.
--
Richard
OK, thanks.
> The code on GitHub is the latest version of what will be 1.1
Knowing that made all the difference, thank you. It wasn't clear since
there's some evidence of "2.0" in the various downloads.
-Noel
-Original Message-
From: Salz, Rich via RT [mailto:r...@open
I don't know what 1.1 beta source you downloaded. The code on GitHub is the
latest version of what will be 1.1 It *is* fixed, just later than the version
you downloaded.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4606
Please log in as guest with password guest if prompted
clear.
-Noel
-Original Message-
From: Rich Salz via RT [mailto:r...@openssl.org]
Sent: Tue, July 5, 2016 5:28 PM
To: ncarb...@prodigitalsoftware.com
Subject: [openssl.org #4606] Resolved: BUG: Windows Startup Code in
OpenSSL RAND_poll() Is Ineffective
According to our records, your request
this is for 1.0.2, right?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi --
Attached are four simple patches.
They make the apps more usable.
They should be pretty much self-explanatory.
Let me know if you have questions.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please log in as guest with password guest if prompted
>From
This is fixed in 1.1.
On Jul 5, 2016 11:29 AM, "Noel Carboni via RT" <r...@openssl.org> wrote:
> This message is to the OpenSSL source code maintainers via
> r...@openssl.org:
>
> I reported this a while back and no one has seen fit to fix it.
>
> On
This message is to the OpenSSL source code maintainers via
r...@openssl.org:
I reported this a while back and no one has seen fit to fix it.
On Windows, the RAND_poll() function in the OpenSSL library uses ancient
Heap32First and Heap32Next function calls to enumerate heap entries from
all
In https://bugs.debian.org/828254, for the software "bro"
I got a request for accessors to:
- For OCSP_RESPID *rid:
- rid->type
- rid->value.byKey->length
- rid->value.byKey->data
- For OCSP_BASICRESP *basic:
- basic->certs
- basic->tbsResponseData->responderId
Kurt
--
Ticket
What part of this is a bug in OpenSSL proper?
To me it looks like the classic issue when linking with static libraries, that
you have to explicitely specify the libraries that libcrypto and libssl depend
on.
Cheers,
Richard
On Mon Jul 04 23:40:25 2016, noloa...@gmail.com wrote:
> From
>From http://stackoverflow.com/q/38192458/608639:
jni/openssl/lib/armeabi-v7a/libcrypto.a(armcap.o):armcap.c:function
OPENSSL_cpuid_setup: error: undefined reference to 'sigfillset'
jni/openssl/lib/armeabi-v7a/libcrypto.a(armcap.o):armcap.c:function
OPENSSL_cpuid_setup: error: undefined reference
Hi,
I received the following bug:
https://bugs.debian.org/829108
the HMAC manpage states:
HMAC_Init_ex() initializes or reuses a HMAC_CTX structure to use the
function evp_md and key key. Either can be NULL, in which case the
existing one will be reused.
However, the current code does
Hi,
I received the following bug in debian:
https://bugs.debian.org/829272
I got a lot of bugs filed about packages FTBFS with openssl 1.1.0.
I started to look at some of them, and many of them are due too
structures having been made opaque. In many cases accessors already
exists, but
On Fri Jul 01 23:31:45 2016, noloa...@gmail.com wrote:
> On Wed, Jun 29, 2016 at 5:19 PM, Richard Levitte via RT
> <r...@openssl.org> wrote:
> > This has nothing to do with Windows 10 per se, it's the space-in-
> > directory
> > issue that's come back.
> > I
On Wed, Jun 29, 2016 at 5:19 PM, Richard Levitte via RT <r...@openssl.org>
wrote:
> This has nothing to do with Windows 10 per se, it's the space-in-directory
> issue that's come back.
> I'm working on a solution that should avoid that problem more consistently,
> going forwa
On Thu, Jun 30, 2016 at 12:52 PM, Salz, Rich via RT <r...@openssl.org> wrote:
>> I don't want either of them. I only want to install the library in the
>> directory of
>> my choosing :)
>
> #! /bin/sh
> make $* && cp *.a $MYDIR
>
> Less flippantly, n
> I don't want either of them. I only want to install the library in the
> directory of
> my choosing :)
#! /bin/sh
make $* && cp *.a $MYDIR
Less flippantly, not everything is supported :)
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4601
Please log in as guest with password
On Thu, Jun 30, 2016 at 11:29 AM, Jeffrey Walton <noloa...@gmail.com> wrote:
> On Thu, Jun 30, 2016 at 11:12 AM, Richard Levitte via RT <r...@openssl.org>
> wrote:
>> That's correct for 1.1.0. install_sw honors --prefix. We made that change to
>> get away f
On Thu, Jun 30, 2016 at 11:12 AM, Richard Levitte via RT <r...@openssl.org>
wrote:
> That's correct for 1.1.0. install_sw honors --prefix. We made that change to
> get away from all the weird magic around the combinations of --prefix and
> --openssldir that happened in pr
That's correct for 1.1.0. install_sw honors --prefix. We made that change to
get away from all the weird magic around the combinations of --prefix and
--openssldir that happened in previous versions.
In other words, it's not a bug, it's a feature. Closing this ticket.
Cheers,
Richard
On Thu Jun
Working on OS 10.8.5. Working from Master,
8a3c000c8f621cd01929313fcb7d0cc23fb516a6.
Using the following configure line:
$ KERNEL_BITS=64 ./config no-shared enable-ec_nistp_64_gcc_128
--openssldir=/usr/local/ssl/1.1.0
Later, when I attempt to compile:
$ gcc -I/usr/local/ssl/1.1.0/include
On Wed Jun 29 21:16:31 2016, levitte wrote:
> On Mon Jun 20 19:37:41 2016, levitte wrote:
> > On Tue Feb 02 01:44:47 2016, openssl-dev@openssl.org wrote:
> > > On Mon, Feb 01, 2016 at 07:18:04PM +0000, Rich Salz via RT wrote:
> > >
> > > > This is reported
This has nothing to do with Windows 10 per se, it's the space-in-directory
issue that's come back.
I'm working on a solution that should avoid that problem more consistently,
going forward.
Cheers,
Richard
On Wed Jun 29 09:04:12 2016, noloa...@gmail.com wrote:
> Working on a Windows 10, 32-bit
On Mon Jun 20 19:37:41 2016, levitte wrote:
> On Tue Feb 02 01:44:47 2016, openssl-dev@openssl.org wrote:
> > On Mon, Feb 01, 2016 at 07:18:04PM +, Rich Salz via RT wrote:
> >
> > > This is reported against 0.9.x; please open a new ticket if still a
> > > pr
when s_client receives alert during handshake and is configured to
export keying material, it will crash with a segmentation fault
current 1.0.2 and master are affected
reproducer:
openssl s_client -keymatexport EXPORT-label -connect google.com:443 -cipher IDEA
Result:
CONNECTED(0003)
Duplicate of RT 3464
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4594
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Working on a Windows 10, 32-bit netbook. HEAD,
03cb37acec0c23a01bee4357cd59ec9f97e528ba.
It looks like configure dies if it can't find NASM. Perhpas it would
be better to automatically add no-asm.
Once NASM is added, Configure dies because it tries to write outside
%HOME%. Windows 8 used to
On 29/06/16 08:33, Tomas Mraz via RT wrote:
> On Út, 2016-06-28 at 22:10 +, Thomas Waldmann via RT wrote:
>> On 06/28/2016 11:18 PM, Kurt Roeckx via RT wrote:
>>>
>>> On Mon, Jun 27, 2016 at 08:50:43PM +0000, Thomas Waldmann via RT
>>> wrote:
>>>
On Út, 2016-06-28 at 22:10 +, Thomas Waldmann via RT wrote:
> On 06/28/2016 11:18 PM, Kurt Roeckx via RT wrote:
> >
> > On Mon, Jun 27, 2016 at 08:50:43PM +, Thomas Waldmann via RT
> > wrote:
> > >
> > > I didn't ask where to get the missi
Hi,
This can be fixed using the patch attached in
https://rt.openssl.org/Ticket/Display.html?id=3464
See also
https://github.com/PeterMosmans/openssl/commit/68ab9b308e173072e5015063be7e194bec1f311f
Cheers,
Peter Mosmans
On 29-06-2016 01:21, Matt Caswell via RT wrote:
>
> On 28/06/16
The attached adds Git repo information if its available.
In the "things work as expected" case, the repo information is
available. It will be submitted with bug reports when configuration
information is provided.
In the "its not a repo" case, then the call to system fails and
nothing is printed.
On 06/28/2016 11:18 PM, Kurt Roeckx via RT wrote:
> On Mon, Jun 27, 2016 at 08:50:43PM +, Thomas Waldmann via RT wrote:
>> 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 t
On Mon, Jun 27, 2016 at 08:50:43PM +, Thomas Waldmann via RT wrote:
> 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 an
> and you will not accept pull requests that do that?
So far, the team is not interested in doing that. Features are not added to
stable branches. But, for myself, I would like to see something like a GitHub
repo that built on top of 1.0.2 and made the 1.1 API's available. I think that
for
On Monday 27 June 2016 20:57:50 Salz, Rich via RT wrote:
> > But obviously I was expecting too much...
>
> Sorry you're not pleased. Not sure what to say -- you get what you pay for?
and you will not accept pull requests that do that?
> Maybe someone will come up with a &quo
from RT#2777
On Monday 27 June 2016 20:43:07 Rich Salz via RT wrote:
> please open a new ticket if this is still an issue with current (at least
> 1.0.2, ideally master) sources.
Current 1.0.2 still doesn't handle ClientHello.client_version set to 0x00,0x00
correctly in a 0x03, 0x00 record
> Also, under the x86 no problem.Now how to solve this problem?
The same way you debug any C problem. Start by running it under the debugger?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4587
Please log in as guest with password guest if prompted
--
openssl-dev
Matt,
>It would be interesting to try this on OpenSSL 1.1.0.
>I have a suspicion this issue is fixed there.
I hope so.
I cannot find a OpenSSL 1.1.0 compiled version anywhere to try.
I'm not that good to compile it myself.
I'll try to contact slproweb.com guys, hopefully they can help.
Thanks
Dear OpenSSL,
As you may be aware, NIST recently approved two Format Preserving
Encryption (FPE) methods - FF1 and FF3.
See:
http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-38G.pdf
The field of tokenization and fixed format encryption (FFX) has taken off
due to PCI compliance.
On 28/06/16 16:18, Oleg Kukartsev via RT wrote:
> Guys,
> There is an issue with openssl s_client described here:
> http://stackoverflow.com/questions/25760596/how-to-terminate-openssl-s-client-after-connection
> Basically, it prevents openssl s_client automation on wind
Guys,
There is an issue with openssl s_client described here:
http://stackoverflow.com/questions/25760596/how-to-terminate-openssl-s-client-after-connection
Basically, it prevents openssl s_client automation on windows platform.
And a similar question here:
./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" <r...@openssl.org> wrote:
>> Guess problem is caused by the CPU architecture.The same example, arm
>> and x86 result is different.ho
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 +-
> 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
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:
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 s
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:
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
> 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
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:
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
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
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 asy
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
OK thanks for your support.
On 26 June 2016 at 19:36, Rich Salz via RT <r...@openssl.org> wrote:
> When it crashes, is k negative? I believe we already fixed this in master.
> with
> commit 0f91e1dff4ab2e7c25bbae5a48dfabbd1a4eae3c (RT 2630).
>
> --
> Ticket here: http
21:23:33, "Rich Salz via RT" <r...@openssl.org> wrote:
>The demo's don't all work, sadly.
>OpenSSL 1.0.1 is very outdated and only gets security fixes; please try a
>recent version.
>closing ticket.
>
>--
>Ticket here: http://rt.openssl.org/Ticket/Display
architecture.The same example, arm and x86
result is different.hope to receive your reply very much!
thank you
At 2016-06-24 21:23:33, "Rich Salz via RT" <r...@openssl.org> wrote:
>The demo's don't all wo
fixed, but slightly differently. thanks!
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2680
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
See https://github.com/openssl/openssl/pull/263 and discussion thread.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3810
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
The amount of source code/build dependency changes to make more of the
no-CIPHER configuration options work is more than we will do for 1.0.2. It is
fixed in 1.1. Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2271
Please log in as guest with password guest if
AI_NUMERICSERV isn't used any more. Is this patch for AI_ADDRCONFIG still
needed? The code in b_addr has it ifdef'd.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3880
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
See RT 3423 and the links for why this is being rejected.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3902
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Seems to be a duplicate of RT 3421; closing.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3143
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
When it crashes, is k negative? I believe we already fixed this in master. with
commit 0f91e1dff4ab2e7c25bbae5a48dfabbd1a4eae3c (RT 2630).
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4235
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To
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 ../test/testlib/OpenSSL/Test/Simple.pm line 77.
# Looks like you failed
Hello,
Recently declaration of a number of get0 methods was changed to return
constant values (BIGNUM).
Lets me quote description of an allocator "/ECDSA_SIG_new()/ allocates a
new *ECDSA_SIG* structure (note: this function also allocates the
BIGNUMs) and initialize it."
Now lets try to
In your previous mail you wrote:
> Nobody got around to looking at this, sorry. I could not decode the patch
> although 103K is big. Windows RT is no longer supported. Closing ticket.
=> no problem...
Thanks
francis.dup...@fdupont.fr
--
Ticket here:
There is not enough information to repeat. Please open a new ticket, post a
backtrace, or whatever.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4298
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
It's not clear there is a bug (in fact, the bug commentary says that). If so,
please open a new ticket with a PEM file of all the certs in the chain. Or
perhaps post to openssl-users mailing list.
Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3886
Please log in as
Cannot reproduce. Attempt to provide a work-around/fix hasn't had any response.
Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3811
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
The warnings are annoying but harmless. running 'make depend' is required.
Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4169
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
No plans to do this. Please re-open the ticket if it's *really* needed for
interop.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3016
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Updated the docs in master and 1.0.2 to explain that these really are
const-like objects.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2964
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Hi,
at borgbackup project, we are currently trying to make it compatible
with OpenSSL 1.0.x and 1.1.x.
For the opaque cipher ctx this worked quite easily like this:
https://github.com/borgbackup/borg/pull/1193/files#diff-85ee6ebe1cdcfd4a4699c3913d519b27R23
I could not have a cipher ctx
Nobody got around to looking at this, sorry. I could not decode the patch
although 103K is big. Windows RT is no longer supported. Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2911
Please log in as guest with password guest if prompted
--
openssl-dev mailing
I just tried this against 1.0.2 and got a backtrace:
#0 0x77847c37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7784b028 in __GI_abort () at abort.c:89
#2 0x00401cfe in my_alloc (n=176) at a.c:4
#3 0x0044e525 in
As Andy said, this flag is not ubiquitous and the workaround is to specify it
config time. Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3792
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
I can't list PKCS#12 file information when it is encrypted with
AES-256-CBC with PKCS#5 v2.0 PBE
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -subj
/CN=localhost -nodes -batch
openssl pkcs12 -export -out bundle.p12 -in localhost.key -nocerts -passout
pass: -name
I'ts not needed; the secure heap automatically puts all private key material in
secure storage, if enabled.
https://github.com/openssl/openssl/pull/1250 is an MR to remove it.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4586
Please log in as guest with password guest if prompted
The demo's don't all work, sadly.
OpenSSL 1.0.1 is very outdated and only gets security fixes; please try a
recent version.
closing ticket.
--
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
Dear：
First of all thank you very much l to contribution.Allow us to use
openssl so good tools.I am a beginner, so had a problem, to be
consulted.Cross-compilation openssl1.0.1 g, on the arm Linux, running under
the/demos/SSL/serv and cli application.The following error:
./serv
The RSA_memory_lock (crypto/rsa/rsa_lib.c) call isn't mentioned in the
documentation. It also isn't called from anywhere inside OpenSSL.
The rsa.h header file says:
| /* This function needs the memory locking malloc callbacks to be installed */
| int RSA_memory_lock(RSA *r);
The
Fixed; see RT 3359 per Steve.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3499
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
This API is gone. Closing ticket.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3921
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
401 - 500 of 12717 matches
Mail list logo
