search for: wadhams

...;s hand through changing their PIN, recording their name, and setting up one or both greetings, the very first time they use the account. I know I can publish docs that tell them how to use the "0" menu and do this by hand... but users are lazy and resent documentation. Thanks! Jeremy Wadhams Yahoo Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070914/b45c07c5/attachment.htm

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

...change in the line-up for the show, that I think bears mentioning here since it possibly will help quite a few of you in your discussions about getting Asterisk into your company. We've had the good fortune to have a last-minute keynote addition at the show, which is going to be Jeremy Wadhams from Yahoo. He's going to be talking about a Fortune 500 implementation of Asterisk across their entire network, and why they made the decision to move to Open- Source telephony for the core of their voice network. Keynote: 3:30 - 4:00 PM on Wednesday - Jeremy Wadhams, Yahoo It's...

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

How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that can't do PAM, perhaps NIS is the way to go (assuming, of course, you're behind a firewall). You can store login information in LDAP like you want, then use a home-grown script to extract the information to a NIS map. Or, if you have a Solaris 8 machine lying around, you can cut out the middle step and use

http://bugs.freedesktop.org/show_bug.cgi?id=23505 Summary: KDE's Kubrick has problems with xf86-video-nouveau driver Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

We're being ping-flooded by the Nachi worm, which probes subnets for systems to attack by sending 92-byte ping packets. Unfortunately, IPFW doesn't seem to have the ability to filter packets by length. Assuming that I stick with IPFW, what's the best way to stem the tide? --Brett Glass

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

The mailing list detained my email because I posted from the wrong address... hoepfully it will get through this time. -------- Original Message -------- Subject: Re: Fwd: FreeBSD hiding security stuff Date: Fri, 04 Mar 2005 05:35:32 -0800 From: Colin Percival <cperciva@freebsd.org> To: Devon H. O'Dell <dodell@sitetronics.com> CC: mike@sentex.net, freebsd-security@freebsd.org,

In response to popular demand, I am now providing both GENERIC and SMP kernels via FreeBSD Update to people running FreeBSD 5.3. To take advantage of this on your FreeBSD 5.3 (and only 5.3!) SMP system, run the following commands as root: # touch /boot/kernel/SMP # freebsd-update fetch (this should mention downloading a new /boot/kernel/SMP file) # freebsd-update install (likewise, this should

Several people have noticed that SecuriTeam.com is reporting a "FreeBSD ECE flag ipfw protection bypass" exploit. In an effort to save time, let me say this publicly: SecuriTeam.com is three years out of date. This problem was fixed in FreeBSD 3.5-STABLE and 4.2-STABLE in January 2001, and reported in Security Advisory FreeBSD-SA-01:08. Colin Percival

In order to provide an easy update path for i386 systems from FreeBSD 5.2 to FreeBSD 5.2.1, FreeBSD Update will now update systems running FreeBSD 5.2-RELEASE to 5.2.1-RELEASE. To take advantage of these updates, install and run FreeBSD Update, and reboot into the new kernel: # cd /usr/ports/security/freebsd-update && make install clean # cp /usr/local/etc/freebsd-update.conf.sample

I am now building binary security updates for FreeBSD 5.x, for use with FreeBSD Update. This has taken rather longer than I expected -- I thought I would be at this point in mid-November -- but porting the update-building code to run on FreeBSD 5.x took rather longer than I expected. For details about how to use these updates, please see the FreeBSD Update web site at

Topic: Potential failure to update vulnerable files Synopsis: FreeBSD Update is a system for tracking FreeBSD release (aka security) branches via signed binary updates. At present, updates are being built for FreeBSD 4.7-RELEASE and 4.8-RELEASE. As a result of differences between the ISO image and FTP distributions of 4.7-RELEASE, FreeBSD Update may have failed to recognize certain

Is there any reason why releases have EoL dates after only 12 months? While it's clear that some sort of EoL is important, I can't think of any security advisories recently which weren't accompanied by patches for all the security branches, even those which are no longer officially supported. Colin Percival

Well, I *tried* to CC: freebsd-security... I'm forwarding this to get around the "posting from wrong address" filter. -------- Original Message -------- Subject: Re: FW:FreeBSD hiding security stuff Date: Fri, 04 Mar 2005 04:42:48 -0800 From: Colin Percival <cperciva@freebsd.org> To: Jonathan Weiss <tomonage2@gmx.de> CC: freebsd-security@freebsd.org, FreeBSD-Hackers

It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite popular, so I've started building an SMP kernel for FreeBSD 5.4 as well, in addition to the usual GENERIC kernel. To take advantage of this on your FreeBSD 5.4 SMP system, run the following commands as root: # touch /boot/kernel/SMP # freebsd-update fetch # freebsd-update install # echo 'bootfile="SMP"'

At the end of March, the RELENG_4_8 (sometimes called 4.8-SECURITY) branch will reach its designated End of Life and cease to be supported by the FreeBSD Security Team. Released in April 2003, FreeBSD 4.8 was the first release designated for "extended" two-year security support instead of the normal one-year support. Over this time, 27 security advisories have been issued which have