RE: Installing Security Advisories
- From: Tino Engel <tino.engel@xxxxxxxxxxx>
- Date: Fri, 26 Oct 2007 23:15:22 +0100
Thank you very much for your quick response.
Here is what I did, as far as I can see exactly according to Security Advisory http://security.freebsd.org/advisories/FreeBSD-SA-07:08.openssl.asc.
openssl.patch 100% of 1051 B 6887 kBps
openssl.patch.asc 100% of 187 B 1325 kBps
Pretty Good Privacy(tm) Version 6.5.8
Internal development version only - not for general release.
(c) 1999 Network Associates Inc.
Export of this software may be restricted by the U.S. government.
File 'openssl.patch.asc' has signature, but with no text.
Text is assumed to be in file 'openssl.patch'.
Good signature from user "FreeBSD Security Officer <security-officer@xxxxxxxxxxx>".
Signature made 2007/10/03 21:48 GMT
WARNING: Because this public key is not certified with a trusted
signature, it is not known with high confidence that this public key
actually belongs to: "FreeBSD Security Officer <security-officer@xxxxxxxxxxx>".
%patch < /root/openssl.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
|RCS file: /home/ncvs/src/crypto/openssl/ssl/ssl_lib.c,v
|retrieving revision 220.127.116.11.2.1
|diff -u -d -r18.104.22.168.2.1 ssl_lib.c
|--- crypto/openssl/ssl/ssl_lib.c 28 Sep 2006 13:02:36 -0000 22.214.171.124.2.1
|+++ crypto/openssl/ssl/ssl_lib.c 3 Oct 2007 17:01:24 -0000
File to patch:
Now it comes up to the point where 'patch' is asking me which file to patch..
The security advisory tells nothing about this as far as I can see.
Actually I did not try cvsup/csup. One of the big advantages of FreeBSD is to me the easy Packages-System in sysinstall. Performance of KDE with all details is outstanding, so I see no need to compile the whole system from source. But maybe I will for the sake of it being cool...
And I striktly refuse to be weak-at-shell!!!! :-)
Best regards, Tino Engel
Subject: Re: Installing Security Advisories
Date: Fri, 26 Oct 2007 13:07:47 -0400
On Fri, 2007-10-26 at 17:42 +0100, Tino Engel wrote:
So how can I find out, which file to tell 'patch' to patch?
Why don't you paste the full input / output dialog from your patch
attempt and we will point out where you're making a syntactical error.
Manual patching is not for the weak-at-shell. Did you try to cvsup/csup
your source tree instead?
Eva sagt: „Kennst du schon den Adressimport für den Messenger?“
freebsd-questions@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: OpenLDAP 2.3/pam_ldap/nss_ldap: not working in FreeBSD 7.0-PRE!
- Next by Date: Re: OpenLDAP 2.3/pam_ldap/nss_ldap: not working in FreeBSD 7.0-PRE!
- Previous by thread: Re: Installing Security Advisories
- Next by thread: Re: Installing Security Advisories