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.
pub 1024D/3D11E4FF 2007-06-02
uid chalkroot (another test key, with password) <root@noemail.org>
sub 1024g/76E9FC59 2007-06-02
There is the snip from my gpg used in example above. The --recipient is the name in bold (uid line) of each public key. So you should have a greg (info) <gregs@email.com> line there if you intend to encrypt it to greg.
try gpg --sign-key greg
see if that gives you an error. signing that key basically states you trust that key belongs to greg.
Hi troybtj,
My cron file log generated looks like this,
gpg: using secondary key 158416E1 instead of primary key 53812876
gpg: 158416E1: There is no indication that this key really belongs to the owner
gpg: cannot open /dev/tty: No such device or address
Hi,
i sorted the problem after a long while,
run the script using crontab -e instead of directly putiing it in /etc/crontab, it some how sets up the environment variables correctly
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.