/100513 (e=0/0)
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1: trying
public key file /home/users/robertobouza/.ssh/authorized_keys
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1:
restore_uid: 0/0
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1
/0)
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1: trying
public key file /home/users/robertobouza/.ssh/authorized_keys
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1:
restore_uid: 0/0
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1
, received 99247.6
debug1: Exit status -1
On the server aixserver01:
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1:
temporarily_use_uid: 150302/100513 (e=0/0)
Dec 3 11:23:15 aixserver01 authpriv:debug sshd[467118]: debug1: trying
public key file /home/users/robertobouza/.ssh
Linux server01 2.6.18-164.2.1.el5 #1 SMP Mon Sep 21 04:37:51 EDT 2009 i686
i686 i386 GNU/Linux
Thank you.
Jeff Layton jlay...@samba.org
12/02/2009 03:27 PM
To
robertobo...@bayviewassetmanagement.com
cc
samba@lists.samba.org
Subject
Re: [Samba] CIFS and ghost files.
On Wed, 2 Dec 2009
Hello,
For some reason if you put anything when a linux machine ask you for a
password it lets you in the box. Any ideas?
We are using winbind to authenticate users against AD. I can log in (any
password) and I can see my AD groups and AD users, etc but the password
part doesn't seem to work.
Ok,
I figured it out...
on the pam.d sshd module the system-auth (which in my case holds the
winbind auth) was not included. Including this module will do. So checking
first for sshd directives and then including the system-auth will check
for AD password match.
Thank you.
--
To
Hello,
I was hoping that someone could shed some light on this issue we are
having.
I'm trying to use AD groups to allow SSH access into the Linux boxes but
It doesn't seem to work.
We have:
AllowGroups unix_admins
AllowUsers j...@server1.domain.com
And doesn't work. If I remove the
Hello,
I'm just wondering if someone stumble upon this. We are trying to create a
local account but it looks like the adduser script is contacting the AD
server for some reason and saying that the user already exists when it
doesn't locally.
Is there a way to disable adduser to contact AD or
Hello,
I'm just wondering if there is a way to disable the DNS update when doing
net ads join. Right now is killing us because the servers have private
IPs and its updating our main AD server with those IPs and all the
interfaces (adding like 10 or 20 records for the same machine different
