SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
So, is that true? or in december we must re-run slackpkg update gpg?
All digital certificates expire after a certain date. This is because the technology to pose security risks to them can improve a lot between "computer generations".
The current GPG-KEY used by Slackware was issued on february, 2003. That one will expire on 21 december this year. This can be verified using the following command in a bash prompt: gpg --list-keys.
I made a "time change" test in a virtual machine with slack 13.37 and tried to verify a patch signature. It was ok, with return code
0 but also displayed a note saying "This key has expired!".
The question is: will Slackware-14 release a new GPG-KEY, so that all packages are signed with that "future-proof" certificate or will we stick with the current one?
Sticking with a 9 year old key a few months from expiration is at least strange for such a traditional secure distro, IMHO.
But I'm pretty sure Pat will answer us very soon :-)
The patches released in 2013 for slackware 13.37, which gpg-key will use?
If the GPG-KEY remains the same, after december 21st, it'll be impossible to sign anything with it. But it will be still possible to verify the old signatures.
I'm not a gpg especialist, but I'm sure there's a decent solution to that problem, maybe using subkeys.
Somewhat related to that end-of-the-world thing... Slackware 14 will have an easter egg which only becomes visible if you install Slackware 14 on 21 december, 2012...
Aak! I don't have access to my laptop today to reinstall Slackware 14.0! I won't see the Easter Egg! 'Tis the end of the world! :'(
I'm going to hazard a guess and say that the Easter Egg is a Mayan themed Lilo boot screen... even though I dreamt (can you believe it!) a while ago that the first boot would flash ASCII keys (yes, the ones that open doors) in place of the ASCII... things that appear during first boot. But I'm probably incorrect on both fronts. Has anyone seen the Easter Egg?