Re: OT: pam_unix(dovecot:auth): authentication failure.

Good time of the day, Federico. Thank You, Federico, for Your time and answer. You wrote: > > Could You please comment this auth. failure: > > > > localhost auth: pam_unix(dovecot:auth): authentication failure; > > logname= uid=0 euid=0 tty=dovecot ruser=

Re: OT: pam_unix(dovecot:auth): authentication failure.

On 24/01/13 14:31, Sthu Deus wrote: Good time of the day. Excuse me for off-topic. Could You please comment this auth. failure: localhost auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=null rhost=91.201.64.249 ? As I understand this - one

Re: OT: pam_unix(dovecot:auth): authentication failure.

Good time of the day, Igor. Thank You, Igor, for Your time and answer. If You have any farther ideas, please share it w/ me. You wrote: > > > > localhost auth: pam_unix(dovecot:auth): authentication failure; > > > > logname= uid=0 euid=0 tty=dovecot ruser=null rhost=91

Re: OT: pam_unix(dovecot:auth): authentication failure.

On Fri, Jan 25, 2013 at 12:31:01AM +0700, Sthu Deus wrote: > Good time of the day. > > > Excuse me for off-topic. > > Could You please comment this auth. failure: > > localhost auth: pam_unix(dovecot:auth): authentication failure; > logname= uid=0 euid=0 t

OT: pam_unix(dovecot:auth): authentication failure.

Good time of the day. Excuse me for off-topic. Could You please comment this auth. failure: localhost auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=null rhost=91.201.64.249 ? As I understand this - one tried to login to dovecot - but dovecot

Re: KDE desktop unlock fails due to authentication failure

Yannick Effinger wrote: >> I'm using a daily updated debian/unstable system with KDE desktop. Since >> about 3-4 week I can no longer succesfully unlock the desktop with my >> password after auto-lockup (msg: "unlock failed.."). So after >> auto-lockup I have to switch to a text VT and kill the kde

Re: KDE desktop unlock fails due to authentication failure

0 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x4e00011 > WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: > cast to 'QString' error Authentication failure > > TIA, > Bruno Hi Bruno, have a look at the file

Re: KDE desktop unlock fails due to authentication failure

0 > Major opcode: 2 > Minor opcode: 0 > Resource id: 0x4e00011 > WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: > cast to 'QString' error Authentication failure > > TIA, > Bruno Hi Bruno, have a look at the file

KDE desktop unlock fails due to authentication failure

cannot figure out what's going wrong: [EMAIL PROTECTED]:~$ cat .xsession-errors X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 Minor opcode: 0 Resource id: 0x4e00011 WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPR

Re: su doesn't work "Authentication failure"

"Dennis G. Wicks" <[EMAIL PROTECTED]> writes: > > Kevin Buhr wrote the following on 01/31/2008 12:50 PM: > > From aptitude show login ==>> 1:4.0.18.1-7 <<== >> should give: >> >> 1381ae1ac77b512258657b096522bb6a /bin/su >c80fc747e24fa8bfa099cbef0bfb926f /bin/su <<== > from md5

Re: su doesn't work "Authentication failure"

On Feb 1, 2008 1:10 PM, Dennis G. Wicks <[EMAIL PROTECTED]> wrote: > What should I be worried about and start looking for? > BTW, nobody can get access to my system unless they > break into my house, and that hasn't happened. I even > did a reinstall of the login package just to make sure > the abo

Re: su doesn't work "Authentication failure"

r user account. > > [ . . . ] > >> Jan 31 15:44:18 myserver su[27729]: (pam_unix) authentication failure; >> logname= uid=1000 euid=1000 tty=pts/4 ruser=myuser rhost= user=root > > The "euid=1000" should read "euid=0": your "su" is ru

Re: su doesn't work "Authentication failure"

Kevin Buhr <[EMAIL PROTECTED]> writes: > > If your version of the "login" package is the latest official Etch > version 1:4.0.18.1-7, then "md5sum /bin/su" should give: > > 1381ae1ac77b512258657b096522bb6a /bin/su Sorry. That was sloppy of me. The above hash is for the amd64 architecture.

Re: su doesn't work "Authentication failure"

paul <[EMAIL PROTECTED]> writes: > > It is possible to do 'su someuser' from root but it's not possible to > get back to root then using just 'su' or change from a normal user to > another user account. [ . . . ] > Jan 31 15:44:18 myserver su[27729]

Re: su doesn't work "Authentication failure"

ccount. myserver:/tmp$ su Password: su: Authentication failure Sorry. auth.log says: Jan 31 15:44:18 myserver su[27729]: (pam_unix) authentication failure; logname= uid=1000 euid=1000 tty=pts/4 ruser=myuser rhost= user=root Jan 31 15:44:20 myserver su[27729]: pam_authenticate: Authentication failure Jan 3

