similar to: Security Release - Samba 3.0.5 and 2.2.10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Summary: Potential Buffer Overruns in Samba 3.0 and Samba 2.2 CVE ID: CAN-2004-0600, CAN-2004-0686 ~ (http://cve.mitre.org/) - ------------- CAN-2004-0600 - ------------- Affected Versions: >= v3.0.2 The internal routine used by the Samba Web Administration Tool (SWAT v3.0.2 and later) to decode the base64 data

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second release candidate snapshot of the Samba 3.0.6 code base (the first rc was labeled as 3.0.5rc1) and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second release candidate snapshot of the Samba 3.0.6 code base (the first rc was labeled as 3.0.5rc1) and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at

Hello all! I found a little bug in the rsync v3.0.2 install, that is if you separate the build (output) folder from the source folder, the man files fail to install because they are generated in the output folder, but the install target searches them in the source folder. I attach a small patch that solves this problem. Thanks all, Ciprian Craciun. P.S.: I'm not on the

Hi all heve been trying (in vain) to get a Solaris b44 DomU (dowloaded from Sun) running on a Linux Xenhost I followed exactly how, and it looked ok when it starts booting... But it never boots . adapted the configfile to boot with -v (that I can see at least something) and this is what I get ===SNIP=== root@Xen-VT02:/export/xc/xvm/solaris-b44# xm create solaris-b44-64.py -c Using config

1. Attempt to load Nexenta under 2.6.32.16-1.2.108.xendom0.fc13.x86_64 Xen 4.0.1-rc6-pre & 2.6.32.16-1.2.108.xendom0.fc13.x86_64 on top F13 [root@fedora13 NexentaStor-Community-3.0.2]# uname -a Linux fedora13 2.6.32.16-1.2.108.xendom0.fc13.x86_64 #1 SMP Fri Jul 23 17:09:30 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux [root@fedora13 NexentaStor-Community-3.0.2]# xm create -c

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

http://bugzilla.mindrot.org/show_bug.cgi?id=262 Summary: ssh fails when run by cron. Product: Portable OpenSSH Version: 3.0.2p1 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: glen.lapham at

1. What is the right procedure for a Samba 3.x server to join multiple domains? I have seen below error intermittently when using "net join": Create of workstation account failed User specified does not have administrator privileges Unable to join domain <domain_name>. 2. Is there a Samba (v3.0.2) command to show what domain(s) it has already joined? Thanks in advance.

If you want to hear an example of the new Cepstral voices (v3.0.2) dial 700-348-3589 I have Frank and Emily available.

Hi all, I experienced the same problem with 3.0.4 that Jeremy and Bruno were discussing - NTBackup unable being to connect to shares and erroring out with 'Access Denied'. I have today upgraded to 3.0.5 (using the Debian Woody packages) and that didn't fix the problem. Was the fix in 3.0.5r1 only applicable to 2000/2003 server? I am stuck in the dark ages of NT 4 here, maybe that is a

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

Earlier this year I upgraded all of our Unix Solaris servers from Samba v2.2.8 w/no domain to Samba v3.0.2 w/one domain. I have been adding Windows 2000 and Windows XP workstations to the domain. Everything has been working fine. I run the winbindd daemon but do not have winbind "configured" in any other way other than these few entries in the global section of the smb.conf files on

Hello, I think I found a problem that should not happen: An OpenSSH client v3.0.2 on Solaris and an OpenSSH server 2.3.0p1 on HP- UX had a problem when authenticating: Password login worked fine, but a password for an existing and configured RSA1 key was never asked, the key never tried. It always fell back to plain password authentication. After fiddling with the client configuration

I was able to resolve this issue. Just in case anyone is interested, I HAD to upgrade the PDC FIRST. Then I was able to upgrade the member servers without problems. ********************************************************* I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to

Hi: I want to upgrade a Fedora Core 1 Linux machine that is running Samba 3.0.2a to 3.0.5. Initially, I compiled the 3.0.2a source, with defaults, and installed. The installation resides in /usr/local/samba. Can I download the 3.0.5 source, compile and install without breaking anything? Will the configuration be broken? Does anyone know a way to do this cleanly? Anyone's help is

Hi All, I have been having problems with the known issue on 3.0.4 with NTBackup and a DFS related issue. Therefore I decided to give 3.0.5rc1 a go, as SuSE have released the rpms on their website. Once I installed the rpms, I found that all daemons started correctly, but all domain authentication failed (I am running a samba server as a member server against a Windows 2000 mixed mode domain).

I have upgraded my openssh version from 2.2.0.p1 to 3.0.2p1. 3.0.2 was compile on a sunblade 100 running Solaris 8. Is it possible for my to use my existing DSA key? Thanks, David Higdon UNIX System Administrator (503) 450-4800 (Office) (503) 701-5558 (Cell Phone) higdon.david at cnf.com

Hi all, In an attempt to get the old v2.2 Samba behaviour to work, I tried to enable the ldapsam_compat mode in passwd backend. Win2k cannot connect, username and password not accepted. The LDAP logs reveal that Samba is trying to make the following search: (&(&(uid=minfrin)(objectClass=sambaSamAccount))(objectClass=sambaAccount)) This search returns users who have both the old v2.2

CentOS Errata and Bugfix Advisory 2012:0686 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0686.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c002dad7305a7334a7587a7129cec40b8b938766154ad50d07f52fa276219c86 gnome-power-manager-2.28.3-6.el6_2.i686.rpm