Hi!
Is there a way to make asn1parse print out GENERALSTRING values? I'm
dissecting the Kerberos v5 protocol and it's a large nuisance to mess
with offsets and dumping strings manually.
There doesn't seem to be any related option documented in asn1parse
manual, nor in asn1parse source
(http://cvs
Similar question.
With the problem
http://www.mail-archive.com/openssl-users@openssl.org/msg58527.html
In order to make fipslink.pl work with MKS perl, in fipslink.pl, if I make a
change
that add a line like below:
$sha1_exe =~ s/\\/\//g;
- After this change, fipslink.pl will work with
> From: owner-openssl-us...@openssl.org On Behalf Of liv2luv
> Sent: Tuesday, 19 October, 2010 11:26
> I am new to SSL and Certificates.
>
> I have generated a CSR and certificate for signing. In return
> I've got three
> certificates.
>
> a. Root CA's certificate
> b. Intermediate Certificate
> So I wasted my precious time preparing a patch while someone
> else had already posted a patch off-list.
Lol... If you're going to throw a tantrum every time someone beats you
ta a patch, you owe us a tantrum:
WinCE patch:
http://www.mail-archive.com/openssl-users@openssl.org/msg61765.html
Pierr
Hi,
I am new to SSL and Certificates.
I have generated a CSR and certificate for signing. In return I've got three
certificates.
a. Root CA's certificate
b. Intermediate Certificate
c. Server certificate
After some searching, understand I need to combine them in the sequence as
server, interm
Hi,
I was not involved in this discussion, but I wanted just to say that
patches and other development issues are discussed in the openssl-dev
list and all messages sent to r...@openssl.org are also copied to that
list not the users list. Anyone interested in OpenSSL internals should
join o
On 19-10-2010 12:32, per frykenvall wrote:
Thanks, Jakob! However, I followed Dr. Stephen Hensons advice earlier
in this thread and filed a report to the bug tracker, and got a
resolution from Andy Polyakov a week ago, based on your suggestion.
I've tested it and am fully satisfied:
[openss
Thanks, Jakob! However, I followed Dr. Stephen Hensons advice earlier
in this thread and filed a report to the bug tracker, and got a
resolution from Andy Polyakov a week ago, based on your suggestion. I've
tested it and am fully satisfied:
[openssl.org #2356] Resolved: LNK4078 and LNK4210 li
Yes, easy, just open openssl.conf in a notepad or another simple text
editor and set it to the desired number of days/years. I have done so
on our internal CA, and it simply works.
If you wish to increase (not decrease) the validity length of your
existing CA, you will need to do the following:
Forwarded to openssl-users for discussion.
Best regards,
Lutz
- Forwarded message from Santhosh AP -
Reply-To: santhosh...@sifycorp.com
From: Santhosh AP
To: r...@openssl.org
Subject: default_crl_days= 365
Date: Tue, 19 Oct 2010 10:16:09 +0530
Thread-Index: ActvSItTKvsOwU5sQvG6
10 matches
Mail list logo