On Fri, Dec 18, 2009, Dave Thompson wrote:
>
> > 2. openssl asn1parse -inform der -in my.key -strparse 22 -out
> mypubkey.der
> > 3. openssl sha1 -c mypubkey.der
> > SHA1(mypubkey.der)=
> 8d:51:f3:a7:03:5a:79:ca:14:1c:5f:9d:92:39:32:28:a8:1e:e3:7f
>
> asn1parse -strparse will d
> From: owner-openssl-us...@openssl.org On Behalf Of tushar ganguli
> Sent: Friday, 18 December, 2009 00:38
> Hi Steve,
> I did what you said (please correct me if I am wrong) and still
> the ouput is not mappiing, below please find the steps I'd taken:
> 1.
On Fri, Dec 18, 2009, tushar ganguli wrote:
> Hi Steve,
> I did what you said (please correct me if I am wrong) and still the ouput is
> not mappiing, below please find the steps I'd taken:
>
> 1. openssl asn1parse -inform der -in my.key
> 0:d=0 hl=4 l= 629 cons: SEQUENCE
> 4:d=1 hl=2 l= 1
Hi,
On postfix 2.5.7 running on Red Hat Enterprise Linux AS release 4 (Nahant Update 8) I've
got the following error message:
Dec 15 12:09:56 lin2a postfix/smtpd[14097]: connect from 85-18-95-44.ip.fastwebnet.it[85.18.95.44]
Dec 15 12:09:56 lin2a postfix/smtpd[14097]: setting up TLS connection
Hi, I'm adding some details about my problem :
When I receive a SSL_ERROR_SYSCALL (mean the connection closed abruptly)
when trying to read, I try to close the connection, wich cause a mem fault
in sock_write.
Are we supposed to try to close the connection after receiving a
SSL_ERROR_SYSCALL ? If
