help about sect163k1 public key size - Openssl

This is a discussion on help about sect163k1 public key size - Openssl ; Hello Ooops sorry for the noise I made a mistake the first format is this one 0000000 30 2b 30 10 06 07 2a 86 48 ce 3d 02 01 06 05 2b 0000020 81 04 00 01 03 17 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: help about sect163k1 public key size

  1. help about sect163k1 public key size

    Hello

    Ooops sorry for the noise


    I made a mistake the first format is this one

    0000000 30 2b 30 10 06 07 2a 86 48 ce 3d 02 01 06 05 2b
    0000020 81 04 00 01 03 17 00 02 00 c6 2b 5c 20 84 e0 33
    0000040 50 cd 27 1c 54 a7 7b 97 5e 10 ce 9d f1

    Second :
    0000000 30 40 30 10 06 07 2a 86 48 ce 3d 02 01 06 05 2b
    0000020 81 04 00 01 03 2c 00 04 05 e4 a9 b0 56 01 51 3f
    0000040 28 cc a0 97 1d 42 e8 62 9b a9 fa 0d ec 05 56 2f
    0000060 86 8a fe 06 ff 09 50 c6 a0 2a 30 d8 df 0b b9 f4
    0000100 73 b6

    The first with a key lentgh of 43 bytes which seems to be the standard,
    the second used by openssl with length 64 bytes. I can't decode using
    asn1parse the first format

    I'm not sure but I don't think that 43 bytes is the compressed format patented by certicom

    Can anyone tell me where I can find informations on that and what is the
    impact on sha1 + sect263k1 signature.

    I use a development snapshot (openssl-SNAP-20080930) of openssl



    Thanks for your help

    Bruno Vetel



    __________________________________________________ ____________________
    OpenSSL Project http://www.openssl.org
    Development Mailing List openssl-dev@openssl.org
    Automated List Manager majordomo@openssl.org


  2. Re: help about sect163k1 public key size

    Hi,

    First format is in compressed form

    30 2b
    30 10
    06 07 2a 86 48 ce 3d 02 01
    06 05 2b 81 04 00 01
    03 17 00 -> (public key as bit string)
    02 -> (compressed format)
    00 c6 2b 5c 20 84 e0 33 50 cd 27 1c 54 a7 7b 97 5e 10 ce 9d f1 -> (x coordinate of EC point)

    Second format is uncompressed form

    30 40
    30 10
    06 07 2a 86 48 ce 3d 02 01
    06 05 2b 81 04 00 01
    03 2c 00 -> (public key as bit string)
    04 -> (uncompressed point)
    05 e4 a9 b0 56 01 51 3f 28 cc a0 97 1d 42 e8 62 9b a9 fa 0d ec -> (x coordinate of EC point)
    05 56 2f 86 8a fe 06 ff 09 50 c6 a0 2a 30 d8 df 0b b9 f4 73 b6 -> (y coordinate of EC point)


    Both formats are supported by OpenSSL.

    Regards,
    Andrzej Chmielowiec

    > Hello
    >
    > Ooops sorry for the noise
    >
    >
    > I made a mistake the first format is this one
    >
    > 0000000 30 2b 30 10 06 07 2a 86 48 ce 3d 02 01 06 05 2b
    > 0000020 81 04 00 01 03 17 00 02 00 c6 2b 5c 20 84 e0 33
    > 0000040 50 cd 27 1c 54 a7 7b 97 5e 10 ce 9d f1
    >
    > Second :
    > 0000000 30 40 30 10 06 07 2a 86 48 ce 3d 02 01 06 05 2b
    > 0000020 81 04 00 01 03 2c 00 04 05 e4 a9 b0 56 01 51 3f
    > 0000040 28 cc a0 97 1d 42 e8 62 9b a9 fa 0d ec 05 56 2f
    > 0000060 86 8a fe 06 ff 09 50 c6 a0 2a 30 d8 df 0b b9 f4
    > 0000100 73 b6
    >
    > The first with a key lentgh of 43 bytes which seems to be the standard,
    > the second used by openssl with length 64 bytes. I can't decode using
    > asn1parse the first format
    >
    > I'm not sure but I don't think that 43 bytes is the compressed format patented by certicom
    >
    > Can anyone tell me where I can find informations on that and what is the
    > impact on sha1 + sect263k1 signature.
    >
    > I use a development snapshot (openssl-SNAP-20080930) of openssl
    >
    >
    >
    > Thanks for your help
    >
    > Bruno Vetel
    >
    >
    >
    > __________________________________________________ ____________________
    > OpenSSL Project http://www.openssl.org
    > Development Mailing List openssl-dev@openssl.org
    > Automated List Manager majordomo@openssl.org
    >
    >


    __________________________________________________ ____________________
    OpenSSL Project http://www.openssl.org
    Development Mailing List openssl-dev@openssl.org
    Automated List Manager majordomo@openssl.org


+ Reply to Thread