Hello,
I have a few questions regarding GnuPG.
1. Is secret key the most important part of GnuPG? By important I mean
if you only had your secret key could get back to your original setup
ignoring the imported public keys. My original setup included signing
and encryption key created along with t
On 19/10/14 11:48, Sudhir Khanger wrote:
> By important I mean
> if you only had your secret key could get back to your original setup
> ignoring the imported public keys.
Yes; also ignoring all assigned ownertrust values.
Public key and revocation certificate can be recreated; the latter is
usua
On 17/10/14 21:17, Sudhir Khanger wrote:
> What do you guys use to encrypt folders which may include audio, video
> and text files?
I'm still missing my favourite alternative in the suggestions.
device-mapper's dm-crypt target together with LUKS (Linux Unified Key
Setup). dm-crypt is somewhat the
On 19/10/14 00:56, Hauke Laging wrote:
> [...] having secring.gpg with
> rather weak passphrases on a cleartext backup volume)
> a) save the complete configuration (optionally protexted with a
> passphrase) to a single file
>
> gpg-backup --with-passphrase --save /path/to/targetfile
I'm not su
On 19.10.2014, Sudhir Khanger wrote:
> 1. Is secret key the most important part of GnuPG? By important I mean
> if you only had your secret key could get back to your original setup
> ignoring the imported public keys.
Of course, you can omit/delete your pubring.gpg, if you like. However, unless
On Sunday, October 19, 2014 01:22:07 PM you wrote:
> device-mapper's dm-crypt target together with LUKS (Linux Unified Key
> Setup). dm-crypt is somewhat the successor to encrypted loopback
> mentioned by Rob, and fixes some of the issues perceived in encrypted
> loopback. Some of those where subse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Sunday 19 October 2014 at 12:26:03 PM, in
, Heinz Diehl wrote:
> You can just copy your secring.gpg into your freshly
> installed ~/.gnupg directory. Importing your secret key
> would also re-install your public key..
In order to achieve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Sunday 19 October 2014 at 12:18:29 PM, in
, Peter Lebbing wrote:
> I'm fairly sure even certifications from other users
> are included in the private key,
I'd always thought this is not the case. Don't you re-reate the public
key from the
Am So 19.10.2014, 13:26:55 schrieb Peter Lebbing:
> > a) save the complete configuration (optionally protexted with a
> > passphrase) to a single file
> I'm not sure how you envision this, but wouldn't it be much easier,
> and sufficient, to have a prompt on startup that read:
>
> ***WARNING***
On Sunday, October 19, 2014 01:26:03 PM Heinz Diehl wrote:
> Of course, you can omit/delete your pubring.gpg, if you like. However,
> unless you import a public key, you won't be able to communicate using gpg
> encryption.
Are you trying to say if I don't import pubring.gpg I won't import the
pre
On Sunday, October 19, 2014 01:18:29 PM you wrote:
> On 19/10/14 11:48, Sudhir Khanger wrote:
> > By important I mean
> > if you only had your secret key could get back to your original setup
> > ignoring the imported public keys.
>
> Yes; also ignoring all assigned ownertrust values.
>
> Public
On 19.10.2014, m...@sudhirkhanger.com wrote:
> Are you trying to say if I don't import pubring.gpg I won't import the
> previously exchanged keys and hence I won't be able to send them encrypted
> messages as I won't have access to other people's public keys?
Exactly. In order to be able to se
On 19/10/14 15:32, Hauke Laging wrote:
> I am quite sure that this is the opposite of easier. Why?
>
> a) Because you have to change the passphrase of each secret key.
>
> b) Because you have to change them back after exporting.
It is clear you are not working on the same assumption as I did: th
I just saw this news story yesterday, and I wasn't sure if folks
around here already knew about it or not, but since the subject
of silly export restrictions had come up on this list recently,
I thought that I should share...
http://www.theregister.co.uk/2014/10/17/intel_subsidiary_crypto_export
On 19.10.2014, MFPA wrote:
> Importing your secret key would also re-install your public key..
> In order to achieve that, don't you have to run something like:-
>gpgsplit --secret-to-public YourPrivateKeyFile.asc
No, that's not neccessary.
A "gpg --import your_secret_key.asc" into a fres
On Sunday, October 19, 2014 08:26:54 PM Heinz Diehl wrote:
> > I am just learning GnuPG.
>
> You're welcome!
Just trying to develop good online habits.
> If you have to move your gpg installation to a new system, just copy the
> secring.gpg, pubring.gpg, trustdb.gpg and gpg.conf from your ~/.gnu
Am So 19.10.2014, 21:10:20 schrieb Peter Lebbing:
> It is clear you are not working on the same assumption as I did: that
> there were already good passphrases on the keys, because this is
> simply good practice
A good passphrase doesn't help against online attacks. The usual
protection against
> I just saw this news story yesterday, and I wasn't sure if folks
> around here already knew about it or not, but since the subject
> of silly export restrictions had come up on this list recently,
> I thought that I should share...
It was brought up and discussed at length less than two days ago
18 matches
Mail list logo
