On 25/01/13 15:39, Dr. Stephen Henson wrote:
On Fri, Jan 25, 2013, T J wrote:
It seems the path to the config file is hardcoded into the openssl
executable at compile time based on the install dir and the only way
to change it is by setting the environment variable OPENSSL_CONF. I
don't have t
> From: owner-openssl-us...@openssl.org On Behalf Of Dr. Stephen Henson
> Sent: Thursday, 24 January, 2013 18:19
> On Thu, Jan 24, 2013, Jeffrey Walton wrote:
>
> > On Wed, Jan 23, 2013 at 1:20 PM, Smith, Russell (Shane), Contractor
> > wrote:
> > > I am looking for a way to disable weak ciphers
> From: owner-openssl-us...@openssl.org On Behalf Of Tovey, Dwight (LaserJet
R&D FW Eng.)
> Sent: Thursday, 24 January, 2013 10:55
> On Jan 23, 2013, at 3:56 PM, Dave Thompson
> wrote:
>
> > Most utilities, yes, although the library supports both.
> > (The routines named RSAPublicKey do the sp
> From: owner-openssl-us...@openssl.org On Behalf Of Viktor Dukhovni
> Sent: Thursday, 24 January, 2013 13:25
> On Thu, Jan 24, 2013 at 05:25:48PM +, Tovey, Dwight
> (LaserJet R&D FW Eng.) wrote:
> > So, my next question is, how did you add the public key
> header? What does this header l
On Fri, Jan 25, 2013, T J wrote:
>
> >>It seems the path to the config file is hardcoded into the openssl
> >>executable at compile time based on the install dir and the only way
> >>to change it is by setting the environment variable OPENSSL_CONF. I
> >>don't have that option.
>
It seems the path to the config file is hardcoded into the openssl
executable at compile time based on the install dir and the only way
to change it is by setting the environment variable OPENSSL_CONF. I
don't have that option.
In my setup, I am installing openssl to a temp dir ($(SSLDIR)/base)
On 25/01/13 12:15, Dr. Stephen Henson wrote:
On Fri, Jan 25, 2013, T J wrote:
It seems the path to the config file is hardcoded into the openssl
executable at compile time based on the install dir and the only way
to change it is by setting the environment variable OPENSSL_CONF. I
don't have t
On Thu, Jan 24, 2013, Jeffrey Walton wrote:
> On Wed, Jan 23, 2013 at 1:20 PM, Smith, Russell (Shane), Contractor
> wrote:
> > I am looking for a way to disable weak ciphers in openssl.
> > I have a legacy program that uses the "default" SSL ciphers and is not
> > configurable like apache and ht
On Fri, Jan 25, 2013, T J wrote:
> >>>
> >>> It seems the path to the config file is hardcoded into the openssl
> >>> executable at compile time based on the install dir and the only way
> >>> to change it is by setting the environment variable OPENSSL_CONF. I
> >>> don't have that option.
> >>>
>
On Wed, Jan 23, 2013 at 1:20 PM, Smith, Russell (Shane), Contractor
wrote:
> I am looking for a way to disable weak ciphers in openssl.
> I have a legacy program that uses the "default" SSL ciphers and is not
> configurable like apache and httpd.conf etc.
> Is there any way I can change the a
>
> It seems the path to the config file is hardcoded into the openssl
> executable at compile time based on the install dir and the only way
> to change it is by setting the environment variable OPENSSL_CONF. I
> don't have that option.
>
> In my setup, I am installing openssl to a temp dir ($(SS
Thanks for explanation.
--kapetr
Dne 24.1.2013 19:31, Erwann Abalea napsal(a):
The 0x00 byte in the BITSTRING is the number of unused bits in the last
octet of the encoded bit string.
See X.690 as a BER/DER reference. Document is free to download from ITU
website.
The 0x00 byte in the BITSTRING is the number of unused bits in the last
octet of the encoded bit string.
See X.690 as a BER/DER reference. Document is free to download from ITU
website.
--
Erwann ABALEA
Le 24/01/2013 19:17, kap...@mizera.cz a écrit :
I have used header from my certificate - it
On Thu, Jan 24, 2013 at 05:25:48PM +, Tovey, Dwight (LaserJet R&D FW Eng.)
wrote:
> On Jan 23, 2013, at 4:18 PM, kap...@mizera.cz wrote:
>
> > I have build the whole pub-key (in DER) from yours pubkey.bin by adding
> > public key header - as wrote w...@omnigroup.com
> >
> > If I did not m
I have used header from my certificate - it does contain only ASN.1
structure data - unspecific.
The structure you can see with
openssl asn1parse -in pub-key.der -inform der
The added "header" are simply the first 22 bytes.
(not 21 (=18+3) - there is in correctly formated pub-key 1 byte 00h on
Yours is the first instance of my getting a message with a warning about the
digital signature. Maybe I recently changed one of my settings in Outlook to
increase its security notifications, but I don't think so. In any case, here
is what I saw:
John A. Wallace
The pen is mightie
On Thu, Jan 24, 2013 at 02:49:25PM +0100, Dr. Stephen Henson wrote:
> > This is a rather non-obvious interface, and X509_get_X509_PUBKEY() is
> > not documented.
> >
>
> I make no claim this is obvious but...
>
> It should be possible to do this in a single call using the ASN1_item_verify
> int
On Jan 23, 2013, at 4:18 PM, kap...@mizera.cz wrote:
> I have build the whole pub-key (in DER) from yours pubkey.bin by adding
> public key header - as wrote w...@omnigroup.com
>
> If I did not make error, it could work now - try it.
> It is in attachment.
>
> openssl asn1parse -in pub-key.de
On Thu, Jan 24, 2013, T J wrote:
>
> It seems the path to the config file is hardcoded into the openssl
> executable at compile time based on the install dir and the only way
> to change it is by setting the environment variable OPENSSL_CONF. I
> don't have that option.
>
> In my setup, I am ins
On Jan 23, 2013, at 3:56 PM, Dave Thompson
wrote:
> Most utilities, yes, although the library supports both.
> (The routines named RSAPublicKey do the specific PKCS#1 form,
> the routines named RSA_PUBKEY or just PUBKEY do the wrapped form.)
>
> But on checking source, since 1.0.0 'rsa' has a
On Wed, Jan 23, 2013, Viktor Dukhovni wrote:
> The OpenSSL library includes two very similar functions:
>
> int X509_digest(
> X509 *cert,
> const EVP_MD *digest,
> unsigned char *md,
> int *len);
>
> int X509_pubkey_digest(
>
21 matches
Mail list logo
