similar to: Solaris 10 Configure failure

Currently running version 3.6.25 on a SPARC Solaris 10 64 bit server. Due to CVE-2016-2118 need to upgrade to version 4.2.11 / 4.3.8 / 4.4.2 No Solaris package available. Configure script fails with “Couldn't determine size of 'bool'” Is it possible to install these versions on Solaris 10 and if so how? Many Thanks Steve. This Email and any attachments contains confidential

Does mitigation of the so-called BADLOCK CVE (CVE-2016-2118) for Samba 3.x imply an upgrade to a non-vulnerable version of the tdb library? If so, can someone point me to any documentation on the tdb vulnerability? Thanks, Sam

Appologies for cross-posting Dear R users, I am using R2WinBUGS to call WinBUGS from R. After loading data, model, and initial values I call this command res <- bugs(data = dfile, inits = list(ifile), parameters.to.save = c("beta"), model.file = mfile, working.directory = tdir, n.thin = nthin, n.chains = 1, n.iter = niterations*nthin, n.burnin = 0, DIC = F, debug = T,

Do you know why Red Hat updated libtdb as part of their remediation for Badlock on Samba4? https://rhn.redhat.com/errata/RHSA-2016-0612.html On Thu, Jun 2, 2016 at 2:37 PM, Jeremy Allison <jra at samba.org> wrote: > On Thu, Jun 02, 2016 at 11:29:25AM -0500, Sam Gardner wrote: > > Does mitigation of the so-called BADLOCK CVE (CVE-2016-2118) for Samba > 3.x > > imply an

Hi all, Does anyone have any experience porting libvorbis to platforms with small total memory sizes? Specifically, I'm trying to figure out if it's feasible to run Ogg Vorbis decoding on one of the PlayStation 3's SPU's -- secondary processors with only 256kb of local memory. It looks like out of the box the memory footprint of libvorbis is roughly: ~130k code ~60k static

Suggested changes applied to smb.conf (and yes, server role is classic PDC): server max protocol = NT1 client signing = auto client ipc signing = auto server signing = auto With no apparent change to the behaviour or resolution to the problem(s). I'm particularly mystified by the logging-in behaviour (that is, if I manage to do it quickly I can log in, but if I

Hello all. We are running Samba 3.6.6 on a Debian 6.0.6 server. We made the upgrade from 3.6.5 to 3.6.5 about a week ago and ever since we have lost the ability to map Samba shares from our Windows XP SP3 and Windows 7 clients: Here's an example from my workstation (logging verbosity set at 10): [2012/11/29 15:23:58.120087, 3] smbd/process.c:1467(switch_message) switch message

Hi, Samba has released patch for CVE-2016-2118 from 3.6.x release onwards. We use samba 3.0.35 in our product. Is there any patch available for 3.0.35? -- Regards Madhu

Running a mix of samba versions (3.6.25 and 4.5.1) in two domains- one "classic" (with samba domain controllers) and one AD (with windows domain controllers.) The eventual goal is to drop the classic domain in favor of the AD domain. Also trying to move from samba 3.x to 4.x since Samba 3 is EOL'd. the "wbinfo -u" command will list users in the servers domain

********************************************************************** http://www.barking-dagenham.gov.uk CONFIDENTIALITY AND DISCLAIMER This email is confidential to the initial email addressee. If you are not the intended recipient, please notify the sender immediately on +44 (0)20 8592 4500 and delete the message from all locations in your computer network. You should not copy this email or

Thanks for your reply, Louis However, I am still blocked by this problem now. !-_- I tried to set the samba server as the DNS server and visit the shared folder by input "\\aaa.bb.com" at windows 7 client. In some cases it works and will not fail. However the similar abnormal phenomenon also occasionally happens (especially at changing the authentication, such as local to ldap): 1) I can

Hi all, A - I thought badlock mitigation was about encrypting SMB traffic, at least most part of it. And this encryption of most part of data transfer could (or should) lower performances. It seems I was wrong: smallest part (something like commands) are encrypted but not SMB traffic (ie file transfer). This for SMB protocol prior to SMB3 (which comes with windows 8). B - According to what I

I have had a very odd problem for a while now, and am hoping this will ring a bell for someone who can point me in the right direction. I had a previous Samba DC (v3.5.6) in my home network, running on a command-line Slackware box. For a variety of reasons I decided to switch to Debian Jessie, which included an upgrade to Samba 4.2.10. I did NOT properly migrate my samba files to the new

Hi all About 18 months ago I connected 14 new Windows 7 PCs to a Centos5.1 server with samba3x as domain members. There are no other servers on site. Today, I had to visit to connect up a PC in a new location. As I would normally do I checked for Centos updates and found 35 outstanding including samba3x 3.6.23-12.el5_11 and samba3x-client, samba3x-common, samba3x-doc, samba3x-domainjoin-gui,

On 20/06/16 19:53, Dale Schroeder wrote: > On 06/17/2016 4:31 PM, peter lawrie wrote: >> Hi all >> About 18 months ago I connected 14 new Windows 7 PCs to a Centos5.1 >> server >> with samba3x as domain members. There are no other servers on site. >> Today, I had to visit to connect up a PC in a new location. As I would >> normally do I checked for Centos

I've now tired both client ipc signing = auto or client signing = required server signing = auto --- that did not work...Also tied winbindd and that was a disaster of a different sort. It wouldn't use the local unix groups first, which will cause way too many issues. All along, however, the PCs that connect (when not trying to use winbindd) have consistently been able to connect and

I disabled client signing from the client side, via OS X's global nsmb.conf file: https://discussions.apple.com/message/30282470#30282470 The performance was back to over 600 MB/s, as compared to 60 MB/s with signing. It just seems a bit weird to me that Apple, in response to the Badlock bug, would have changed the OS X client default to something with such drastic performance implications,

Hi, Due to "Red Hat Vulnerability Response: BADLOCK", an automatic samba package RHEL5 update was apply on our system. This broke "The trust relationship between this workstation and the primary domain failed" (error message logon client) in my environnement production. So, I use now 3.6.23-12.el5_11, I see they are new directive for smb.conf and some others more restrict

So happy for BadLock bug it finally pushed Ubuntu to upgrade samba :-) So many things work better * I can now sudo without having to newgrp first * I can now run id and get a list of all groups I am in * I can now run getent group and get a list of the domain groups but I now have two unexpected groups running the following I get id | sed 's/,/\n/g' | sort > id_without.txt id $USER

I'm seeing these problems with a samba-4.5.x that I wish to be a member of a samba-3.6.x PDC (NT4 style domain controller). =========================== net rpc join -S PDC ... smb_signing_good: BAD SIG: seq 1 Failed to join domain: failed to lookup DC info for domain 'EXAMPLE' over rpc: Access denied =========================== =========================== net rpc info ...