On Jan 25, 2013, at 6:45 PM, Dave Thompson wrote:
>> I dug up the X,690 document that describes the DER format,
>> and that is basically the approach that I've been working on.
>> I now have a very basic DER parser that will handle the
>> Sequence and Integer types that are in the public keys
> From: owner-openssl-us...@openssl.org On Behalf Of Tovey, Dwight (LaserJet
R&D FW Eng.)
> Sent: Friday, 25 January, 2013 17:50
> On Jan 24, 2013, at 8:13 PM, Dave Thompson
> wrote:
>
> > If you want to do it actually in Python:
> > - get m and e from the public key (DER isn't hard to parse,
On Jan 24, 2013, at 8:13 PM, Dave Thompson
wrote:
> If you want to do it actually in Python:
> - get m and e from the public key (DER isn't hard to parse,
> you were already shown an example elsethread, and if Python
> doesn't have a direct way to convert bytestring to bignum
> which I'd exp
> From: owner-openssl-us...@openssl.org On Behalf Of Tovey, Dwight (LaserJet
R&D FW Eng.)
> Sent: Thursday, 24 January, 2013 10:55
> On Jan 23, 2013, at 3:56 PM, Dave Thompson
> wrote:
>
> > Most utilities, yes, although the library supports both.
> > (The routines named RSAPublicKey do the sp
> From: owner-openssl-us...@openssl.org On Behalf Of Viktor Dukhovni
> Sent: Thursday, 24 January, 2013 13:25
> On Thu, Jan 24, 2013 at 05:25:48PM +, Tovey, Dwight
> (LaserJet R&D FW Eng.) wrote:
> > So, my next question is, how did you add the public key
> header? What does this header l
Thanks for explanation.
--kapetr
Dne 24.1.2013 19:31, Erwann Abalea napsal(a):
The 0x00 byte in the BITSTRING is the number of unused bits in the last
octet of the encoded bit string.
See X.690 as a BER/DER reference. Document is free to download from ITU
website.
The 0x00 byte in the BITSTRING is the number of unused bits in the last
octet of the encoded bit string.
See X.690 as a BER/DER reference. Document is free to download from ITU
website.
--
Erwann ABALEA
Le 24/01/2013 19:17, kap...@mizera.cz a écrit :
I have used header from my certificate - it
On Thu, Jan 24, 2013 at 05:25:48PM +, Tovey, Dwight (LaserJet R&D FW Eng.)
wrote:
> On Jan 23, 2013, at 4:18 PM, kap...@mizera.cz wrote:
>
> > I have build the whole pub-key (in DER) from yours pubkey.bin by adding
> > public key header - as wrote w...@omnigroup.com
> >
> > If I did not m
I have used header from my certificate - it does contain only ASN.1
structure data - unspecific.
The structure you can see with
openssl asn1parse -in pub-key.der -inform der
The added "header" are simply the first 22 bytes.
(not 21 (=18+3) - there is in correctly formated pub-key 1 byte 00h on
On Jan 23, 2013, at 4:18 PM, kap...@mizera.cz wrote:
> I have build the whole pub-key (in DER) from yours pubkey.bin by adding
> public key header - as wrote w...@omnigroup.com
>
> If I did not make error, it could work now - try it.
> It is in attachment.
>
> openssl asn1parse -in pub-key.de
On Jan 23, 2013, at 3:56 PM, Dave Thompson
wrote:
> Most utilities, yes, although the library supports both.
> (The routines named RSAPublicKey do the specific PKCS#1 form,
> the routines named RSA_PUBKEY or just PUBKEY do the wrapped form.)
>
> But on checking source, since 1.0.0 'rsa' has a
I have build the whole pub-key (in DER) from yours pubkey.bin by adding
public key header - as wrote w...@omnigroup.com
If I did not make error, it could work now - try it.
It is in attachment.
openssl asn1parse -in pub-key.der -inform der -strparse 18
and you will see the same as by parsing
> From: owner-openssl-us...@openssl.org On Behalf Of Wim Lewis
> Sent: Wednesday, 23 January, 2013 16:57
> On Jan 23, 2013, at 1:12 PM, Tovey, Dwight (LaserJet R&D FW
> Eng.) wrote:
> > Hello all -
> >
> > I have a need to send a bit of RSA encrypted data to a
> device. The device will provid
On Jan 23, 2013, at 1:12 PM, Tovey, Dwight (LaserJet R&D FW Eng.) wrote:
> Hello all –
>
> I have a need to send a bit of RSA encrypted data to a device. The device
> will provide it’s public key via SNMP as 140 bytes of binary data. I’m
> assuming that the data is DER format, but I can’t swe
14 matches
Mail list logo