Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm working on this project, wherein a gpg-encrypted file is being generated and transmitted from one end and is being received and processed on another end. I work on the receiving end, and I already have the decryption part working by entering a passphrase.
But, what really would be the problem if I don't put passphrase to my private key? It sounds like a security concern to me, but I don't understand why in a technical way.
Distribution: Ubuntu, Debian, Fedora, Oracle Linux
Posts: 109
Rep:
The password protect your (private) key encryting it.
This to prevent extraction|access|use to your protected content.
For example, someone (with access to your box) could get your private key (gpg --export-secret-key [keyId]) and do what you can do with that ... it would not be a great scenario :-(
The password protect your (private) key encryting it.
This to prevent extraction|access|use to your protected content.
For example, someone (with access to your box) could get your private key (gpg --export-secret-key [keyId]) and do what you can do with that ... it would not be a great scenario :-(
But, if the key is only in my keyring, the other user would not be able to see and export the private key, right?
I mean, when the other user does [gpg --list-secret-keys] and does not see my privkey001, he would not be able to export the key using [gpg --export-secret-key privkey001], right?
Distribution: Ubuntu, Debian, Fedora, Oracle Linux
Posts: 109
Rep:
Yes, sure, you're right ... she/he would be able in case you set up correctly the directory grants of your .gnupg directory (and contained files) or she/he cannot be root onto your box.... ;-)
It really is "up to you." You might, for example, be dealing strictly with an "internal-only" connection between two systems that are well-known to one another and fairly easy for you to control. Passphrases (encryption ...) might truly be superfluous in such a case.
The primary layer of protection is simply that ... "you must possess the key." The key should be unique, and installed on exactly one machine, and it should be impossible to make a connection to that box without possession of that key. If you do all of these things, and judge that you truly are able to control physical possession of the key, then you might well conclude that a passphrase is of no real added-value.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.