start line
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Liz Fall
> Sent: Sunday, 14 September, 2014 00:33
> To: openssl-users@openssl.org
> Subject: RE: cannot read PEM key file - no start line
>
> Thank you, Viktor
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Liz Fall
> Sent: Sunday, 14 September, 2014 00:33
> To: openssl-users@openssl.org
> Subject: RE: cannot read PEM key file - no start line
>
> Thank you, Viktor. Do you have a goo
On Sat, Sep 13, 2014 at 09:32:59PM -0700, Liz Fall wrote:
> Thank you, Viktor. Do you have a good recommendation?
Sorry, have not read any myself. Got there over a couple of decades
via a different path, but I am under the impression that at least
one decent book on the subject is available.
-
read PEM key file - no start line
On Sat, Sep 13, 2014 at 06:46:01PM -0700, Liz Fall wrote:
> I did specify the client key file to NULL. Then, I authenticated the
> client with a user id and password. That worked.
Good. I think it is best to stop there for now.
> Why would the file n
On Sat, Sep 13, 2014 at 06:46:01PM -0700, Liz Fall wrote:
> I did specify the client key file to NULL. Then, I authenticated the client
> with a user id and password. That worked.
Good. I think it is best to stop there for now.
> Why would the file not have a client private key?
[ No such
-openssl-us...@openssl.org] On Behalf Of Viktor Dukhovni
Sent: Friday, September 12, 2014 7:39 AM
To: openssl-users@openssl.org
Subject: Re: cannot read PEM key file - no start line
On Fri, Sep 12, 2014 at 04:31:13AM -0400, Dave Thompson wrote:
> *If* you are now using a legacy-format encrypted priv
> From: owner-openssl-us...@openssl.org On Behalf Of Dave Thompson
> Sent: Friday, September 12, 2014 04:31
> *If* you are now using a legacy-format encrypted private-key (and your
> original
> error message suggested you might need some form of private key, which does
> necessarily mean legacy
On Fri, Sep 12, 2014 at 04:31:13AM -0400, Dave Thompson wrote:
> *If* you are now using a legacy-format encrypted private-key (and your
> original
>
> error message suggested you might need some form of private key, which does
>
> necessarily mean legacy-format encrypted) yes 76 chars is a pr
okay.
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Liz Fall
Sent: Wednesday, September 10, 2014 11:20
To: openssl-users@openssl.org
Subject: RE: cannot read PEM key file - no start line
Hi Dave,
Are you saying that the 76 characters per
On Tue, Sep 9, 2014 at 8:49 PM, Dave Thompson wrote:
> ...
>
> I have and know of no software to create encrypted legacy-format privatekeys
> other than OpenSSL itself which always writes 64, so I never encountered
> this before.
>
You can use Crypto++ with the PEM Pack
(http://www.cryptopp.com/wi
Subject: RE: cannot read PEM key file - no start line
I was half wrong before.
The base64 read in EVP_Decode* allows 76. But the PEM parser in PEM_read_bio
enforces exactly 64 >>only for input files that have PEM-encrypt headers<<
which in practice is only encrypted legacy-forma
To: OpenSSL Users List
Subject: Re: cannot read PEM key file - no start line
On Sun, Sep 7, 2014 at 10:26 PM, Liz Fall wrote:
All,
I am getting the following with my client cert when trying to connect to an
SSL-enabled MongoDB:
2014-09-03T13:37:56.881-0500 ERROR: cannot read
if you need any additional information.
Thanks for your help,
Liz
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Jeffrey Walton
Sent: Tuesday, September 09, 2014 5:09 AM
To: OpenSSL Users List
Subject: Re: cannot read PEM key file - no start lin
On Tue, Sep 09, 2014 at 04:42:53AM -0700, Liz Fall wrote:
> Thanks for the info. I will try what you suggested today. However, I am a
> bit confused by what you are saying - You may need to separately specify a
> CAfile, or CApath for validating the server certificate. I have the two pem
> file
end
line:pem_lib.c:802" when the line size was 76 (see below). This kind of
surprised me.
Since you are receiving the "no start line" error (and not another error),
I would suspect you are reading an ASN.1/DER encoded certificate; and not a
PEM encoded certificate. The error oc
certificate
Thanks,
Liz
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Viktor Dukhovni
Sent: Monday, September 08, 2014 8:28 PM
To: openssl-users@openssl.org
Subject: Re: cannot read PEM key file - no start line
On Mon, Sep 08, 2014
On Mon, Sep 08, 2014 at 08:14:32PM -0700, Liz Fall wrote:
> I am trying to connect to a MongoDB SSL-enable database. This is the API:
> // only really need a PEM on the server side
> mongo::sslGlobalParams.sslPEMKeyFile = "";
The comment is highly misleading. PEM is a "meta" format. I
certificate
Can someone please help clarify this?
Thanks,
Liz
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Viktor Dukhovni
Sent: Monday, September 08, 2014 7:54 PM
To: openssl-users@openssl.org
Subject: Re: cannot read
On Mon, Sep 08, 2014 at 07:44:56PM -0700, Liz Fall wrote:
> This is what my cert looks like below: What are you saying I should do?
> Thanks for the clarification.
These are the certificates for an intermediate CA and the issuing root
CA. Generally, you'd append these to a certificate file with
CERTIFICATE-
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson
Sent: Monday, September 08, 2014 7:29 PM
To: openssl-users@openssl.org
Subject: RE: cannot read PEM key file - no start line
> From: owner-openssl
pec), but the decoder
will accept up to 76 (the less-old MIME spec). As one case I hit often,
Java keytool -exportcert writes 76 and openssl reads it just fine.
And the error here is "no start line". *On Windows* that often occurs
when Windows editors treat text files as Unicode/UTF-8 with
: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Viktor Dukhovni
Sent: Monday, September 08, 2014 5:20 PM
To: openssl-users@openssl.org
Subject: Re: cannot read PEM key file - no start line
On Mon, Sep 08, 2014 at 05:03:58PM -0700, Liz Fall wrote:
> Thank you
sl-us...@openssl.org] On Behalf Of Viktor Dukhovni
Sent: Monday, September 08, 2014 5:20 PM
To: openssl-users@openssl.org
Subject: Re: cannot read PEM key file - no start line
On Mon, Sep 08, 2014 at 05:03:58PM -0700, Liz Fall wrote:
> Thank you so much for your response.
>
> Do I need
On Mon, Sep 08, 2014 at 05:03:58PM -0700, Liz Fall wrote:
> Thank you so much for your response.
>
> Do I need to request for a specific certificate that will is base64?
No, you can just re-wrap the base64 data you have to 64 characters
per line. There are two different 64's here. The size of
, 2014 5:42 AM
To: openssl-users@openssl.org
Subject: Re: cannot read PEM key file - no start line
On Sun, Sep 07, 2014 at 07:26:05PM -0700, Liz Fall wrote:
> I have checked and verified that there is no whitespace. Also, the
> BEGIN and END statements look correct. However, each line in th
On Sun, Sep 7, 2014 at 10:26 PM, Liz Fall wrote:
> I am getting the following with my client cert when trying to connect to an
> SSL-enabled MongoDB:
>
> 2014-09-03T13:37:56.881-0500 ERROR: cannot read PEM key file:
> /users/apps/tstlrn/u019807/DTCD9C3B2F42757.ent.wfb.bank.corp_mongo_wells.pem
On Sun, Sep 07, 2014 at 07:26:05PM -0700, Liz Fall wrote:
> I have checked and verified that there is no whitespace. Also, the BEGIN
> and END statements look correct. However, each line in the cert is 76 chars
> in length, except for the last line. Should the lines be 64-characters
> long?
Ye
On Sun, Sep 7, 2014 at 10:26 PM, Liz Fall wrote:
> I am getting the following with my client cert when trying to connect to
> an SSL-enabled MongoDB:
>
>
> 2014-09-03T13:37:56.881-0500 ERROR: cannot read PEM key file:
> /users/apps/tstlrn/u019807/DTCD9C3B2F42757.ent.wfb.bank.corp_mongo_wells.pem
All,
I am getting the following with my client cert when trying to connect to an
SSL-enabled MongoDB:
2014-09-03T13:37:56.881-0500 ERROR: cannot read PEM key file:
/users/apps/tstlrn/u019807/DTCD9C3B2F42757.ent.wfb.bank.corp_mongo_wells.pem
error:0906D06C:PEM routines:PEM_read_bio:no start li
02.n7.nabble.com/problem-with-pem-file-no-start-line-centos-tp10791p51048.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL Project http://www.openssl.org
User Support Ma
On Tue, Mar 29, 2011 at 10:15:04AM +0200, Aarno Syv?nen wrote:
> HI,
>
> what would error OpenSSL: error:0906D06C:PEM routines:PEM_read_bio:no start
> line mean ?
A PEM file was expected, but the input was not a PEM file, specifically,
it had no "-BEGIN ...-" line.
--
Viktor.
HI,
what would error OpenSSL: error:0906D06C:PEM routines:PEM_read_bio:no start
line mean ?
Aarno
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-use
On 11/18/2010 12:50 AM, Steve yongjin Shin wrote:
-BEGIN RSA PRIVATE KEY-
...omitted..
-END RSA PRIVATE KEY-
-BEGIN CERTIFICATE-
...omitted...
-END CERTIFICATE-
===
Hi all.
I have trouble with using certificates with openssl.
os : centos5.4
kernel : 2.6.27.29
openssl-ver : 0.9.8e-fips-rhel5
At first, I created "rsa private key" and let's suppose this is test.key.
with "test.key" I generated certificate request. and lets suppose this as
test.csr
with "tes
rtificates, keys, Ca, CRL etc...
Thanks All
Maddalena
Da: [EMAIL PROTECTED] per conto di Matyas Majzik
Inviato: ven 20/05/2005 13.21
A: openssl-users@openssl.org
Oggetto: Re: PEM_read_bio: no start line
>Hi All,
>someone knows what does mean :
>&quo
Hi All,
someone knows what does mean :
"PEM_read_bio: no start line"
when server calls the function (for CA file)
:SSL_CTX_load_verify_locations() ?
I'm using openssl-0.9.7d
I think that CA certificate file is not in PEM file format. Therefore I
think that there is no
-BE
Da: Pulcini Maddalena
Inviato: ven 20/05/2005 13.05
A: openssl-users@openssl.org
Oggetto:
Hi All,
someone knows what does mean :
"PEM_read_bio: no start line"
when server calls the function (for CA file) :SSL_CTX_load_verify_locations() ?
Title: Message
Could
someone tell me what the usual cause of a PEM_read_bio:No start line error is? I
am getting this and i think it's causing some problems in my application.
Thanks.
-Andrew T.
FinnellSoftware EngineereSecurity Inc(321) 394-2485
I receive this error when reading the ca-cert.pem file that is included
with openssl: error:***:PEM routines:PEM_read_bio:No start line.
This file loads just fine when running on Windows, but receives the
error when ran on a Macintosh. What could the problem be?
--
Nathan Bell
Companion Corpor
.0...
> SSL_DEBUG_FLAG on
> Error loading /path/to/newcert.pem: 589:error:0906D06C:PEM
> routines:PEM_read_bio:no start line:pem_lib.c:628: 589:error:140CE009:SSL
> routines:SSL_use_RSAPrivateKey_file:missing asn1 eos:ssl_rsa.c:313:
> do_ssleay_init() failed
>
It means there&#
Hiya,
Well, I try it to see my PEM certificate and I can see "-BEGIN CERTIFICATE-"
but It
still isn't working... why?
I repeat all the process bcoss I'm not sure about it.
1. I've installed OpenSSL 0.9.2b and SSLtelnet 0.11.2
2. I've created own CA enviroment (CA.sh -newca)
3. I've c
> /usr/local/ssl/bin/telnet -z debug -z cert=/path/to/newcert.pem 0
> Trying 0.0.0.0...
> SSL_DEBUG_FLAG on
> Error loading /path/to/newcert.pem: 589:error:0906D06C:PEM
> routines:PEM_read_bio:no start line:pem_lib.c:628: 589:error:140CE009:SSL
> routines:SSL_use_RSAPrivateKey_file:missing asn1 eo
Hiya to all,
Well... This is my 10th message in this list, I hope you can answer me some of
them :)
I've installed OpenSSL 0.9.2b and SSLtelnet 0.11.2
Then I've configured my own CA (using CA.sh script)
I've made a Certificate Request (CA.sh -newreq) to my test user
Then i've signed (CA.sh -sign
43 matches
Mail list logo
