similar to: [Announce] Samba 4.0.2, 3.6.12 and 3.5.21 Security Releases Available for Download

Release Announcements ===================== Samba 3.5.10, 3.4.14 and 3.3.16 are security releases in order to address CVE-2011-2522 (Cross-Site Request Forgery in SWAT) and CVE-2011-2694 (Cross-Site Scripting vulnerability in SWAT). o CVE-2011-2522: The Samba Web Administration Tool (SWAT) in Samba versions 3.0.x to 3.5.9 are affected by a cross-site request forgery. o CVE-2011-2694:

Release Announcements ===================== Samba 3.5.10, 3.4.14 and 3.3.16 are security releases in order to address CVE-2011-2522 (Cross-Site Request Forgery in SWAT) and CVE-2011-2694 (Cross-Site Scripting vulnerability in SWAT). o CVE-2011-2522: The Samba Web Administration Tool (SWAT) in Samba versions 3.0.x to 3.5.9 are affected by a cross-site request forgery. o CVE-2011-2694:

Hey Samba list. We recently had to switch from 3.5.x to 3.6, due to the ports tree dropping 3.5 Since then, I've have had issues with the looking up users consistently. It may work for 30 minutes, and then stop. I finally started to run winbindd -i -d and here are some of my findings: Environment: OS: FreeBSD 9.1-RELEASE uname -a: FreeBSD pkg-server 9.1-RELEASE FreeBSD 9.1-RELEASE #0

Hi everyone, In the last few days I've spended hours and hours on the web surching for a solution to my problems. Eventhough it looked like there where several other people having the same problem I couldn't find a way to solve it. Therefore I'm hoping that one of you could help me with the following problem. I've installed Samba 3.0.14a on RedHat 9.0. Samba is working perfectly.

Dear samba-ers, I have installed SWAT so that my samba users can change their passwords easily and remotely as they do not have login access to the samba server. Broadly speaking my problem is that when registered as a user, it seems that swat cannot access the file /var/lib/samba/private/secrets.tdb Version info: Linux platform: CentOS 6.5 Linux Kernel: 2.6.32-431 Samba: 3.6.9-167.el6_5

I have downloaded, build and installed samba-4.0.9 from source on two separate boxes running RHEL6.4. My problem is that despite having identical configurations, swat is running on one server and not on the other. Here is my xinetd conf service swat { port = 901 socket_type = stream wait = no only_from = 192.168.1.0/24 user = root server =

Hello All Samba-list Members, I have installed a Samba 2.2.7, the samba-latest.tar.gz, as a PDC on a Redhat8.0 GNU/Linux server. ( Of course, I first uninstalled the original samba that came with the Redhat installation CDs by rpm -e samba*.) The installation was successful. Then I modified /etc/services and /etc/xinetd.d/swat as suggested in the installation document uncompressed from

Hi Sean, I had this problem when I upgraded our servers to RedHat 7. In RedHat 7 they changed from running the inetd.d to running xinetd.d. This is the daemon that figures out what programs to start when a port is accessed. Port 901 is for swat, this is configured in your /etc/services file. In the /etc/xinetd.d/ directory you'll find a file called swat. Edit this file so it looks

hola, habla usted ingles? bueno, revise bien que 'xinetd' este instalado y corriedo como servicio: ps -ae | grep xinetd si resulta que si, entonces revise el documento de configuracion de swat (/etc/xinetd.d/swat): # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ # connect to port 901

Hello: I have samba-2.2.5-1 running in RedHat 7.3, but I get the page cannot be displayed message when I go to http://sambaserver:901 My /etc/etc/xinetd.d/swat file looks as below. I have removed only_from = localhost and changed disable = yes to no service swat { port = 901 socket_type = stream wait = no user = root server = /usr/sbin/swat

On Mon, 5 May 2003, Anthony Watters wrote: > Since I have Samba working already, is there a way to install just SWAT? ie; > *.tar.gz file? No need if you have already installed the SWAT RPM. > > I did also try and re-install the RPM file samba-swat-2.2.7a.9.0.i386.rpm > using the rpm manager. it seemed to take 5 seconds, so I am not sure what > really occurred other than SWAT

Ok, I should be able to start swat with xinetd, but I can't seem to get anything to start. 1. How do I tell if swat is running (other than trying to browse to aaa.bbb.ccc.ddd:901) 2. Can someone give me an idea of what and where I need commands for xinetd. Server is RH7.2, Samba 2.2.3a, following file "swat" is in /etc/xinetd.d/ ## /etc/xinetd.d/swat service swat { port

IT WORKS!!!!!!!!!!! But before I say what I did... yall have to promise not to laugh! (MAH!! I HEAR YOU!!) ... anyone ever heard of.... /etc/rc.d/init.d/xinetd restart I can tell you from experience that 'killall -HUP xinetd' is NOT the same. I can also say that nobody will find that command line entry in "Using Samba". To show my appreciation to the groups involved,

Okay, here's what you need to do. You have to configure apache. This won't be too hard. You will need to edit the httpd.conf located in /etc/httpd/conf directory. Look through the httpd.conf file until you find this line: #Servername localhost It may or may not have the # in front of it. You need to edit this line and make it say: Servername yourservernamegoeshere For example,

Hello, I have recently updated the Samba 3.6.14 to 3.6.21 on a Gentoo server PACKAGE.USE = net-fs/samba acl aio caps client ldap netapi pam readline server smbclient winbind -addns -ads -avahi -cluster -cups debug -dmapi doc -examples fam -ldb quo 1st issue I cannot get SWAT to connect using my Windows 7 PC to my linux samba server using (http//:ip_address of samba server:901 I have port 901 open

Hitting a big mystery here. I've configured samba properly but I would like to run swat. The /etc/xinetd.d/swat file contains: service swat { disable = no port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure +=

I'm having problems validating when using swat on the localhost. The server is RH Linux 7.3. I'm using encrypted passwords and I'm able to connect to points using Windows products, etc; however, when I http://localhost:901, I get the login dialog, but it won't accept the root account or password. It tells me that the "Authorization failed". I did configure the

Did an upgrade from samba 3.4.6 to 3.5.2 Left the smb.conf completely unchanged. As background I'm using samba on gentoo amd64 with a ldapsam backend on openldap. Upgrade went well, I thought. Users could login and access their home directories. Service reloaded without issue. Here was the issue though, windows 2003 servers couldn't login users into the domain. These servers were

Hello all: Here's the problem [on a RH7 running kernel 2.2.17-14 with Samba 2.0.7-21ssl and xinetd-2.1.8.9pre14]: http://localhost:901 does bring up the SWAT login dialog box.. but upon entering root as the user, followed by my root passwd in the next entry... it tells me "Authentication failed. Retry?" I can tell you that I did enter the correct root passwd, because I am root

Sorry for the direct post.... Eric Hines -------- Original Message -------- Subject: Re: [Samba] can't connect to swat Date: Sun, 16 Apr 2006 08:51:45 -0500 From: EHines <eehines@comcast.net> To: Larry Weldon <lweldon@weldoncomputers.com> References: <02a201c66148$c8925290$0c46a8c0@jshinotebook> <1145194206.20034.72.camel@tiger.home.welcoin.com> Larry Weldon