On 2013-06-26 4:05 PM, Jim Klimov wrote:
snip
ln -s ../usr/local/samba/lib/nss_winbind.so.1 /lib/nss_winbind.so.1
ln -s nss_winbind.so.1 /lib/nss_winbind.so.2
ln -s nss_winbind.so.1 /lib/libnss_winbind.so.1
(this would symlink the current-directory's .so.1 in /lib/ into other
names that you
On 25/06/13 18:15, James Relph wrote:
All the rest is good but that crle line - ugh.
Ignore that, I should have deleted it out. I was using that while
trying to sort out the LDFLAGS bit, but it's not necessary.
Aha, good ;-)
One thing in terms of the LDFLAGS line actually that you might
On Wed, Jun 26, 2013 at 10:25:53AM +0200, Laurent Blume wrote:
On 25/06/13 18:15, James Relph wrote:
In there. The installation copies the contents of the
bin/shared/private folder in the installation directory to
/usr/local/samba/lib/private, so is that the correct method, or could
I have
On 25/06/13 02:08, Christopher Chan wrote:
Depends I guess. I have the same results but things work over here...but
then I did build a patched version of samba and I don't just run vanilla
samba like what csw built.
If you have interesting patches, they'd be welcome. I'll keep those for
the
Hi all,
I still haven't been able to get Samba 3.6 working (of any variety), but I have
managed to get Samba4 up and running, and it's pretty good.
I'll check these notes to make sure these are accurate, but these are the steps
to have a non-global zone in Oi 151a7 sharing out SMB and AFP with
On 25/06/13 12:24, James Relph wrote:
crle -l
/lib:/usr/lib:/etc/lib:/opt/gcc/4.4.4/lib:/usr/local/samba/lib:/usr/local/samba/lib/private
All the rest is good but that crle line - ugh.
Playing with crle is more dangerous than it looks, and advising to use
it without explaining exactly why
On Wednesday, June 26, 2013 12:15 AM, James Relph wrote:
All the rest is good but that crle line - ugh.
Ignore that, I should have deleted it out. I was using that while trying to
sort out the LDFLAGS bit, but it's not necessary.
One thing in terms of the LDFLAGS line actually that you might
What do you get when you do wbinfo -a user or wbinfo -k user?
Plaintext and Kerberos authentication succeeds, but challenge-response doesn't
for some reason. Not sure if that's related?
Thanks,
James.
___
OpenIndiana-discuss mailing list
On Monday, June 24, 2013 06:51 PM, James Relph wrote:
What do you get when you do wbinfo -a user or wbinfo -k user?
Plaintext and Kerberos authentication succeeds, but challenge-response doesn't
for some reason. Not sure if that's related?
Depends I guess. I have the same results but things
On Tuesday, June 25, 2013 08:21 AM, James Relph wrote:
Depends I guess. I have the same results but things work over
here...but then I did build a patched version of samba and I don't
just run vanilla samba like what csw built.
I tried the same approach myself but ran into a problem
Thanks, that got me past the LDAP error! Just a Kerberos error now... sigh...
For reference this fixes that:
export CPPFLAGS=-I/usr/include/kerberosv5
James
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
Hey James,
Am 23.06.2013 um 02:10 schrieb James Relph ja...@themacplace.co.uk:
Just been looking into this a bit and I wondered if the was any chance that
this group issue could be causing problems (users are in a lot of groups):
https://bugzilla.samba.org/process_bug.cgi
guess you're
On 2013-06-23 2:10 AM, James Relph wrote:
Just been looking into this a bit and I wondered if the was any
chance that this group issue could be causing problems (users are in
a lot of groups):
https://bugzilla.samba.org/process_bug.cgi
Does the current version of cswsamba have those patches?
If Andrew doesn't respond, let me know. It shouldn't be too hard to get these
right for Samba 4.
Thanks Frank, I think Samba4 looks in general a little easier - even the
compilation seems more straightforward than 3. The benefit there is I can get
Samba4 to actually use winbind properly!
You should be able to just upgrade to them:
pkgutil -t http://buildfarm.opencsw.org/opencsw/experimental/laurent -u
Hi Lauren,
Thanks for that, the patches seem to work and I can use netatalk with winbind
still (with more groups now!), but SMB is still a no go, I just get:
On 23/06/2013 22:23, James Relph wrote:
Hi Lauren,
Laurent with a 't', so it's male, just for the record ;-)
Thanks for that, the patches seem to work and I can use netatalk with
winbind still (with more groups now!),
Okay, good to know, I'll see if upstream will get the patches in or if
Laurent with a 't', so it's male, just for the record ;-)
Sorry, typo there, I did get it right earlier!
Careful, IIRC, the No such user answer for Samba is an authentication
issue, you can get that even when the user is indeed there, but with eg a bad
password. While the pam results
On Monday, June 24, 2013 07:24 AM, James Relph wrote:
Yep, if I setup other PAM bits I can login via (for instance) SSH, and
netatalk worked pretty much straight away. I'll bring this up on the
samba lists and see if anyone has any ideas. Samba4 is working pretty
well, so that might be an
Just been looking into this a bit and I wondered if the was any chance that
this group issue could be causing problems (users are in a lot of groups):
https://bugzilla.samba.org/process_bug.cgi
Does the current version of cswsamba have those patches? I tried compiling a
version from scratch,
On 21/06/13 07:15, James Relph wrote:
Hi,
Apologies for cross posting, but I'm not sure if this is an Oi issue
or a cswsamba issue. I've installed cswsamba (3.6.15) and
cswsamba_winbind on an OI box (151a7). I've got it bound to AD fine,
and winbind itself seems to be operating perfectly
Thanks Laurent, appreciate the help.
I'm maintaining that package, I do want to keep it running on OI as well, so
it's good to know it's working there.
Both cswsamba and cswwinbind do seem to be working fine, they're just not
talking to each other!
It might be a Samba configuration issue,
On 21/06/13 14:50, James Relph wrote:
Both cswsamba and cswwinbind do seem to be working fine, they're just
not talking to each other!
Well, the lines you had shown appeared to show they were talking, just
the answer was negative for some reason.
snip
Look all good.
It didn't seem to
Well, the lines you had shown appeared to show they were talking, just the
answer was negative for some reason.
Interesting, odd that the PAM side is working though. It's been very annoying
I'll say that.
Do you remember where?
Here: https://www.opencsw.org/mantis/view.php?id=5020
On 21/06/13 15:50, James Relph wrote:
Here: https://www.opencsw.org/mantis/view.php?id=5020
Ah, for nss, yes. That one is not a lib per se, but a module, so it does
make sense. I don't thin Jan got over to document it before I took the
packaging away from him, so I'll see what can be done.
I think might be a problem. Those are the 32 bit modules. I don't think
you're running the system 32 bit, so apps requesting 64 bit pam will not be
happy.
I think you should try with $ISA (implicit for the relative names), something
like that:
/opt/csw/lib/$ISA/security/pam_winbind.so
I
On 2013-06-21 5:53 PM, James Relph wrote:
I initially dropped the 64-bit versions in and it freaked out big
style (couldn't login initially). The netatalk bit seems to be
running fine with those as well. Does samba even use PAM for talking
with winbind or deal directly?
You need to have
You need to have both, hence the $ISA, since 32 and 64 bits apps will
each need the proper binary.
And I realized I gave you a wrong path earlier for the ldd, forgotten I
had just introduced both 32/64 Samba binaries, I should have noticed it
was way too short:
/opt/csw/sbin/amd64 or
Hi,
Apologies for cross posting, but I'm not sure if this is an Oi issue or a
cswsamba issue. I've installed cswsamba (3.6.15) and cswsamba_winbind on an OI
box (151a7). I've got it bound to AD fine, and winbind itself seems to be
operating perfectly (I've actually got netatalk happily
28 matches
Mail list logo
