Good find! This is indeed wrong (sk_*_find returns -1 when the item
couldn't be found).
A grep + code inspection of HEAD 20090202 (sorry, haven't synced to
the VERY latest yet) reveals almost all code checks for '>= 0' or '<
0' as it should.
Code inspection also pops up a few spots in v3_addr.c wh
>On Tue 10/02/09 10:53 PM , Michael Sierchio ku...@tenebras.com sent:
>Tomasz Kaźmierczak wrote:
>> I've managed to base64 decode a public key (at least I think so;).
>> Now I'm trying to understand how to interpret the key data. I've found the
>> definitions of RSAPublicKey and RSAPrivateKey stru
I'm using carbonite to backup my important files to their servers. There was
an option when I installed to manage my own encryption key which I chose to
use. They asked for a pass phrase and I randomly generated one and saved it
into my encrypted password database like I do for all my passwords.
Hello everybody,
I would like to ask what is the difference, from the cryptographic
point of view, between an opaque signature (-nodetach) and a clear
text signature.
Thanks in advance for your answers,
Jan.
__
OpenSSL Project
24 hours on and still stuck!
Nickfx wrote:
>
> Hi, first post here and I wonder if anyone with a larger brain than me can
> help?
>
> I'm in Windows XP Pro and using DD to image a disk and then pipe to
> openssl to encrypt. I'm using the -pass pass:'anotherpassword' switch to
> make decrypti
Since from the looks of it your feeding enc an entire disc image, the
first question of course is: have you tried your process with a
smaller file, say a snippet of about 1K of data or even less?
(I'm thinking about hidden boundary issues here, so best would be to
check the process with something
On Wed, Feb 11, 2009, Jan C. wrote:
> Hello everybody,
> I would like to ask what is the difference, from the cryptographic
> point of view, between an opaque signature (-nodetach) and a clear
> text signature.
>
No cryptographic difference at all: they are different ways of packaging the
same t
On Wed, Feb 11, 2009, Nickfx wrote:
>
>
> Nickfx wrote:
> >
> > Hi, first post here and I wonder if anyone with a larger brain than me can
> > help?
> >
> > I'm in Windows XP Pro and using DD to image a disk and then pipe to
> > openssl to encrypt. I'm using the -pass pass:'anotherpassword' s
Thank you for your kind replies.
Interestingly it appears that 2 days trying to figure out what is wrong with
OpenSSL I was barking up the wrong tree. I omitted from my posted command
line that I was splitting the file after encryption then cat'ing back
together again to decrypt.
Against all lo
Hi, first post and I will confess right up front that I'm far from an expert
on SSL/cryptography.
I'm trying to use OpenSSL to create a PKCS12 Version 3 file for import into
IBM's Digital Certificate Manager. I used our own proprietary code (which
uses a third party library for encryption) to ge
On Wed February 11 2009, Nickfx wrote:
>
> Thank you for your kind replies.
>
> Interestingly it appears that 2 days trying to figure out what is wrong with
> OpenSSL I was barking up the wrong tree. I omitted from my posted command
> line that I was splitting the file after encryption then cat'
Thanks,
I've managed to find a direct link to the X.690 documentation on
Wikipedia
(http://en.wikipedia.org/wiki/Basic_Encoding_Rules#External_links). Now
things are clarifying quickly.
Kyle Hamilton pisze:
For information on how they're encoded, please see ITU recommendation
X.690 (DER).
The problem appears to be how your private key is stored, more than
anything. What are the two lines following "BEGIN ENCRYPTED PRIVATE
KEY" in your sslinf.key file?
(This is one reason that standards exist, so that different things can
(ostensibly) use the file formats. However, not everything
Kyle,
Thanks for the response. Just to clarify a bit, our proprietary code is
simply a wrapper around the third party libraries, which are SSLPlus/BSAFE.
As far as I know they should be generating/storing the private key in a
standards compliant way.
The first 2 lines of the private key are:
M
Could you generate a new private key with that proprietary code, and
post it or email it to me offlist? (this new key would obviously need
to be treated as compromised-destroyed in the NIST framework.)
BEGIN ENCRYPTED PRIVATE KEY looks like PKCS8. There's a couple of
bugs in other implementation
On Wed, Feb 11, 2009, Bob Barnes wrote:
> Kyle,
>
> Thanks for the response. Just to clarify a bit, our proprietary code is
> simply a wrapper around the third party libraries, which are SSLPlus/BSAFE.
> As far as I know they should be generating/storing the private key in a
> standards complian
An excellent idea Ger, I will try it now, thanks for replying.
Nick
On 11 Feb 2009, at 14:04, Ger Hobbelt wrote:
Since from the looks of it your feeding enc an entire disc image, the
first question of course is: have you tried your process with a
smaller file, say a snippet of about 1K of data
On 9-Feb-09, at 11:21 AM, Steffen DETTMER wrote:
Hi all,
* Charles Darwin wrote on Sun, Feb 08, 2009 at 09:27 -0500:
Any idea?
(This is off topic here)
Sorry
Shouldn't it be in /etc/sshd_config (or /etc/ssh/sshd_config)?
Yes it should. Thanks
And if missing there, why not simply a
18 matches
Mail list logo
