Hello... This is the log from SuSE server : Jun 5 11:09:14 b235 in.telnetd[25273]: connect from 134.x.x.x (134.x.x.x) Jun 5 11:09:24 b235 login: FAILED LOGIN 1 FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:09:34 b235 login: FAILED LOGIN 2 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:09:46 b235 login: FAILED LOGIN 3 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:09:53 b235 login: FAILED LOGIN SESSION FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:10:08 b235 in.telnetd[25275]: connect from 134.x.x.x (134.x.x.x) Jun 5 11:10:20 b235 login: FAILED LOGIN 1 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:10:37 b235 login: FAILED LOGIN 2 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:10:49 b235 login: FAILED LOGIN 3 FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:11:35 b235 in.telnetd[25285]: connect from 134.x.x.x (134.x.x.x) Thanks -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
So what was the problem again? The log shows that they did not get in. On Wednesday 05 June 2002 09:43 pm, Stanley Caramoy wrote:
Hello...
This is the log from SuSE server :
Jun 5 11:09:14 b235 in.telnetd[25273]: connect from 134.x.x.x (134.x.x.x) Jun 5 11:09:24 b235 login: FAILED LOGIN 1 FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:09:34 b235 login: FAILED LOGIN 2 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:09:46 b235 login: FAILED LOGIN 3 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:09:53 b235 login: FAILED LOGIN SESSION FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:10:08 b235 in.telnetd[25275]: connect from 134.x.x.x (134.x.x.x) Jun 5 11:10:20 b235 login: FAILED LOGIN 1 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:10:37 b235 login: FAILED LOGIN 2 FROM 134.x.x.x FOR stancrm, Authentication failure Jun 5 11:10:49 b235 login: FAILED LOGIN 3 FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module Jun 5 11:11:35 b235 in.telnetd[25285]: connect from 134.x.x.x (134.x.x.x)
Thanks
-- _________________________________________________ No I Don't Yahoo! And I'm getting pretty sick of being asked if I do. _________________________________________________ John Andersen / Juneau Alaska
Jun 5 11:09:14 b235 in.telnetd[25273]: connect from 134.x.x.x (134.x.x.x) Jun 5 11:09:24 b235 login: FAILED LOGIN 1 FROM 134.x.x.x FOR UNKNOWN, User not known to the underlying authentication module
Like already said, all is safe. A snippet from man in.telnetd (note that all modes require authentication): SYNOPSIS /usr/sbin/in.telnetd [-hns] [-a authmode] [-D debugmode] [-L loginprg] [-S tos] [-X authtype] [-edebug] [-debug port] -a authmode This option may be used for specifying what mode should be used for authentication. Note that this option is only use- ful if telnetd has been compiled with support for authenti- cation, which is not available in the current version. The following values of authmode are understood: debug Turns on authentication debugging code. user Only allow connections when the remote user can pro- vide valid authentication information to identify the remote user, and is allowed access to the specified account without providing a password. valid Only allow connections when the remote user can pro- vide valid authentication information to identify the remote user. The login(1) command will provide any additional user verification needed if the remote user is not allowed automatic access to the specified account. other Only allow connections that supply some authentica- tion information. This option is currently not sup- ported by any of the existing authentication mecha- nisms, and is thus the same as specifying valid. none This is the default state. Authentication informa- tion is not required. If no or insufficient authen- tication information is provided, then the login(1) program will provide the necessary user verification. off This disables the authentication code. All user ver- ification will happen through the login(1) program.
participants (3)
-
John Andersen
-
Peter van den Heuvel
-
Stanley Caramoy