|SMTP TLS, but I am not obligated to provide a comprehensive
|justification in response to every trollish one liner, the above
Luckily there is the UDPish EDNS0 extension from RFC 2671 as in
The default is 1280 (RFC 2671, 4.5.1.).
The minimum is 1024 (RFC 3226, 3.; note: not 1220!).
The m
FYI: it's hard to believe the error is on the OpenSSL side (the
software shows timing errors (the way i use it at least), and
these are always handled properly by the OpenSSL layer), but
i have nonetheless added a 'debug-darwin64-x86_64-cc' to
'Configure' and got some debug libraries (
206984 -r
Hello! Am i right here?
It's actually hard to believe the error is on the OpenSSL side,
and i definetely should look deeper before sending this, but on
the other hand this is so deep down in the OpenSSL code...
?0[steffen@sherwood src]$ openssl version
OpenSSL 1.0.1e 11 Feb 2013
?0[steffen@
JohnSmith wrote:
|*I encrypt an signed mime with this openssl command:*
|
|smime -encrypt -aes128 -to stadl3.de -from stweb.de -subject "Nachricht" -in
|signedmessage -out encryptedsignedmessage2 stadl2certificate.pem
|
|*My problem is that the encrypted message only has from, subject and f
|On Mon, Dec 31, 2012 at 1:58 PM, Walter H. \
|wrote:
|> Hello,
|>
|> why does the following makefile not succeed?
|>
|> ...
|> I have isolated the problem:
|>
|> openssl crl -noout -text -in $< >$@
|> exits with exit code 1 instead of 0, why?
|>
|> openssl crl -noout -text -in $< -ou
Dr. David Kirkby wrote [2012-04-27 09:43+0200]:
>[.]
> See for
>
> ftp://ftp.berlios.de/pub/star/README.otherbugs
>
> He has developed "star"
>
> http://developer.berlios.de/projects/star
>
> which he has said produces POSIX compliant tar files.
(berlios.de seems to be accessible again today.)
