Dear Josh,
Greetings.
I have a windows machine that a lot of Operating system users (windows users) can access.
I want all of these users to be able to import keys to the same shared rings (pub and priv).
I had edited the Environment Variable on the machine and also the "C:\ProgramData\PGP Corporation\PGP\PGPprefs.xml" with the below configuration:
<key>rngSeedFile</key><string>C:\pgp_home\randseed.rnd</string><key>privateKeyringFile</key><string>C:\pgp_home\rings\secring.skr</string><key>publicKeyringFile</key><string>C:\pgp_home\rings\pubring.pkr</string>
when I execute the command "
pgp --version --verbose "
I get the below output for each user:
Administrator:File information:Home Directory: C:\pgp_home\Personal Directory: C:\pgp_home\Public Keyring: C:\pgp_home\rings\pubring.pkrPrivate Keyring: C:\pgp_home\rings\secring.skrRandom Seed: C:\pgp_home\randseed.rndWCG:File information:Home Directory: C:\Users\wcg\AppData\Roaming\PGP Corporation\PGP\Personal Directory: C:\Users\wcg\Documents\PGP\Public Keyring: C:\pgp_home\rings\pubring.pkrPrivate Keyring: C:\pgp_home\rings\secring.skrRandom Seed: C:\pgp_home\randseed.rndCould you please help me to make both identical ?
That will help me import any key with any windows account .
In the above case I can import any key with
Administrator account only and list the keys normally and I can find the key.
But with
WCG account, the key is imported but it's not listed.
BR,
Ahmed Magdy
Original Message:
Sent: 11-30-2020 02:20 PM
From: Joshua Johnson
Subject: 1080: No private key found : PGP Command Line
Yes. When you issue the --encrypt command the key(s) you wish to encrypt to should be specified as a --recipient. If a recipient is ambiguous (for example, multiple keys with the same email address) then use an unambiguous property as the --recipient, like a keyid.
Josh
Original Message:
Sent: 11-30-2020 02:12 PM
From: Ahmed Magdy
Subject: 1080: No private key found : PGP Command Line
If the user has multiple keys. Can I encrypt a file using one of them ? I mean specific one.
BR,
Original Message:
Sent: 11-30-2020 02:02 PM
From: Joshua Johnson
Subject: 1080: No private key found : PGP Command Line
PGP Command Line doesn't have the concept of different users. By default, it will store its keyrings and preferences in the user's home directory but the software doesn't do any user management or anything like that. If you have a keyring that you need a different user to access then replace the user's keyring with the desired keyring. You can also use --export to export a key from an existing keyring and --import to import them into the new user's keyring if there are only a subset of keys desired for the new user.
Josh
Original Message:
Sent: 11-30-2020 01:47 PM
From: Ahmed Magdy
Subject: 1080: No private key found : PGP Command Line
Dear Josh,
Thanks for valuable help.
Now, is it possible to link the imported keys to a specific user ?
Example:
=======
1-I imported "key1"
2-create a user with no keys (I don't know hot to da that)
3-Enforce the user to use the imported keypairs only to encrypt/decrypt
Regards,
Original Message:
Sent: 11-30-2020 11:17 AM
From: Joshua Johnson
Subject: 1080: No private key found : PGP Command Line
Ahmed,
To import keys into a user with no existing keyrings, you must first create the keyrings:
pgp --create-keyrings
Then import the key(s) you require
pgp --import key_file_name.asc
You can view imported keys on the keyring by issuing:
pgp --list-keys
Josh
Original Message:
Sent: 11-28-2020 08:31 PM
From: Ahmed Magdy
Subject: 1080: No private key found : PGP Command Line
Can I create a pgp command-line user with third party generated keys (using openssl for example) ?
I mean without using "pgp --gen-key "pgp --gen-key" .
So, I want to:
1-create user with no keys
2-give this user public and private keys that were generated using OpenSSL not pgp command-line.
If possible, kindly help with the required options from this guide
https://techdocs.broadcom.com/content/dam/broadcom/techdocs/symantec-security-software/information-security/pgp-solutions/10-4-2/generated-pdfs/pgpCmdline_usersguide_en.pdf
Original Message:
Sent: 12-07-2013 11:00 AM
From: Daniel Silva
Subject: 1080: No private key found : PGP Command Line
Hello kkhelawy,
That's correct. The private key should never leave the "hands" of the key owner. Otherwise it would be useless to encrypt data.
Encryption is done to the public key (which everyone can have access) and then only the private portion (of that same key pair) will be able to decrypt that data.
The only exception to the above line is when you encrypt to multiple public keys, then, any private key of those same keys can access the encrypted data. This is basically what does an Additional Decryption Key (ADK).
Regards,
dcats