SlackwareThis Forum is for the discussion of Slackware Linux.
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.
The Easter egg is that the Mayan LILO bootsplash will be installed...
Code:
# Mayan calendar easter egg
if [ "$(date "+%Y%m%d")" = "20121221" ]; then
if [ -r $LILODOCDIR/sample/slack14.0.2012.bmp ]; then
cp -a $LILODOCDIR/sample/slack14.0.2012.bmp /boot/slack.bmp
fi
fi
tomorrow change date to your computer and reinstall
Of course, I was right. As if I could ever be wrong... although my dreams seem prone to error...
Unfortunately I tried changing the date and installing, but to no avail. Looking at the code for liloconfig, I get the impression it's because I use Slackware64. Or maybe Bob got annoyed at me for trying to cheat. Anyway, I decided to track down the picture on the Slackware64 DVD and force the issue. 'Tis a pretty Lilo splash!
If a GPG key's expiry date is updated, then files which were signed with the old version of the GPG key will still validate OK.
I'll let you in on a secret:
Code:
$ gpg --refresh-keys
$ gpg --list-keys "Slackware Linux Project"
pub 1024D/40102233 2003-02-26 [expires: 2038-01-19]
uid Slackware Linux Project <security@slackware.com>
sub 1024g/4E523569 2003-02-26 [expires: 2038-01-19]
$ gpg --verify ~ftp/pub/Linux/Slackware/slackware-13.37/CHECKSUMS.md5.asc
gpg: Signature made Mon 25 Apr 2011 04:56:55 PM CEST using DSA key ID 40102233
gpg: Good signature from "Slackware Linux Project <security@slackware.com>"
Eric
But slackpkg automatically does not refresh the key:
Code:
# slackpkg update gpg
Downloading http://ftp.osuosl.org/.2/slackware/slackware64-13.37/GPG-KEY...
--2013-01-04 16:27:26-- http://ftp.osuosl.org/.2/slackware/slackware64-13.37/GPG-KEY
Resolving ftp.osuosl.org (ftp.osuosl.org)... 140.211.166.134
Connecting to ftp.osuosl.org (ftp.osuosl.org)|140.211.166.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1565 (1.5K) [text/plain]
Saving to: '/tmp/slackpkg.mi3WC6/gpgkey'
100%[========================================>] 1,565 --.-K/s in 0s
2013-01-04 16:27:27 (105 MB/s) - '/tmp/slackpkg.mi3WC6/gpgkey' saved [1565/1565]
Slackware Linux Project's GPG key added
root@matteo:~# gpg --list-keys "Slackware Linux Project"
pub 1024D/40102233 2003-02-26 [expired: 2012-12-21]
uid Slackware Linux Project <security@slackware.com>
But slackpkg automatically does not refresh the key:
Code:
# slackpkg update gpg
Downloading http://ftp.osuosl.org/.2/slackware/slackware64-13.37/GPG-KEY...
--2013-01-04 16:27:26-- http://ftp.osuosl.org/.2/slackware/slackware64-13.37/GPG-KEY
Resolving ftp.osuosl.org (ftp.osuosl.org)... 140.211.166.134
Connecting to ftp.osuosl.org (ftp.osuosl.org)|140.211.166.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1565 (1.5K) [text/plain]
Saving to: '/tmp/slackpkg.mi3WC6/gpgkey'
100%[========================================>] 1,565 --.-K/s in 0s
2013-01-04 16:27:27 (105 MB/s) - '/tmp/slackpkg.mi3WC6/gpgkey' saved [1565/1565]
Slackware Linux Project's GPG key added
root@matteo:~# gpg --list-keys "Slackware Linux Project"
pub 1024D/40102233 2003-02-26 [expired: 2012-12-21]
uid Slackware Linux Project <security@slackware.com>
Oh, but it does!
However, the Slackware GPG key has only been updated in the Slackware 14.0 tree. You pointed slackpkg to a Slackware 13.37 mirror which still has the old key.
zerouno, let me explain again what I meant to say.
The command "slackpkg update gpg" will regresh the Slackware GPG key. It will download the GPG-KEY file from the mirror you have configured, for the Slackware release which you have configured. If that GPG-KEY file contains an expired key (which is the case with all Slackware releases before 14.0) then slackpkg will happily "refresh" the GPG key with that same expired key. Slackpkg does not check for expiration of the key!
Your (and mine) idea of "refreshing" is refreshing a key using a keyserver. This is not what "slackpkg update gpg" does.
I have asked Pat Volkerding to update the GPG-KEY file on all Slackware mirror releases for 13.37 and earlier, let's wait and see if he does that.
Code:
Seeing the code:
Code:
function checkgpg() {
gpg --verify ${1}.asc ${1} 2>/dev/null && echo "1" || echo "0"
}
slackpkg does not show any warning becouse '2>/dev/null' is present.
Removing it slackpkg show the warning.
The need to remove that "2>/dev/null" is arguable. If the key verification fails, this function will return a "0" to the calling routine. This return code is checked and you will get a GPG verification error on your screen. I agree that you will not see the reason for the failure because the key expiration message is filtered out by that "2>/dev/null" redirection.
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...
Eric
Has anyone installed on 21 december 2012? What was the easter egg?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.