Bitcoin Forum
May 09, 2024, 04:29:45 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: encrypting with 16 digit keyid rather than 8  (Read 1863 times)
curiousone (OP)
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
August 22, 2012, 01:49:32 PM
 #1

I am on Windows 7 using GnuPG (gpa.exe) for encrypting messages.

I need a 16 digit keyid but I can only seem to get 8 digits, I have tried numerous command line attempts to change this (using gpg2.exe in the same directory) but cannot seem to get it right.

Can anyone help?

Thanks
1715272185
Hero Member
*
Offline Offline

Posts: 1715272185

View Profile Personal Message (Offline)

Ignore
1715272185
Reply with quote  #2

1715272185
Report to moderator
1715272185
Hero Member
*
Offline Offline

Posts: 1715272185

View Profile Personal Message (Offline)

Ignore
1715272185
Reply with quote  #2

1715272185
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715272185
Hero Member
*
Offline Offline

Posts: 1715272185

View Profile Personal Message (Offline)

Ignore
1715272185
Reply with quote  #2

1715272185
Report to moderator
1715272185
Hero Member
*
Offline Offline

Posts: 1715272185

View Profile Personal Message (Offline)

Ignore
1715272185
Reply with quote  #2

1715272185
Report to moderator
1715272185
Hero Member
*
Offline Offline

Posts: 1715272185

View Profile Personal Message (Offline)

Ignore
1715272185
Reply with quote  #2

1715272185
Report to moderator
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
August 22, 2012, 01:56:12 PM
Last edit: August 22, 2012, 02:16:16 PM by DeathAndTaxes
 #2

Well there is some mixing up of terms in your post.

The KeyID is simply a way to identify the key.  
You encrypt using the public key of the recipient (and the recipient decrypts using their private key).
You sign using your private key (and verify using the public key of signer).

When encrypting or signing the output will always be the same.  The short or long key ID is simply a way to identify the key.  There is only one key.
Kinda first name or full legal name both identify the same person.

Are you just asking how to get the extender (16 digit) keyID for your keypair? If so I assume this is for Bitcoin-OTC?

If so this should help.  I don't believe GPA has an option to show 16 digit keyID so you will need the GPG CLI tool.   You can keep using GPA or any other client once you have the keyID because it won't change.

GPG command line tool:
http://ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32cli-1.4.11.exe

GPG clients find all keys from the same user store so  if you already created or imported a key using GPA (or another client) it can be "seen" from the CLI tool.

To get extended keyID
Code:
gpg --list-keys --keyid-format long

Example:
Code:
C:\Program Files (x86)\GNU\GnuPG>gpg --list-keys --keyid-format long
C:/Users/<USERNAME>/AppData/Roaming/gnupg\pubring.gpg
-------------------------------------------------------
pub   2048R/28BB715FC26C17CD 2012-06-10
uid                          Tangible Cryptography LLC <info@tangiblecryptography.com>
sub   2048R/73A6FE7F86DA949B 2012-06-10

28BB715FC26C17CD is the 16 digit KeyID for our company master key.  You may or may not have "sub" keys listed.  Sub keys are linked to the master key.  You can google GPG subkey for more info but the simple version if the master KeyID is your full identity.  It was what you want to provide the counterparty.
curiousone (OP)
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
August 22, 2012, 02:14:21 PM
 #3

awesome, thanks.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!