Sponsored Content
Operating Systems Solaris help forwarding display over vpn Post 302145304 by kuliksco on Tuesday 13th of November 2007 06:55:44 PM
Old 11-13-2007
help forwarding display over vpn

my and the other unix administrator have never been able to get our DISPLAY forwarded over vpn. on our redhat linux boxes we can just use:

ssh -X server1

and it works with no problems.

however, on the solaris boxes the -X doesn't work. is it possible to set up solaris 7 through solaris 10 with a simliar configuration?

when inside our network we can manually set the display

export DISPLAY=10.20.20.10:0.0

and it works fine. anyone have suggestions for getting the display to work over vpn though?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

E-mail forwarding

Hi, I would like to set up an E-mail forwarding service like Netaddress whereby users would be able to create an E-mail account in my domain name and have all the mail sent to that account forwarded to an alternate address they specify. I know that I can redirect mail sent to my domain using... (1 Reply)
Discussion started by: BigBro
1 Replies

2. IP Networking

ip forwarding

Can anyone out there explain to me how to multi home a nic? I hate to say it but I'm a windows guy forced to learn Unix. The issue I currently have is I can't changed the ip on eth0, but in order to make it pingable by other servers I need to multi home the nic with a totally seperate Ip. Any help... (1 Reply)
Discussion started by: win2khater
1 Replies

3. UNIX for Dummies Questions & Answers

help with vpn

We have an older model DG Aviion Unix system and we're trying to switch to VPN but we can't talk to the Unix box... can't ping or telnet to it, but we can talk to all our other systems (PC/NT servers). Is there a network/tcpip setting we're missing? Something we have to change/set, either on... (0 Replies)
Discussion started by: markb
0 Replies

4. IP Networking

Vpn

Hi, I have two unix networks connected via VPN via IPsec. I am using snapgear vpn devices at each location. The two devices can ping one another, as well as the unix network behind the respected devices. The unix machines can ping their local vpn devices. However, I am having issues pinging... (1 Reply)
Discussion started by: l8kerboi23
1 Replies

5. UNIX for Advanced & Expert Users

VPN and then

Hi, I want to work on a remote unix server, then on a windows XP station I have a Forticlient that makes a VPN to the network on which the server is situated. But then I do not know how to work with. In DOS box (cmd BOX) I issue: telnet myserver but It does not know IT. Any idea ? Many thanks. (2 Replies)
Discussion started by: big123456
2 Replies

6. Cybersecurity

ssh X-forwarding and remote forwarding behind proxy

Hi, from my workplace we use a proxy to connect to the outside world, including external ssh servers. The problem is that the server is seeing the connection coming from the proxy and knows nothing about the client behind it. The ssh connection itself works fine, but x-forwarding does not work as... (1 Reply)
Discussion started by: vampirodolce
1 Replies

7. Cybersecurity

X forwarding vs Remote DISPLAY

Hello, I have a question about X forwarding. I was told that we can't X forwarding anymore, do to a security checklist. Example: bitlord@server1# ssh -X server2 So we have to use the DISPLAY variable now. I thought this was less secure? Example: bitlord@server1# xhost + server2 server1... (0 Replies)
Discussion started by: bitlord
0 Replies

8. Solaris

Vpn

Hi. Yesterday I installed Solaris 11.3 and I tried to setup a VPN but I didn't find how to make it. I saw the "network manager" where I found the ethernet connection but I didn't find where to add a VPN connection. When I used Debian Linux there was NetworkManagerVPN that with a GUI I... (0 Replies)
Discussion started by: Jena
0 Replies
pam_xauth(8)						   System Administrator's Manual					      pam_xauth(8)

NAME
pam_xauth - forward xauth keys between users SYNOPSIS
session optional /lib/security/pam_xauth.so arguments DESCRIPTION
pam_xauth.so is designed to forward xauth keys (sometimes referred to as "cookies") between users. Without pam_xauth, when xauth is enabled and a user uses the su command to assume another user's priviledges, that user is no longer able to access the original user's X display because the new user does not have the key needed to access the display. pam_xauth solves the problem by forwarding the key from the user running su (the source user) to the user whose identity the source user is assuming (the target user) when the session is created, and destroying the key when the session is torn down. This means, for example, that when you run su from an xterm sesssion, you will be able to run X programs without explicitly dealing with the xauth command or ~/.Xauthority files. pam_xauth will only forward keys if xauth can list a key connected to the $DISPLAY environment variable. Primitive access control is provided by ~/.xauth/export in the invoking user's home directory and ~/.xauth/import in the target user's home directory. If a user has a ~/.xauth/import file, the user will only receive cookies from users listed in the file. If there is no ~/.xauth/import file, the user will accept cookies from any other user. If a user has a .xauth/export file, the user will only forward cookies to users listed in the file. If there is no ~/.xauth/export file, and the invoking user is not root, the user will forward cookies to any other user. If there is no ~/.xauth/export file, and the invoking user is root, the user will not forward cookies to other users. Both the import and export files support wildcards (such as *). Both the import and export files can be empty, signifying that no users are allowed. ARGUMENTS
debug Turns on debugging messages sent to syslog. xauthpath=/usr/X11R6/bin/xauth Specify the path the xauth program (the default is /usr/X11R6/bin/xauth). IMPLEMENTATION DETAILS
pam_xauth will work only if it is used from a setuid application in which the getuid() call returns the id of the user running the applica- tion, and for which PAM can supply the name of the account that the user is attempting to assume. The typical application of this type is su. The application must call both pam_open_session() and pam_close_session() with the ruid set to the uid of the calling user and the euid set to root, and must have provided as the PAM_USER item the name of the target user. pam_xauth calls xauth as the source user to extract the key for $DISPLAY, then calls xauth as the target user to merge the key into the a temporary database and later remove the database. pam_xauth cannot be told not to remove the keys when the session is closed. SEE ALSO
/usr/share/doc/pam*/html/index.html FILES
~/.xauth/import ~/.xauth/export BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/ AUTHOR
Nalin Dahyabhai <nalin@redhat.com>, based on original version by Michael K. Johnson <johnsonm@redhat.com> Red Hat Linux 2001/9/27 pam_xauth(8)
All times are GMT -4. The time now is 06:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy