similar to: portsnap not updating

I''ve posted a FreeBSD portsnap class for those wanting to automate the use of portsnap for ports maintenance (fetch, extraction, cron, and update). http://reductivelabs.com/trac/puppet/wiki/PuppetFreeBSD#portsnap ## EXAMPLE import ''freebsd.pp'' import ''schedule.pp'' node ''freebsd.local'' { include freebsd::portsnap } ## END

freebsd-security-request@freebsd.org wrote: > Send freebsd-security mailing list submissions to > freebsd-security@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-security > or, via email, send a message with subject or body 'help' to > freebsd-security-request@freebsd.org > > You

Dear FreeBSD users, Slightly more than three years ago, I released FreeBSD Update, my first major contribution to FreeBSD. Since then, I have become a FreeBSD committer, joined the FreeBSD Security Team, released Portsnap, and become the FreeBSD Security Officer. However, as I have gone from being a graduate student at Oxford University -- busy writing my thesis -- to a researcher at Simon

CVSup is slow, insecure, and a memory hog. However, until now it's been the only option for keeping an up-to-date ports tree, and (thanks to all of the recent work on vuxml and portaudit) it has become quite obvious that keeping an up-to-date ports tree is very important. To provide a secure, lightweight, and fast alternative to CVSup, I've written portsnap. As the name suggests, this

I have been using Freebsd for along time. I have a client of mine that wants me to use Centos for his email server and web server. Anyway with Freebsd to update the packages file you use the following commands. portsnap fetch fetches all the current port trees portsnap update adds all the new ports to the tree on the server portupgrade -arR will install all the ports that are installed on the

Hi, I am profiling some workloads for the voluntary and involuntary context switches. I am interested in finding out the reasons causing these two types of context switches. As far as I understand, involuntary context switch happens on expiration of time slice or when a higher priority process comes in. While the voluntary switch generally happens when a process is waiting for I/O etc. So to

lol - yep when news of this first broke I thought thats actually a very good idea to have implemented, though it sounds the way Trixbox implemented it may have been unsecure. Maybe someone else can come up with a better way of implementing this. If the data was all randomised there's no harm in doing this; some basic infomration like; Hours of uptime Reboots Number of extensions Number of

We are currently using cvs for both source and ports. I have begun changing to portsnap for ports, and I would also like to try changing at least some of our servers to freebsd-update. But all servers have been patched, using either RELENG_8_3 or RELENG_9_0 as cvs tag. I need to revert them to their respective RELEASE to be able to use freebsd-update. Complete reinstall from eg CD is not an

anyone knows what to do? [root at rock]# freebsd-update -r 9.1-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Inspecting system... done. The following components of FreeBSD seem to be installed:

Hi list, after the security announcement (http://www.freebsd.org/news/2012-compromise.html) I use svn to update my local ports tree. I've found out that the port index is not updated. What is the preferred/recommended way to update port indexes when using svn? Thanks, Serguey.

Hi ! All MP3 radio stations have disappeared from dir.xiph.org... Is this a bug or is this voluntary ?! Thanks, yomguy

I am getting a-mail with security run output from one of my 9.2-RELEASE servers whose primary role is mysql server: sql1.kappastar.com login failures: Nov 18 02:11:09 sql1 sshd[58619]: Invalid user this-is-not-an-attack from 188.95.234.6 Nov 18 02:11:17 sql1 sshd[58621]: Invalid user this-is-not-an-attack from 188.95.234.6 Nov 18 04:54:10 sql1 sshd [59190]: reverse mapping checking getaddrinfo

Hi FreeBSD Community, i got warning that 9.1RC3 is approaching end of its life, i should upgrade with in two week. when i started the upgrade, i get the following error. any solution anyone knows? [root at rock]# freebsd-update -r 9.1-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done. Fetching

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic

Ports and Package users, Ports now have SSP enabled by default. The package repository will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses.

Ports and Package users, Ports now have SSP enabled by default. The package repository will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses.

Ports and Package users, Ports now have SSP enabled by default. The package repository will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses.

Dear members, It may sound a silly question. I have curl installed: # pkg_info |grep curl curl-7.24.0_3 Non-interactive tool to get files from FTP, GOPHER, HTTP(S) Today portsnap updated the ftp/curl port, and patch-CVE-2013-2174 appeared in files/, but the port version remained such that portaudit, and portupgrade still complain about curl's version. What is the recommended way to

I realise that Samba is a voluntary effort and keeping Web Sites upto date may not be everyone's favourite occupation, but there appear to be a number of things missing or wrong: a) There is no contact info for the WebSite I could discern - hence posting here. b) There is still reference to samba-bugs@samba.org address - which I have been informed by it, is now dead. So may be this could be

Hi Quick question about something I find surprising: In tdb mode : net cache list -s /etc/samba/smb.conf |grep '\-513' Key: IDMAP/GID2SID/100?? ? Timeout: Tue Apr? 9 14:34:48 2024 Value: S-1-5-21-1040823229-2152490729-3717368692-513 id of group "domain users" is?100 But id 100 use by "users" system group: getent group|grep users users:x:100: Is this something