[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[suse-security] RE: why is new sax2 (8.1) missing SuSE build key ?
I just downloaded from two rpms for my 8.1 box, namely:
The first rpm was an October 2002 build labeled "sax2-4.7-171.i586.rpm"
and it was signed by the "SuSE Package Signing Key <build@xxxxxxx>",
whereas the second, labeled "sax2-4.7-440.i586.rpm" (a July 2nd 2003 build)
had only a MD5 (MD5 sum OK: bc3d052924097f8266b9f1a147015026)
when I checked it using rpm -v --checksig.
It appears that both packages were created by you.
Can you shead any light on why this is so??
In the Beginning was the Command Line
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
Get AOL Instant Messenger 5.1 free of charge. Download Now!
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here