scallion icon indicating copy to clipboard operation
scallion copied to clipboard

Invalid PrivateKey

Open pskuza opened this issue 7 years ago • 1 comments

Edit:

Can be closed see: https://tor.stackexchange.com/questions/3371/hidden-onion-service-with-2048-bit-or-4096-bit-rsa-private-key-how-to-host Not what I expected.

Tor doesn't start with the private_key generated from scallion.

Log output:

Mar 24 15:06:17.000 [warn] parse error: Wrong size on key for permanent-key: 2048 bits
Mar 24 15:06:17.000 [warn] Error tokenizing descriptor.
Mar 24 15:06:17.000 [warn] rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor xxxxxxxxxxxxxxxxxxxxx

then followed by in an endless loop

Mar 24 15:06:18.000 [warn] upload_service_descriptor(): Bug: Internal error: couldn't encode service descriptor; not uploading. (on Tor 0.2.9.10 )
Mar 24 15:06:19.000 [warn] parse error: Wrong size on key for permanent-key: 2048 bits
Mar 24 15:06:19.000 [warn] Error tokenizing descriptor.
Mar 24 15:06:19.000 [warn] rend_encode_v2_descriptors(): Bug: Could not parse my own descriptor: rendezvous-service-descriptor xxxxxxxxxxxxxxxxxxxxxxxxxxx

Any ideas on what this might mean? The PrivateKey loaded fine into Puttygen for example. Only replacing the private_key file makes tor generate the same hostname file that scallion produced.

So I did a few tests and it seems that tor for whatever reason doesn't like the keys produced with -k 2048

pskuza avatar Mar 24 '17 15:03 pskuza

Last I checked, Tor only works with 1024-bit keys for hidden services.

alecmuffett avatar Apr 03 '17 12:04 alecmuffett