org [samba-boun...@lists.samba.org] on behalf
of Benjamin Huntsman [bhunts...@mail2.cu-portland.edu]
Sent: Monday, March 18, 2013 2:30 PM
To: samba@lists.samba.org
Subject: [Samba] helppp! security = user + public share
I'm getting killed this morning, since we did a Samba upgrade to one of
I'm getting killed this morning, since we did a Samba upgrade to one of our
production servers this weekend and didn't expect this one.
I have one share that I need unauthenticated access to from a few named
workstations. Here's the config:
# Samba config file created using SWAT
# from UNKNOWN
ik.de]
Sent: Sunday, February 03, 2013 10:59 PM
To: 'TAKAHASHI Motonobu'; Benjamin Huntsman
Cc: samba@lists.samba.org
Subject: AW: [Samba] Cannot logon Samba 4 via plaintext password
Did you try samba-tool:
pwsettings
Sets password settings
set
-H
--quiet
--complexity=on|off|default
--
, 2013 8:27 AM
To: Benjamin Huntsman
Cc: samba@lists.samba.org
Subject: Re: [Samba] Cannot logon Samba 4 via plaintext password
From: Benjamin Huntsman
Date: Fri, 1 Feb 2013 21:42:29 +
> So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the
> traditional build system on
al UNIX password, or is it hopeless?
Thanks!
-Ben
From: samba-boun...@lists.samba.org [samba-boun...@lists.samba.org] on behalf
of Benjamin Huntsman [bhunts...@mail2.cu-portland.edu]
Sent: Friday, February 01, 2013 9:47 AM
To: samba@lists.samba.org
Subject:
So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional
build system on AIX, both built with XLC.
For historical reasons, we're needing to use 'encrypt passwords = no', so that
Samba uses the OS password.
The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 d
Are the man pages not included with the Samba 4 distribution?
After running configure and make (using the old-style build environment under
source3), a "make installman" gives the the following error:
No manpages present. Development version maybe?
How would I go about getting the man pages bui
__
From: Chris Smith [smb...@chrissmith.org]
Sent: Monday, January 21, 2013 1:19 PM
To: Benjamin Huntsman
Cc: samba@lists.samba.org
Subject: Re: [Samba] Samba 3.6.10 not reading groups
Might be related to my bug:
https://bugzilla.samba.org/show_bug.cgi?id=9561
Unfortunately I'm not getting any t
Helpp! :) We didn't catch this in testing and now it's killing me in
production!
I'm getting stuck with my fresh build of Samba 3.6.10. It isn't honoring
groups specified in the valid users clause of the share configuration.
I'm running in security = SHARE mode, and user authentication is worki
>Run ldd on the binary. it will show the unresolved library references.
Hi there! Here is the output:
benhu@systst:/opt $ ldd /opt/samba-4.0.0/lib/security/pam_smbpass.so
/opt/samba-4.0.0/lib/security/pam_smbpass.so needs:
/usr/lib/libc.a(shr.o)
/usr/lib/libpam.a(shr.o)
Yet another odd one...
I've got it set up now so that swat uses pam_smbpass.so, and once a user logs
into swat at least once, it'll update their password in the passdb backend
configured for Samba. But, I also need to ensure that when a user changes
their password via passwd, it also gets upda
Anyone know how to set up pam_smbpass on AIX?
I'm thinking that's going to be the way to go...
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Ok, now I'm stuck...
We have several stand-alone UNIX (AIX) systems that we need to share a few SMB
shares from. None of these are joined to our domain.
We want the end-users to be able to map these shares to their Windows systems
using the username in the form of AIXSERVER\username, and using
Just to report back in on this, the traditional build system under source3
worked for us, and we were able to build and install a working set of Samba
binaries. At this time, we only need the file server bits.
I'll give the new build system another shot when 4.0.1 comes out.
Thanks again!
-Ben
>I can build and install samba 4.0.0 - I have the same library problems as
>you(copy, then set LIBPATH), but after copying the libraries I can run the
>smbd -b command without an error.
>Here's my environment - disclaimer - I've compiled ALL of the necessary
>freeware modules locally(gettext, libic
>Those should have been linked into smbd directly as configure on AIX
>adds vfs_aixacl to the list of modules to be compiled statically.
>
>Would you mind opening a bug on https://bugzilla.samba.org for tracking?
>
>Cheers,
>Christian
Hi there!
Thanks for the reply!
I have added Bug 9557: h
amba-boun...@lists.samba.org [samba-boun...@lists.samba.org] on behalf
of Benjamin Huntsman [bhunts...@mail2.cu-portland.edu]
Sent: Wednesday, January 09, 2013 3:18 PM
To: samba@lists.samba.org
Subject: Re: [Samba] Samba 4 on AIX with XLC
Just FYI, here are at least some of the shared objects that don't get
Just FYI, here are at least some of the shared objects that don't get copied to
the destination when running "make install":
libtalloc.so
libgssapi-samba4.so
libtdb.so
libtevent.so
libkrb5-samba4.so
libroken-samba4.so
libasn1-samba4.so
libhcrypto-samba4.so
libcom_err-samba4.so
libwind-samba4.so
l
Also, shouldn't "make clean" delete all the .so's in the build tree? It
doesn't. After figuring out that that may be tripping me up, I used 'find .
name "*.so" -print | while read so; do rm $so; done' to take care of that. Who
knows what other cruft may be lying around though... at this point
Hi again!
I'll stop making so much noise shortly, but I've got to get this proved by
say, tomorrow, or take a different direction on my project.
I got Samba 4 to compile on AIX using the following:
# export CFLAGS="-I/opt/openldap-2.4.32/include -qlanglvl=extc99"
# CFLAGS="$CFLAGS" ./configur
>I would ensure gettext is available. That's how it's mostly been
>tested.
>
>Jeremy.
Hee hee... that worked. Got samba 4 compiled, so, for the record, gettext is
absolutely required.
I also had to use xlC_r (note the capital C) as the compiler, since XLC will
choke on using C++-style comments
>See if there's a config.log. Look for things to do with "nls",
>"i18n", "l10n", "gettext" etc.
>
>Btw, I think OpenLDAP and "Active Directory support" are only relevant
>to client/member support for AD. The Samba 4.x AD server has its own
>built-in LDAP and Kerberos components.
>
>--
>Michael Wo
>_(...) is how the localisation is done AFAIK. i.e. it's for
>translating messages into different languages.
>
>Maybe there's something wrong with internationalisation/localisation
>(i18n/l10n) on the system? See what the configure output says about
>it (maybe gettext).
>
>--
>Michael Wood
Hi t
>On Mon, Jan 07, 2013 at 10:58:08PM +0000, Benjamin Huntsman wrote:
>> As a further follow-up, here's an example, from source3/utils/net_cache.c:
>>
>> d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
>> timeout_str,
As a further follow-up, here's an example, from source3/utils/net_cache.c:
d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
timeout_str, datastr, timeout > now_t ? "": _("(expired)"));
My C skills aren't good enough to understand what's being done here, but the
off
Has anyone tried building Samba 4.0 on AIX with XLC?
I'm moving right along, but tripping up on some bugs in
source3/utils/net_rpc.c, source3/utils/net_rpc_printer.c, and
source3/utils/net_cache.c where there is an invalid use of the ":" operator.
According to some other posts on the PostgreSQ
I'm getting the impression that ADS support isn't available on AIX at all.
I built a copy of OpenLDAP, and while the configure script detects the ldap
headers, it still says that Active Directory support is not available.
Has anyone had any luck getting this working on AIX?
Thanks in advance!
-
So, if I read this right, Samba4 should be able to participate as a domain
controller, if I specify the option --with-ads, right?
I'm using the following options:
--with-winbind
--with-swat
--with-ads
--with-ldap
--with-acl-support
--with-dnsupdate
--with-aio-support
--prefix=/opt/samba-4.0.0
--
>If it pukes this one last time, I think I'll give up and try 2.7.3 like you
>suggest.
2.6.5 failed. I'm building Samba into /opt/samba-4.0.0. I built a private
copy of 2.7.3 into /opt/samba-4.0.0/python using only the options specified in
install_with_python.sh. Worked no prob.
Thanks!
-B
>I had to build a python 2.7.3 on AIX to get the waf scripts working - the
>Version from Perzl has a bug...
>Howard
I've been killing myself trying to get the "reccomended" Python 2.6.5 from the
install_with_python.sh script to work. Even rebuilt the AIX build system with
minimal packages only
>I think the next step is to change your python install to something as
>close to the upstream python as possible. We supply an
>'install_with_python.sh' script which installs a (now old) but known
>working version, but you should also have reasonable luck with just the
>current python 2.7
>
>http
Hi there!
We're trying to compile Samba 4.0.0 on a fresh install of AIX 6.1
(6100-02-01-0847), with Python RPM's from perzl.org installed into
/opt/freeware. We're also using XLC 12.1.
Unfortunately, we can't even run ./configure, as we're getting errors from the
waf system. Here's what we
n to avoid replacing IBM-supplied components unless strictly
necessary.
Thanks!
-Ben
-Original Message-
From: Björn Jacke [mailto:b...@sernet.de]
Sent: Wed 6/10/2009 2:25 PM
To: Benjamin Huntsman
Cc: samba@lists.samba.org
Subject: Re: [Samba] samba-3.3.4 AD/krb5/pam build failure o
As I suspected, changing a few things like winbind makes no difference.
At the bottom of this message is the error I get.
Reading through the IBM-supplied krb5.h shows a MIT copyright, so it ought to
be compatible.
Given the errors in the build, can we determine where it's choking or what its
mi
Bill-
Thanks for the quick response!
>If it's found by the script, why isn't it listed in the any of the -I
>options below?
IBM puts krb5.h, etc in /usr/include. Only the libs live in /usr/krb5:
$ ls /usr/krb5
COPYRIGHT README.ZH_TW README.ko_KR bin scripts
README.KO_KR REA
Hi all!
Perhaps someone here could tell me if this has been seen before.
We're trying to build samba-3.3.4 for IBM AIX with support for PAM, Active
Directory, and Kerberos.
The end goal is to be able to join the AIX system to our Active Directory
domain so that users can log in via their AD user
36 matches
Mail list logo
