similar to: Security-officer PGP Key?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hello all, I hope someone can help me with this issue, I have the SVN file_column and using LoginEngine/UserEngine with Rails 1.1.2. My issue is that I''m overloading the view for LoginEngine to support a file image upload as part of the user record and having a heck of a time doing so. Near the bottom of my new _edit.rhtml

Hello, I have scheduled a birds-of-a-feather (BoF) meeting at BSDcon to discuss the FreeBSD Security Officer role. Details such as time, location, and topics are posted on the BSDcon unofficial Wiki <URL: http://bsdcon.kwiki.org/index.cgi?FreeBSDSecurityOfficerBoF >. Please attend if you are interested in what the SO team does currently and in participating in and improving its

Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent releases and EoL (end-of-life) events. The new list is below (and should appear at <URL: http://www.freebsd.org/security/ > soon). In particular, FreeBSD 4.6 and FreeBSD 5.0 have `expired'. If you wish to be certain to get critical bug fixes, it is recommended that you upgrade

Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://www.freebsd.org/security/ >. FreeBSD 4.8 has `expired' and is no longer supported effective April 1, 2005. Also note that FreeBSD 4.9 ceased to be supported on November 1, 2004. If you are running FreeBSD 4.8

Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below (and should appear at <URL: http://www.freebsd.org/security/ > soon). FreeBSD 4.7 has `expired', but I have extended the EoL date for FreeBSD 5.1. If you are running FreeBSD 4.7 or older and you wish to be certain to get critical

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 5.3 and FreeBSD 5.4 have `expired' and are no longer supported effective November 1, 2006. The end-of-life date for FreeBSD 6.0 has

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 5.3 and FreeBSD 5.4 have `expired' and are no longer supported effective November 1, 2006. The end-of-life date for FreeBSD 6.0 has

The FreeBSD Security Officer would normally be sending out this email, but he's a bit busy right now and it is clear from reactions to FreeBSD Security Advisory FreeBSD-SA-04:04.tcp that many people are unaware of the current status of the RELENG_5_1 branch, so I'm going to send out this reminder myself. The branches supported by the FreeBSD Security Officer have been updated to reflect

Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://www.freebsd.org/security/ >. FreeBSD 5.2.1 has `expired' and is no longer supported effective January 1, 2005. Also note that FreeBSD 4.9 ceased to be supported on November 1, 2004, while FreeBSD 4.8 will

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://www.freebsd.org/security/ >. FreeBSD 4.10 has `expired' and is no longer supported effective June 1, 2006. Also note that FreeBSD 5.3 and FreeBSD 5.4 will cease to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://www.freebsd.org/security/ >. FreeBSD 4.10 has `expired' and is no longer supported effective June 1, 2006. Also note that FreeBSD 5.3 and FreeBSD 5.4 will cease to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 4.11 and FreeBSD 6.0 have `expired' and are no longer supported effective February 1, 2007. Discussions concerning FreeBSD releases

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

On Sunday, 06 January 2008, Akemi Yagi wrote: <snip> > Question: What rpm > command do I use, to Import the Public Key that's in the browser > window? Or, if I need more than one command, what are they? You should wget that file and run the rpm command as instructed in that wiki. Akemi: Having the proper command did the trick! Thanks a million! It's installed. :-) Lanny

Can you send a PGP file over FTPS, and which Centos FTP daemon option supports this?

Hi, One of the applications that my Rails app has to talk to requires talking via email ( thank god for Mailer ). The problem is that the emails need to be pgp signed... I was wondering if anyone had ever used pgp signatures within a Rails app? Thanks in advance! -- Posted via http://www.ruby-forum.com/.

Dear all! I'd like to know if something changed for pgp263i on amd64. In ports, archs recommended are i386 and alpha. Has someone used gpg-idea port (with idea and rsa) to circum- vent pgp <-> gpg missmetch? Best regards Zoran

Hi, I have to apologise: I edited a moderator comment into a message that was pgp-signed. I must say that I normally notice the PGP signature and put comments on those messages in the end, but I must have missed it this time. I''m sorry for the confusion that this must''ve caused. Roger.

Paul Johnson wrote: > On Thursday 13 March 2008 01:27:23 pm Paul Johnson wrote: > > > -------------- next part -------------- > > A non-text attachment was scrubbed... > > Name: not available > > Type: application/pgp-signature > > Size: 189 bytes > > Desc: This is a digitally signed message part. > > Url : > >