similar to: Samba 3.0.9 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several important issues fixes since the 3.0.8 release. Common bugs fixed in 3.0.9 include: ~ o Problem updating roaming user profiles. ~ o Crash in smbd when printing from a Windows 9x client.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Possible remote code execution == CVE ID#: CAN-2004-1154 == == Versions: Samba 2.x & 3.0.x <= 3.0.9 == == Summary: A potential integer overflow when == unmarshalling specific MS-RPC requests == from clients could lead to heap == corruption and remote code execution.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Possible remote code execution == CVE ID#: CAN-2004-1154 == == Versions: Samba 2.x & 3.0.x <= 3.0.9 == == Summary: A potential integer overflow when == unmarshalling specific MS-RPC requests == from clients could lead to heap == corruption and remote code execution.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba; the version that production Samba servers should be running for all current bug-fixes. There have been several important issues fixes since the 3.0.7 release. Common bugs fixed in 3.0.8 include: ~ o Compile fixes for HP-UX ~ o Fixes for the printer publishing code used when joined to ~ an AD domain.

Hi, I have two Linux systems, one running FC2 and the other Mandrake 10.1. When I tried installing Samba 3.0.11 on both the systems, I get the following error: # rpm -i samba-3.0.11-1.i386.rpm samba-common-3.0.11-1.i386.rpm warning: samba-3.0.11-1.i386.rpm: V3 DSA signature: NOKEY, key ID f17f9772 error: Failed dependencies: liblber-2.2.so.7 is needed by samba-3.0.11-1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba; the version that production Samba servers should be running for all current bug-fixes. There have been several important issues fixes since the 3.0.7 release. Common bugs fixed in 3.0.8 include: ~ o Compile fixes for HP-UX ~ o Fixes for the printer publishing code used when joined to ~ an AD domain.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. This is primarily a security release to address CAN-2004-1154. The uncompressed tarball and patch file have been signed using GnuPG. The source code and the Samba public key (ID F17F9772) can be downloaded

Hi fellow Icecasters, We just released a new version of Cool Mic (v1.2.2), a GPLv3 Icecast source client for Android. There are a new features and improvements in this release. You can download it directly from Google Play or go to our website and download the APK directly. It will also be updated soon on the F-Droid app repository. We hope you enjoy it! https://coolmic.net Sincerely, Jordan

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After having upgraded my W2K clients with SP4, i'm unable to access the [netlogon] share. A look at the <machinename>.log file says: [2003/09/01 16:44:59, 0] smbd/service.c:make_connection(528) make_connection: connection to netlogon denied due to security descriptor. The netlogon share (if set browseable) is visible from clients, in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate of the Samba 3.0.11 code base and is provided for testing only. While close to the final stable release, this snapshot is *not* intended for production servers. If all goes well, this this version will become the final 3.0.11 stable release (with possible minor changes). Common bugs fixed in 3.0.11rc1 include: ~ o

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate of the Samba 3.0.11 code base and is provided for testing only. While close to the final stable release, this snapshot is *not* intended for production servers. If all goes well, this this version will become the final 3.0.11 stable release (with possible minor changes). Common bugs fixed in 3.0.11rc1 include: ~ o

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. Using inAccess Networks chan_oh323, I'm experiencing some clicks or pops, how can I fix that? - -- Regards, Tais M. Hansen ComX Networks Tel: +45-70257474 Fax: +45-70257374 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/QMfF2TEAILET3McRAu9zAJwNWtv+QSpka0NGaVk9E/IDHyalhwCgkQME Gynfp5zF0SWZUQEjelp7sBI= =CSqT

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.11 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes since 3.0.10 that we feel are important to make available to the Samba community for wider testing. Common bugs fixed in 3.0.11pre1 include: ~ o Numerous

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.11 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes since 3.0.10 that we feel are important to make available to the Samba community for wider testing. Common bugs fixed in 3.0.11pre1 include: ~ o Numerous

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== I feel like I'm waiting on some event before I grow up. Please wake me up so I don't miss it. -- anonymous ============================================================== Release Announcements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I have a simple question about incoming phone line rollovers. How are these usually done? Is this done at the phone company usually, or is this something that Asterisk or channel bank is capable of? I just need someone to give me a brief explanation how it usually works, and if someone was implementing an Asterisk system, how they would go

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, listers I managed how to fix the issue caused by upgrading W2k clients to SP4 (no domain logins, no profiles, no netlogon). It's been a nice week-end as you can figure... :) I resume here the steps i've done so far. SERVER SIDE: /etc/samba/smb.conf: [global] ; basic server settings workgroup = uagb netbios name = malaussene

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Now that I've been unable to register 2 hardware SIP phones and one software (Kphone), I'm beginning to doubt that chan_sip works at all. - -- Regards, Tais M. Hansen ComX Networks Tel: +45-70257474 Fax: +45-70257374 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After upgrading the kernel on an Asterisk box, asterisk segfaults on startup. It seems like it's the g729 codec that causes this: #0 0x4015acad in memset () from /lib/libc.so.6 #1 0x4022686a in load_module () at codec_g729b.c:416 #2 0x08054794 in ast_load_resource (resource_name=0x80d1068 "codec_g729b.so") at loader.c:298 #3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. Yesterday I had the funny idea of upgrading all my Windows 2000 Professional worksations (20 W2k boxes more or less) to SP4. I run Samba 2.2.8a on a glorious RedHat 6.2, and after the endless download-and-reboot I found with no W2K client able to logging in. I skimmed the mail archives, tried a bunch of suggestion from really a lot of