10-05-2012
Does your VNC not let you see the login screen itself? Perhaps it can be configured to do so. Other than that I don't think it can be forced from the outside, as it were -- it's a local login screen, if it accepts input from non-local sources that's a severe bug.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How to I write to a log file all the output that is displaying on the screen? with time stamp.
thankx. (3 Replies)
Discussion started by: laila63
3 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies
3. Red Hat
hi,
Can someone help in trouble shooting why my RedHat linux 8.0 in not logging into the KDE screen.
Thanks (1 Reply)
Discussion started by: kayode
1 Replies
4. Solaris
Does anyone have a simple method of logging all shell commands typed by a user (csh in our case)?
- I could enable auditing, but this would be overkill
- I could enable process accounting, but AFAIK, this does not log arguments
Thanks all. (2 Replies)
Discussion started by: minkie
2 Replies
5. Shell Programming and Scripting
Hi All,
Currently my requirement is to parse through the log scripts and show the errors to the user.The only twist I got is it needs some GUI ,which is considered user friendly.
Does anyone has any idea , if GUI can be implemented through shell scripts, please let me know.
Thanks!
nua7 (5 Replies)
Discussion started by: nua7
5 Replies
6. Shell Programming and Scripting
I want to create a GUI which runs shell scripts in the background. What should I use for creating that GUI. I would be nice if you could point me to some resources where I can learn to create a GUI (2 Replies)
Discussion started by: lassimanji
2 Replies
7. Shell Programming and Scripting
what GUI can be used with shell scripting
for example if i want to say hello in prompted window
thnx in advance (3 Replies)
Discussion started by: semosam
3 Replies
8. Shell Programming and Scripting
Hey guys,
I just can't seem to find any hints on this topic (or maybe I just don't find the correct search terms to use :rolleyes: ).
My company developed an application which requires harsh configuration to run it on a server. So I wrote a LOT of shell scripts which take care of the... (2 Replies)
Discussion started by: fatfingerjoe
2 Replies
9. UNIX for Dummies Questions & Answers
Hi
i am connected to remote system using putty over ssh-1 version. i can see the command line and able to perform the operations through it.
is it possible to have a GUI interface of my login rather than terminal access?
do i need to use any client other than putty ?
any help is much... (5 Replies)
Discussion started by: rakeshkumar
5 Replies
10. Programming
python gui or c++ gui or java gui?
and when to use etch one? (1 Reply)
Discussion started by: kaja
1 Replies
LEARN ABOUT NETBSD
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from
which only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD