That helps a lot,
Thanks, Let me look again
On Wed, Jan 29, 2014 at 11:44 AM, Jeffrey Walton wrote:
>
>
>
> On Wed, Jan 29, 2014 at 12:51 AM, Devchandra L Meetei
> wrote:
>
>> when I run ./config, The final lines says following things
>>
>> "Since you've disabled or enabled at least one algori
On Wed, Jan 29, 2014 at 12:51 AM, Devchandra L Meetei wrote:
> when I run ./config, The final lines says following things
>
> "Since you've disabled or enabled at least one algorithm, you need to do
> the following before building:
>
> make depend
> "
> is there any way to check which algo
when I run ./config, The final lines says following things
"Since you've disabled or enabled at least one algorithm, you need to do
the following before building:
make depend
"
is there any way to check which algo are disabled or
How do I enabled all algo?
--
Warm Regards
--Dev
OpenP
> From: Adam M [mailto:open...@irotas.net]
> Sent: Wednesday, January 29, 2014 2:56 AM
>
> On Tue, Jan 28, 2014, at 05:18 PM, Dr. Stephen Henson wrote:
> >
> > Yes the documention is rather old and could be clearer.
> >
> > I had to double check with the source to see what was happening.
> > ...
>
I can create a CSR with the following:
$ openssl req -out ./test.csr -new -newkey rsa:2048 -nodes -keyout
./test.key -subj "/emailAddress=j...@example.com/CN=John Does/C=US"
However, the custom subject causes the CSR to lack other fields, like
State, Locality and Organization.
Is there a way to
On Tue, Jan 28, 2014, at 05:18 PM, Dr. Stephen Henson wrote:
> On Tue, Jan 28, 2014, Adam McLaurin wrote:
>
> > I suspect this will result in a double free bug, as I don't think memory
> > ownership of 'data' is actually passed back to the caller (which is why
> > it's 'const char**'). The error i
> From: Jeremy Farrell
> Sent: Wednesday, January 29, 2014 1:39 AM
>
> > From: Dr. Stephen Henson [mailto:st...@openssl.org]
> > Sent: Wednesday, January 29, 2014 12:50 AM
> > To: openssl-users@openssl.org
> >
> > On Tue, Jan 28, 2014, Jeremy Farrell wrote:
> >
> > >
> > > Ugh. Thanks for checking
> From: Dr. Stephen Henson [mailto:st...@openssl.org]
> Sent: Wednesday, January 29, 2014 12:50 AM
> To: openssl-users@openssl.org
>
> On Tue, Jan 28, 2014, Jeremy Farrell wrote:
>
> >
> > Ugh. Thanks for checking Steve, that's rather different from the
> > understanding I'd built up. I suggest a
On Tue, Jan 28, 2014, Jeremy Farrell wrote:
>
> Ugh. Thanks for checking Steve, that's rather different from the
> understanding I'd built up. I suggest a quick fix to improve the
> documentation would be simply to delete the sentence "If it has been
> allocated by OPENSSL_malloc(), *flags&ERR_TX
> From: Dr. Stephen Henson [mailto:st...@openssl.org]
> Sent: Tuesday, January 28, 2014 10:19 PM
> To: openssl-users@openssl.org
>
> On Tue, Jan 28, 2014, Adam McLaurin wrote:
>
> > I suspect this will result in a double free bug, as I don't think
> memory
> > ownership of 'data' is actually pass
On Tue, Jan 28, 2014, Adam McLaurin wrote:
> I suspect this will result in a double free bug, as I don't think memory
> ownership of 'data' is actually passed back to the caller (which is why
> it's 'const char**'). The error isn't really 'popped' from the queue -
> the queue just gets some indexe
I suspect this will result in a double free bug, as I don't think memory
ownership of 'data' is actually passed back to the caller (which is why
it's 'const char**'). The error isn't really 'popped' from the queue -
the queue just gets some indexes adjusted but the structure itself seems
unmodified
Hi Chinmaya,
I am an engineer working with S/W team at Cavium. I work on OpenSSL
and
Crypto relates Tool kits. We already have a separate Octeon OpenSSL toolkit
which leverages
crypto acceleration of Octeon. If you are interested i can give some
contacts who can
help you get the Toolkit.
Than
Hello,
Our company uses OpenSSL-0.9.8r for our encryption purpose and occasionally
our app would crash because of a undefined pointer in libcrypto.so.0.9.8.
It seems to have to do with the symbol BIO_test_flags. Does anyone else
have this problem and if so how to fix it?
Thanks,
M Van Pham
In C:
if ( data != NULL && flags & ERR_TXT_STRING ) {
PRINT(data);
if ( flags & ERR_TXT_MALLOCED ) {
OPENSSL_free((void *)data);
}
}
> From: Adam M [mailto:open...@irotas.net]
> Sent: Tuesday, January 28, 2014 5:47 PM
> To: openssl-users@openssl.org
>
> I'm
> From: Dr. Stephen Henson [mailto:st...@openssl.org]
> Sent: Tuesday, January 28, 2014 6:41 PM
> On Tue, Jan 28, 2014, Adam M wrote:
>
> > Hi,
> >
> > I'm reading the documentation for ERR_get_error_line_data() here:
> > http://www.openssl.org/docs/crypto/ERR_get_error.html
> >
> > The comments s
On Tue, Jan 28, 2014, at 01:41 PM, Dr. Stephen Henson wrote:
> On Tue, Jan 28, 2014, Adam M wrote:
>
> > Hi,
> >
> > I'm reading the documentation for ERR_get_error_line_data() here:
> > http://www.openssl.org/docs/crypto/ERR_get_error.html
> >
> > The comments say that 'data' is dynamically all
On Tue, Jan 28, 2014, Adam M wrote:
> Hi,
>
> I'm reading the documentation for ERR_get_error_line_data() here:
> http://www.openssl.org/docs/crypto/ERR_get_error.html
>
> The comments say that 'data' is dynamically allocated with
> OPENSSL_malloc() if the ERR_TXT_MALLOCED bit is set in 'flags'.
Hi,
I'm reading the documentation for ERR_get_error_line_data() here:
http://www.openssl.org/docs/crypto/ERR_get_error.html
The comments say that 'data' is dynamically allocated with
OPENSSL_malloc() if the ERR_TXT_MALLOCED bit is set in 'flags'. I
presume this means that we need to call OPENSSL_
Hi,
The Diffe Hellman exchange consists of CPU-intensive
operations like key-pair generation and shared-secret generation. The Octeon
Core Crypto Library provides API's on Octeon for Crypto acceleration. The
following functions (provided by the Cavium) to perform the Diffie-Hellman
Operations, wh
Hello Team,
In our application we open "non blocking socket" for read and write
operation and pass the fd to openssl through BOI API's like this
bio = BIO_new(BIO_s_socket());
BIO_set_fd(bio, socket_fd, BIO_NOCLOSE);
And
we update this bio to SSL using SSL_set_bio() function.
My query is do we
Sorry folks - I was fixated on something else to see the obvious.
-Amarendra
On Sun, Jan 26, 2014 at 10:22 AM, Amarendra Godbole
wrote:
> Hi,
>
> I am analyzing CVE-2013-4353, and the CVSS vector mentions Au
> parameter to N [1] From what I understand, the culprit code is called
> in the Server
22 matches
Mail list logo