su doesn't work "Authentication failure"

Hello, on my debian etch machine 'su' doesn't work if a password is needed. It is possible to do 'su someuser' from root but it's not possible to get back to root then using just 'su' or change from a normal user to another user account. myserver:/tmp$

Re: authentication failure

I am sorry for repling so late.Thanks all. Maintainer give me a lot help. http://www.linode.com/forums/archive/o_t/t_944/cannot_ssh_into_root_account.html From: Jim Hyslop <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: authentication failure Date: Wed, 14 Mar 2007 23

Re: authentication failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrei Popescu wrote: > BTW, IM*VERY*HO I'm not entirely convinced the maintainer is right, but > who asks me? :) I agree with you. His main argument seems to be that an ordinary user has access to root anyway, so why prevent direct access to root? We

Re: authentication failure

Tarek Soliman <[EMAIL PROTECTED]> wrote: > On Tue, Mar 13, 2007 at 10:05:24AM +0200, Andrei Popescu wrote: > > Tarek Soliman <[EMAIL PROTECTED]> wrote: > > > > > Do not log in as root via ssh or even allow it. > > > There are reasons why the default in Debian is PermitRootLogin no > > > > The de

Re: authentication failure

omeone can point me in the right direction... >> > >> > Using SSH , I cannot log in using root - I get 'acccess denied'. >> >> Never log in as root. >> >> > I can log in using a second account I have set up, however when I try >> > su - root (

Re: authentication failure

On Tue, Mar 13, 2007 at 10:05:24AM +0200, Andrei Popescu wrote: > Tarek Soliman <[EMAIL PROTECTED]> wrote: > > > Do not log in as root via ssh or even allow it. > > There are reasons why the default in Debian is PermitRootLogin no > > The default is "yes". > See /usr/share/doc/openssh-server/Read

Re: authentication failure

7;acccess denied'. > > Never log in as root. > > > I can log in using a second account I have set up, however when I try su > > - root (and give root password) it fails and reports 'su: authentication > > failure sorry'. > > Use your root password on th

Re: authentication failure

count I have set up, however when I try su - > root (and give root password) it fails and reports 'su: authentication > failure sorry'. Use your root password on the Password: prompt su gives you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: authentication failure

On 12 Mar 2007, Kent West wrote: > semgogo sem wrote: > > I think that the password I'm typing in is correct. It worked fine a > > week ago. I do nothing but try login using root by wrong password. > > I'm sorry, but your English fails me on this last sentence; I'm unsure > what you're saying. >

Re: authentication failure

Tarek Soliman <[EMAIL PROTECTED]> wrote: > Do not log in as root via ssh or even allow it. > There are reasons why the default in Debian is PermitRootLogin no The default is "yes". See /usr/share/doc/openssh-server/Readme.DEBIAN.gz for the maintainers oppinion. Regards, Andrei -- If you can't e

Re: authentication failure

On Mon, Mar 12, 2007 at 01:43:40PM -0500, Kent West wrote: > So you can log in locally at the terminal as a normal user and then "su > - root" successfully, > but you can not log in via ssh as that same normal user and then "su - > root" successfully. > > I don't know of any mechanism that would c

Re: authentication failure

On Mon, 12 Mar 2007 11:57:27 -0300 Cassiano Leal <[EMAIL PROTECTED]> wrote: [snip] > Both in etch and sarge, root login via SSH is enabled by default. At > least in my installations it was so. I had to disable it manually. In my default Sid it is also enabled. Celejar -- To UNSUBSCRIBE, emai

Re: authentication failure

semgogo sem wrote: > yes, I can log in locally at the terminal as a normal user and then "su > - root" successfully. following the rest of this thread, I think your keyboard is differently configured for the computer and for the computer from where you ssh from. HTH, Johannes -- To UNSUBSCRIBE

Re: authentication failure

semgogo sem wrote: > yes, I can log in locally at the terminal as a normal user and then > "su - root" successfully. > Okay. So you can log in locally at the terminal as a normal user and then "su - root" successfully, but you can not log in via ssh as that same normal user and then "su - root" su

Re: authentication failure

yes, I can log in locally at the terminal as a normal user and then "su - root" successfully. From: Kent West <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: authentication failure Date: Mon, 12 Mar 2007 12:52:34 -0500 semgogo sem wrote: > I can lo

Re: authentication failure

semgogo sem wrote: > I can log in locally at the terminal. > Can you log in locally at the terminal as a normal user and then "su - root" successfully? -- Kent West http://kentwest.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

Re: authentication failure

I can log in locally at the terminal. From: Kent West <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: authentication failure Date: Mon, 12 Mar 2007 12:05:45 -0500 semgogo sem wrote: > I can login as a non-root user, but not as a root user. I get message > &q

Re: authentication failure

semgogo sem wrote: > I can login as a non-root user, but not as a root user. I get message > "Access denied" when longin using root via ssh. When I am in as a > non-root user via ssh and trying to use > su, I get message "su: authentication failure". > Sounds

Re: authentication failure

I can login as a non-root user, but not as a root user. I get message "Access denied" when longin using root via ssh. When I am in as a non-root user via ssh and trying to use su, I get message "su: authentication failure". From: Kent West <[EMAIL PROT

Re: authentication failure

semgogo sem wrote: > I'am sorry for my English. No need to apologize; my comment was not intended as criticism, but rather as an indication that I wasn't understanding. > My box worked fine a week ago. When I login using root last night, I > type in wrong password more than 5 times. Now, I can log

Re: authentication failure

Subject: Re: authentication failure Date: Mon, 12 Mar 2007 10:34:30 -0500 semgogo sem wrote: > I think that the password I'm typing in is correct. It worked fine a > week ago. I do nothing but try login using root by wrong password. I'm sorry, but your English fails me on this last sentence; I&

Re: authentication failure

semgogo sem wrote: > I think that the password I'm typing in is correct. It worked fine a > week ago. I do nothing but try login using root by wrong password. I'm sorry, but your English fails me on this last sentence; I'm unsure what you're saying. Perhaps there is someone else who admins that b

Re: authentication failure

e root password) it fails and reports 'su: authentication >> failure sorry'. > Logging in via ssh as root is a no-no; it's thus disabled by default in > Debian (although you can over-ride it by changing the "PermitRootLogin" > line in "/etc/ssh/sshd_conf

Re: authentication failure

I think that the password I'm typing in is correct. It worked fine a week ago. I do nothing but try login using root by wrong password. From: Kent West <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: authentication failure Date: Mon, 12 Mar 2007 09:35:46 -0500

Re: authentication failure

semgogo sem wrote: > Hopefully someone can point me in the right direction... > Using SSH , I cannot log in using root - I get 'acccess denied'. I can > log in using a second account I have set up, however when I try su - > root (and give root password) it fails and repor

authentication failure

Hopefully someone can point me in the right direction... Using SSH , I cannot log in using root - I get 'acccess denied'. I can log in using a second account I have set up, however when I try su - root (and give root password) it fails and reports 'su: authenticatio

authentication failure

Hopefully someone can point me in the right direction... Using SSH, I cannot log in using root - I get 'Access denied'. I can log in using a second account I have set up, however when I try su - root (and give root password) it fails and reports 'su: authentication

su: authentication failure

Hello, I am unable to 'su' to root or any other user (except when being root). /var/log/auth.log tells me this: unix_checkpwd: check pass: user unknown PAM_unix: authentication failure; sebastia(uid=1000) -> root for su service pam_authenticate: Authentication failure I feel I

Re: su authentication failure

; % su > Password: > su: Authentication failure > Sorry. > > Which I wouldn't expect with a root definition in /etc/passwd of: > > % grep root /etc/passwd > root::0:0:root:/root:/usr/bin/tcsh > > I've got the following versio

su authentication failure

Hola~ I finally took the plunge and pointed apt-get on to the unstable packages. So far, no major problems, wahoo. I am getting some weirdness, tho. When I run su, now, I get: % su Password: su: Authentication failure Sorry. Which I wouldn't expect with a

Re: Debian 2.0: pon works, diald gets PAP authentication failure

On Wed, Sep 16, 1998 at 12:51:46PM +, Ken Westerback wrote: > I have a working ppp connection, using PAP, available through pon or > wmppp as evidenced by the console messages: [logs and config files snipped] > Can anyone tell me what the problem might be? Sounds like you need to add the

Re: Debian 2.0: pon works, diald gets PAP authentication failure

Ken Westerback <[EMAIL PROTECTED]> writes: > I have a working ppp connection, using PAP, available through pon or > wmppp as evidenced by the console messages: > When I try to enable diald by filling out the diald.options files as > follows: > > fifo /etc/diald/diald.ctl > mode ppp > connect "/u

Debian 2.0: pon works, diald gets PAP authentication failure

nky diald[535]: Running pppd: /usr/sbin/pppd -detach modem crtscts mtu 1500 mru 1500 asyncmap 0 Sep 16 08:37:07 pinky pppd[535]: pppd 2.3.5 started by root, uid 0 Sep 16 08:37:07 pinky pppd[535]: Using interface ppp0 Sep 16 08:37:07 pinky pppd[535]: Connect: ppp0 <--> /dev/ttyS1Sep 16 08:37:1