07-11-2011
Quote:
Originally Posted by
mamun_bu
Can I allow IP per user basis? i.e one user can telnet 10.10.113.77 another user can telnet other IP like 10.10.78.43 etc. Is it possible in solaris??
I'm not aware if this is possible with telnet or not .
But ssh in cojunction with IPFilter and TCPwrappers can provide something like that with some custom scripting , After all it's not easy job if this is scenario you are looking for .
Maybe some expert can answer your question .
10 More Discussions You Might Find Interesting
1. IP Networking
Hello All
I am running redhat linux 7.2 and would like to know how i can block telnetting to a specified port .
say for example i would like to block telnet acesses to port 80.
regards
Xiamin (5 Replies)
Discussion started by: xiamin
5 Replies
2. Solaris
dear all
does any one give any user write permission using access control list or another way to solve this problem (1 Reply)
Discussion started by: murad.jaber
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
we are on RED HAT linux:
$uname -a
Linux myserver.domain.com 2.6.9-42.0.2.ELsmp #1 SMP Thu Aug 17 18:00:32 EDT 2006 i686 i686 i386 GNU/Linux
The only user that can connect in telnet is root. How can I authorize another users to do telnet ?
Many thanks. (1 Reply)
Discussion started by: big123456
1 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I have a problem. I have machine names and their IP addresses in /etc/hosts file. My application does telnet on that machine host name. The application does not uses IP address for tenet. It will fetch the host name from /etc/hosts file.
Now the telnet server runs on customized port.... (6 Replies)
Discussion started by: zing_foru
6 Replies
5. Solaris
Hi,
I need to implement something that will enforce login to a Solaris server as a particular, specifed user. After this login stage, users will be able to "su -" to whichever user they wish, by which time their activity will be captured by some sort of script (yet to be written). What I need... (7 Replies)
Discussion started by: jamiegeo1
7 Replies
6. Solaris
I need to create a user account for a developer that will allow him rwx access to all resources in a directory. How can I do that?
Thanks (5 Replies)
Discussion started by: gsander
5 Replies
7. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
8. Solaris
Hi all,
I want to create a new user and grant him ONLY transfer files access to a specific directory where he can only upload and read the files. He should be restricted to this activity only.
Regards (6 Replies)
Discussion started by: gilldn
6 Replies
9. AIX
I need to change the security on our AIX servers and disable telnet from all but certain IP addresses.
I have hashed the telnet line in /etc/inetd.conf and added filter rules for those IP adds to allow access on port 23, but this didn't work.
Does anyone have any ideas?
Thanks. (2 Replies)
Discussion started by: Alps
2 Replies
10. UNIX for Advanced & Expert Users
Is there a way to allow a user to use sudo cp on a specific directory and only a specific file? (6 Replies)
Discussion started by: cokedude
6 Replies
LEARN ABOUT DEBIAN
xrlogin
XRLOGIN(1) General Commands Manual XRLOGIN(1)
NAME
xrlogin - start an xterm that uses ssh (or optionally rlogin or telnet) to connect to a remote host
SYNOPSIS
xrlogin [-l username] [-rlogin|-telnet] [xterm options] remote-host
DESCRIPTION
Xrlogin opens an xterm window and runs ssh, rlogin or telnet to login to a remote host.
Xrlogin automatically passes the -name argument to xterm with a value of "xterm-hostname" where hostname is the name of the remote host.
This allows the user to specify resources in their server's resource manager which are specific to xterms from a given host. For example,
this feature can be used to make all xterm windows to a given remote host be the same color or use a specific font or start up in a spe-
cific place on the screen. Xrsh(1) passes the same string so they are compatible in this regard.
Xrlogin specifies that the default title for the new xterm will be "hostname" where hostname is the name of the remote host. This and the
-name argument above can be overridden with xterm-options on the command line.
One could also use xrlogin's sister command xrsh(1) to open a window to a remote host. In the case of xrsh, the xterm would run on the
remote host and use X as the connection protocol while xrlogin would run the xterm on the local host and use rlogin or telnet as the con-
nection protocol. See xrsh(1) for a discussion of the merits of each scheme.
OPTIONS
-l username
When not using -telnet, use username as the id to login to the remote host.
-rlogin
Use the rlogin protocol to open the connection. In general rlogin is preferred because it can be configured to not prompt the user
for a password. Rlogin also automatically propagates window size change signals (SIGWINCH) to the remote host so that applications
running there will learn of a new window size.
-telnet
Use the -telnet protocol to open the connection. Use of telnet provided mostly for hosts that don't support rlogin.
COMMON PROBLEMS
Make sure that the local host is specified in the .rhosts file on the remote host or in the remote hosts /etc/hosts.equiv file. See
rlogin(1) for more information.
EXAMPLES
xrlogin -bg red yoda
Start a local red xterm which connects to the remote host yoda using rlogin.
xrlogin -telnet c70
Open a local xterm which connects to the remote host c70 using telnet.
SEE ALSO
xrsh(1), rlogin(1), telnet(1)
AUTHOR
James J. Dempsey <jjd@jjd.com> and Stephen Gildea <gildea@intouchsys.com>.
X Version 11 Release 6 XRLOGIN(1)