Server :: SSHD Authenticate User Then Terminate Session
Jan 1, 2010
I have problem with sshd server, its authenticate user and then terminate the session. Here is debug log:
Jan 1 04:26:41 server sshd[29677]: debug1: userauth-request for user root service ssh-connection method none
Jan 1 04:26:41 server sshd[29677]: debug1: attempt 0 failures 0
Jan 1 04:26:43 server sshd[29677]: debug1: userauth-request for user root service ssh-connection method password
Jan 1 04:26:43 server sshd[29677]: debug1: attempt 1 failures 0
Jan 1 04:26:43 server sshd[29676]: Accepted password for root from xx.xx.xx.xxx port 50971 ssh2
Jan 1 04:26:43 server sshd[29676]: debug1: monitor_child_preauth: root has been authenticated by privileged process .....
I am trying to setup a chroot with a sshd service running. when I start the sshd in the chroot and login I get this message. Can not find anything on google.
[damien@dev ~]$ ssh -l damien localhost -p 2233 damien@localhost's password: Last login: Tue Jul 21 13:32:52 2009 from 127.0.0.1 debug3: PAM session not opened, exiting Connection to localhost closed.
I am attempting to configure vsftpd to allow anonymous users to PUT files into a shared incoming directory. This would be like a dropbox for my customers. Ideally, the incoming directory's contents would not be viewable by the users.
I believe that refused connection is due to the PAM configuration for vsftpd.
May 4 08:03:16 WSVM-S1-1 sshd[1512]: Invalid user anonymous from xxx.xxx.xxx.xxx May 4 08:03:16 WSVM-S1-1 sshd[1513]: input_userauth_request: invalid user anonymous May 4 08:03:16 WSVM-S1-1 sshd[1512]: pam_unix(sshd:auth): check pass; user unknown
I am currently in a project to set up an LTSP server with 10 thin clients. I am using Ubuntu 9.10 (Karmic).
Installing server and booting clients are working fine. Now, according to the need, I have to restrict user session numbers and allow resuming previous user session.
I have achieved to do the first one, but still could not able to setup the second one. As per requirement, if some thin can have power failure, the same session should be restored back. I am confused here, if I need to focus on saving xsessions or saving gnome sessions. I am looking for a concrete solution as I am running out of time.
I have a BASH script which at one point asks the user a yes/no question. I want to make it so that if the user types in an invalid input 3 times consecutively then the BASH script will echo an error and terminate with exit status 1.
I have an issue with my web server. We are running RedHat Enterprise Linux 3.0 with Apache 2.0 and Tomcat 5.5. The situation has arisen that the httpd sessions never terminate. New connections continue and continue to be created and never die. I have restarted the apache services to reset the connection and have even rebooted the server, however, to no avail. Yes, that does the trick of getting the web sites operational, however, this is not a solution.
I have searched and searched here, www.google.com/linux to no avail. I have looked through the apache.org bug tracker and can't find anything like what I am experiencing. This happened 6 months ago and I got lucky and it stopped, however, the situation has resurfaced. I have reviewed the logs and found nothing that provides any insight.
During the business day, the number of httpd connections continue to grow and I decided to let it see how high it would get before the web sites would crash. That magical number is 203. Now that it is later in the evening and about 2 hours since I restarted the httpd services, I now only have 59 connections. However, I'm fairly certain based upon the traffic on these 2 websites, that in the evening, there aren't many connections after 2000 hours.
I'm using tigthvnc server on linux machine. Often my clients are closing their vncviewrs from close button ('X'), and not exiting gracefully their sessions from OS. How can I terminate the server when they do that?
I am trying to write a perl script which will give an interactive session to a user to execute command on the server. I have written a small script to do this :
Code: !/usr/bin/perl -w use strict; use Net::SSH::Perl; my $host = '192.168.1.1'; my $username = 'user'; my $login_passwd = 'test123';
Previously I have a hard disk running OpenSUSE partitioned as follows: Code: /dev/sda1 = swap /dev/sda2 = / /dev/sda3 = /home
I redid the default partitioning scheme that Fedora tries to use (no LVM crap). Basically told it to make the above layout and to format swap and slash, but NOT to format /home because I want that data. I had it go ahead and install grub on the MBR of this HD as well. The install seems to have went ok and it rebooted. That is when the first problem comes up. I never see grub. I just get a black screen then a bar at the bottom that progressively turns blue, which I assume is Fedora loading.
This is all well and good, then it gets to the login screen (GDM) and I try to log in as root and it tells me "can't authenticate user" hangs for a bit, then goes back to the log in box. I try to get a virtual console (Ctrl+Alt+F#) and nothing. So I guess I have 3 problems in order of significance: - Why no grub? - Why no virtual console? - Why root can't log in?
Normally I would edit kernel option line at the grub prompt to boot into single user mode and fix the problem, but can't. I was able to use the "rescue mode" on the Fedora DVD to accomplish this, but have not had a chance to figure things out any further. I don't think having a /home created by another OS would prevent root from logging in since root "home dir" is /root.
I cannot ssh into an RHEL 5.5 server (192.168.20.104) from another RHEL 5.5 server (192.168.20.101) unless server debug is turned on 192.168.20.104, and even then, I have to wait several minutes before the connection is established. scp to and from the 104 server is also not working.Here is the debug output on the 101 server when server debug is not enabled on the 104 server-:
I've got Fedora 14 running on an EBS volume on Amazon EC2. I've created a few users and enabled port 22. When I set a password for these users, they can successfully ssh into the instance; even if they logout and login again....until:
If I reboot the machine, they can no longer ssh into the machine (permission denied). If I issue the passwd <user> command and change their passwords, they can login again....until I reboot the machine at which time they cannot login again until I change their passwords. The problem exists even from the machine. That is, if root attempts to ssh into 127.0.0.1 using their username/password, the same problem/resolution exists.
I have a Redhat fedora core release 6 (2.6.22.9-61.Ns4) server and form time to time ssh fails although I am still able to ping the device and with a reboot the device will start working correctly so upon further investigation it appears the sshd daemon fails.Not knowing a great deal about Linux I thought I would ask some advice on the path I am thinking of taking. The first would be to put an entry in the cron to try and start the ssdh every hour or so. Would this cause issues in the long term run it multiple times when the sshd daemon was still running?
The Second though I had was having a bash script to check if the process was running and if not restarts it and if it was just exit the program which would seem like a neater way to do it but this is where my limited Linux knowledge hits a wall so was looking for suggestion on how to implement this?
I want to make sure sshd service will start after a server reboot. On redhat or centOS I can do "chkconfig sshd on". What's the equivalent command for ubuntu?
i'm running fedora 10 Gnome ver 2.24.3 kernel 2.6.30.4
i tried to change my /etc/gdm/custom.conf by adding it the following lines: [daemon] TimedLoginEnable=true TimedLogin=your_mike TimedLoginDelay=0
after reloading gnome it's trying to log through "autologin" but than it give an error message "Unable to authenticate user", i tried using passwd -d on my account but still the error persisted, i saw that some users had this error after a fresh install just with logging into the machine without relation to autologin and they needed to change their password first i tried that as well.
i also tried to edit the /etc/gdm/gdm.schemas file <schema> <key>daemon/AutomaticLoginEnable</key> <signature>b</signature> <default>true</default> <schema> <key>daemon/AutomaticLogin</key> code....
But unfortunately the results were the same, i tried this procedure on a different Fedora 7 and on a virtual ubunto 9.4 machine and is was successful.
How to authenticate Samba server with another LDAP Server. - I would like to set up samba server(CentOS5 samba version 3.0.33)for sharing directory. WindowXP client will can access to samba if username and password match with username and password of another existing LDAP server.
- I only know URL and DN of LDAP server and can not modify anything on LDAP Server.
- Can I config at samba server for requirement above.
Im using linux (Suse 11.1) on my laptop in my new job, however I need to set up my accounts and any account to authenticate using the existing windows ADC server.
What do i need to do precisely. I have kerberos & Samba installed. Do i need both of them or can I just go ahead and set up one.
In recent versions of ubuntu, the behavior of gdm and gnome is changed so that if a gnome user doesn't touch the mouse or keyboard for a while, the session is locked, and they have to type their password in order to get back in. I dislike this behavior, because on some of the machines I use and manage, people will walk away and not come back, and then there is no way to log them out. I can switch and log in as a different user, but the AWOL user's session is sitting there eating up resources until the machine is rebooted. I prefer the old behavior, with no locking. Is there any way to get the old behavior back? I've looked through the gdm.conf docs, but can't seem to find anything relevant. This actually seems more like a gnome issue than a gdm issue. I think what's changed is that gnome now invokes a screensaver after a certain amount of time, and that screensaver locks the session.
We're still using an NT Domain Server, and Samba is already configured properly. But the problem is if the shared folder is configured in samba to be accessed by group and not the domain username, authentication fails even if the user is member of the group.
I don't know what happened but sendmail suddenly stopped authenticate my users who tries to send mail. I use slackware 13.0 and sendmail for SMTP with ssl and plain authentication. Imapd works fine. There is nothing in logs just that the client did not issue MAIL/EXPN/VRFY/ETRN during connection.
I'm trying to expand my Courier+MySQL+Postfix+PostfixAdmin server to use SASL logins on Postfix so I can relay on my server. After following several guides I still can't get it to work: Postfix logs show the user transcript and end with "Authentication failure" but it does not tell me what told it that the login failed. The messages log show this:
Feb 19 22:48:55 sportlaan-server saslauthd[7254]: do_auth : auth failure: [user=berend] [service=smtp] [realm=mydomain.com] [mech=pam] [reason=PAM auth error] Which I don't get because I don't think it should be using PAM... I think...
The setup is similar to this one: http://www.howtoforge.org/virtual_users_postfix_courier_mailscanner_clamav_centos_p6 My SASL config has this in it: /usr/lib/sasl2/smtpd.conf pwcheck_method: saslauthd log_level: 3 authdaemond_path: /var/spool/authdaemon/socket mech_list: plain login
I installed KDE 4.3.5 on my existing Gnome desktop and i have two users using the computer. Now from Gnome I am accustomed to switch between session very easy and the sessions continue to run. If I use the Switch option from KDE it just looks my screen and does not switch. Is it possible that I miss some programs? I installed it with Yast and used the group option. I am pretty sure that I missed something during the installation.
