improve GnuPG configuration file /etc/skel/.gnupg/gpg.conf #223

Activity

3. adrelanos commented on May 28, 2024

   

   adrelanos

   on May 28, 2024

   ContributorAuthor

   More actions

   Unless using live mode, writing to RAM is too difficult for users.

   /tmp isn't guaranteeing that nothing is written to the disk. (Swap, crash dumps. This goes into the topic of anti-forensics. In short: forget about it and use live mode.)

   But what is the point of writing to RAM anyhow in this context? The private key needs to be stored persistently somewhere anyhow.
6. ben-grande commented on Jun 12, 2024

   

   ben-grande

   on Jun 12, 2024

   Contributor

   More actions

   Another hardend GnuPG configuration:

   • https://gist.github.com/sebmellen/b0d0424caefa1221cbe4d9aaf2172d2c
7. ben-grande commented on Jul 1, 2024

   

   ben-grande

   on Jul 1, 2024

   Contributor

   More actions

   Thats many years old and wonder if key size beyond 4096 are really more secure at this point?

   1. Many years old and still newer than the currently used gpg.conf.
   2. I didn't say to trust everything in that file, it has outdated settings, yes, but it has many valuable ones.
9. adrelanos commented on Jun 22, 2025

   

   adrelanos

   on Jun 22, 2025

   ContributorAuthor

   More actions

   AI generated?
11. adrelanos commented on Sep 16, 2025

    

    adrelanos

    on Sep 16, 2025

    ContributorAuthor

    More actions

    Our plan during the Kicksecure 18 release cycle is to port to Sequoia-PGP.