10 More Discussions You Might Find Interesting
1. Red Hat
hi,
I'm trying to run a bash script that starts GUI. Though it says application started when I run this bash script doesn't show up any GUI. Here is what I've tried so far and please let me know if I'm missing something with the X11 set up here.
cat /etc/redhat-release
Red Hat Enterprise... (8 Replies)
Discussion started by: fop4658
8 Replies
2. UNIX for Beginners Questions & Answers
Unable to get X11 activated on my login even after Unix admin has enabled it (2 Replies)
Discussion started by: tomsayer1977
2 Replies
3. Red Hat
Is it possible to launch an X11 application and have it use an X11 server on the other side of a bastion host? Specifically, here's my setup:
my laptop ------------- bastion -------------- remote host
I have putty installed on my laptop. The bastion is rhel 6.5 and the remote host is... (1 Reply)
Discussion started by: tsreyb
1 Replies
4. UNIX for Dummies Questions & Answers
Hello. I installed a Debian box, and its installed remotely. I need to boot up iceweasel from there to do a quick test.
I log on using:
ssh root@<IP> -X
I have modified the /etc/ssh/sshd_config file, and added the X11Forwarding yes flag
And yet I still get:
Error: cannot open... (10 Replies)
Discussion started by: dynelight
10 Replies
5. UNIX for Dummies Questions & Answers
Hi all
I'm having an issue with X11 Forwarding
I have a VM set up on my computer which I usually "ssh -X" to over a home network (192.168.1.*).
Client 192.168.1.100
Server 192.168.1.103
This worked perfectly fine for X11 forwarding.
However I am not at home now (and have no access to... (2 Replies)
Discussion started by: grahambo2005
2 Replies
6. Cybersecurity
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. Red Hat
X11 forwarding problem between 2 RHEL4 machines with SSH
Already configured the following on both machines under /etc/ssh
Under sshd_config:
UsePAM no
AllowTcpForwarding yes
Under ssh_config:
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
-----------------------------
Using... (1 Reply)
Discussion started by: panggou
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am using Putty, enabled SSH X11 forwarding and entered the X11 display location as "localhost:0". However I encountered the following error:
------------------------------------
# xclock &
2941
# X connection to localhost:10.0 broken (explicit kill or server shutdown).
+ Exit 1... (4 Replies)
Discussion started by: panggou
4 Replies
9. Debian
I have 2 Debian boxes.
In my ssh.com client and my putty client, I have X11 fowarding turned
on for both boxes.
When I connect one, I can xterm with no problem back to my pc.
On the other, I keep getting:
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
On both... (3 Replies)
Discussion started by: natter
3 Replies
10. OS X (Apple)
Hi,
I have issues with running graphical interfaces on my computer being remotely logged into a network via the -X option of ssh. My .cshrc shows DISPLAY=hostname:0 and I think there should be a different number instead of the 0. I changed the ssh_config file already to 'X11 forwarding yes', which... (0 Replies)
Discussion started by: ginese
0 Replies
SSH-AGENT(1) BSD General Commands Manual SSH-AGENT(1)
NAME
ssh-agent -- authentication agent
SYNOPSIS
ssh-agent [-a bind_address] [-c | -s] [-d] [command [args ...]]
ssh-agent [-c | -s] -k
DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). The idea is that ssh-agent is started in the
beginning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Through use
of environment variables the agent can be located and automatically used for authentication when logging in to other machines using ssh(1).
The options are as follows:
-a bind_address
Bind the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.<ppid>.
-c Generate C-shell commands on stdout. This is the default if SHELL looks like it's a csh style of shell.
-s Generate Bourne shell commands on stdout. This is the default if SHELL does not look like it's a csh style of shell.
-k Kill the current agent (given by the SSH_AGENT_PID environment variable).
-d Debug mode. When this option is specified ssh-agent will not fork.
If a commandline is given, this is executed as a subprocess of the agent. When the command dies, so does the agent.
The agent initially does not have any private keys. Keys are added using ssh-add(1). When executed without arguments, ssh-add(1) adds the
files $HOME/.ssh/id_rsa, $HOME/.ssh/id_dsa and $HOME/.ssh/identity. If the identity has a passphrase, ssh-add(1) asks for the passphrase
(using a small X11 application if running under X11, or from the terminal if running without X). It then sends the identity to the agent.
Several identities can be stored in the agent; the agent can automatically use any of these identities. ssh-add -l displays the identities
currently held by the agent.
The idea is that the agent is run in the user's local PC, laptop, or terminal. Authentication data need not be stored on any other machine,
and authentication passphrases never go over the network. However, the connection to the agent is forwarded over SSH remote logins, and the
user can thus use the privileges given by the identities anywhere in the network in a secure way.
There are two main ways to get an agent setup: Either the agent starts a new subcommand into which some environment variables are exported,
or the agent prints the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the calling shell.
Later ssh(1) looks at these variables and uses them to establish a connection to the agent.
The agent will never send a private key over its request channel. Instead, operations that require a private key will be performed by the
agent, and the result will be returned to the requester. This way, private keys are not exposed to clients using the agent.
A unix-domain socket is created and the name of this socket is stored in the SSH_AUTH_SOCK environment variable. The socket is made accessi-
ble only to the current user. This method is easily abused by root or another instance of the same user.
The SSH_AGENT_PID environment variable holds the agent's process ID.
The agent exits automatically when the command given on the command line terminates.
FILES
$HOME/.ssh/identity
Contains the protocol version 1 RSA authentication identity of the user.
$HOME/.ssh/id_dsa
Contains the protocol version 2 DSA authentication identity of the user.
$HOME/.ssh/id_rsa
Contains the protocol version 2 RSA authentication identity of the user.
/tmp/ssh-XXXXXXXX/agent.<ppid>
Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner.
The sockets should get automatically removed when the agent exits.
AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. Markus Friedl contributed the support for SSH
protocol versions 1.5 and 2.0.
SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(8)
BSD
September 25, 1999 BSD