10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi friends,
I am trying to scp a file from server A to Server C via Server B (which is jump host)
from Server A to Server B i have one pem key. from server B to server C I have different Pem key..
what I tried
scp -r -o ProxyCommand="ssh -W %h:%p ec2-user@1.4.5.5 dmu.sh... (7 Replies)
Discussion started by: onenessboy
7 Replies
2. UNIX for Advanced & Expert Users
I am not clear with the part of concept of Tunneling using ssh.
ssh -f -N -L 1029 192.168.1.47:25 james@192.168.1.47
I found out that above code works for me . but didn't quite well understood how ti works and need to ask you guys some questions.
since we are using tunnel through ssh ... (2 Replies)
Discussion started by: lobsang
2 Replies
3. Solaris
Hello Solaris experts:
Trying to bring the 11.3 gdm screen over ssh to a Linux Box:
I did the following:
1. made chanes to /etc/ssh/sshd_config & bounced ssh daemon:
# X11 tunneling options
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
2. From the remote Linux box:
... (6 Replies)
Discussion started by: delphys
6 Replies
4. Shell Programming and Scripting
Hi
I need to write a script to ssh through several hops (e.g. HostA-HostB-HostC-HostD), where Host A does not have direct assess to HostC ; HostB cannot access HostD directly.
when I ssh 3 hops and run command with arg1, arg2 and redirect the output to a file, e.g.
HostA> ssh -t HostB ssh -t... (3 Replies)
Discussion started by: chiensh
3 Replies
5. IP Networking
I have a Java web app on machine (X) that needs to talk to an LDAP server (Y) on :636, but the LDAP server is only accessible on a particular network.
I can login to a machine (Z) on that network from X, and this machine can talk to the LDAP server on :636.
How can I tunnel so that X can... (2 Replies)
Discussion started by: spacegoose
2 Replies
6. UNIX for Dummies Questions & Answers
I'm trying to setup a link between my home pc (work-machine) and a server at work (tar-machine) that is behind a gateway (hop-machine) and not directly accessible.
my actions:
work-machine$ ssh -L 1234:tar-machine:22 hop-machine
work-machine$ ssh -p 1234 user@127.0.0.1
- shh access on... (1 Reply)
Discussion started by: Vathau
1 Replies
7. IP Networking
I have situation:
- localhost L
- server A
- server B (currently accessible only from B, but it have key of my localhost - added when L have different location and can access directly to B)
problem:
how set tunnel from L to B and use key from localhost (I don't remember password to B)?
I... (0 Replies)
Discussion started by: lessmore
0 Replies
8. Solaris
Hi SSHers,
I have embedded this below code in my shell script..
/usr/bin/ssh -t $USER@$SERVER1 /usr/bin/ssh $USER2@S$SERVER2 echo uptime:`/opt/OV/bin/snmpget -r 0 -t 60 $nodeName system.3.0 | cut -d: -f3-5`
SSH to both these servers are public-key authenticated, so things run... (13 Replies)
Discussion started by: LinuxUser2008
13 Replies
9. Shell Programming and Scripting
Hi,
I have got a shell script, which fails to run properly..
I am getting the following error:
"Pseudo-terminal will not be allocated because stdin is not a terminal.
Permission denied (gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive)."
I SSH to the machine and then run the... (1 Reply)
Discussion started by: LinuxUser2008
1 Replies
10. IP Networking
Does any one know how to block HTTP Tunnel in squid proxy server.
Pls reply (1 Reply)
Discussion started by: vishwanathhcl
1 Replies
svnserve(8) System Manager's Manual svnserve(8)
NAME
svnserve - Server for the 'svn' repository access method
SYNOPSIS
svnserve [options]
DESCRIPTION
svnserve allows access to Subversion repositories using the svn network protocol. It can both run as a standalone server process, or it
can run out of inetd. You must choose a mode of operation when you start svnserve. The following options are recognized:
-d, --daemon
Causes svnserve to run in daemon mode. svnserve backgrounds itself and accepts and serves TCP/IP connections on the svn port (3690,
by default).
--listen-port=port
Causes svnserve to listen on port when run in daemon mode.
--listen-host=host
Causes svnserve to listen on the interface specified by host, which may be either a hostname or an IP address.
--foreground
When used together with -d, this option causes svnserve to stay in the foreground. This option is mainly useful for debugging.
-i, --inetd
Causes svnserve to use the stdin/stdout file descriptors, as is appropriate for a daemon running out of inetd.
-h, --help
Displays a usage summary and exits.
-r root, --root=root
Sets the virtual root for repositories served by svnserve. The pathname in URLs provided by the client will be interpreted relative
to this root, and will not be allowed to escape this root.
-R --read-only
Force all write operations through this svnserve instance to be forbidden, overriding all other access policy configuration. Do not
use this option to set general repository access policy - that is what the conf/svnserve.conf repository configuration file is for.
This option should be used only to restrict access via a certain method of invoking svnserve - for example, to allow write access via
SSH, but not via a svnserve daemon, or to create a restricted SSH key which is only capable of read access.
-t, --tunnel
Causes svnserve to run in tunnel mode, which is just like the inetd mode of operation (serve one connection over stdin/stdout) except
that the connection is considered to be pre-authenticated with the username of the current uid. This flag is selected by the client
when running over a tunnel agent.
--tunnel-user=username
When combined with --tunnel, overrides the pre-authenticated username with the supplied username. This is useful in combination with
the ssh authorized_key file's "command" directive to allow a single system account to be used by multiple committers, each having a
distinct ssh identity.
-T, --threads
When running in daemon mode, causes svnserve to spawn a thread instead of a process for each connection. The svnserve process still
backgrounds itself at startup time.
-X, --listen-once
Causes svnserve to accept one connection on the svn port, serve it, and exit. This option is mainly useful for debugging.
Once the client has selected a repository by transmitting its URL, svnserve reads a file named conf/svnserve.conf in the repository direc-
tory to determine repository-specific settings such as what authentication database to use and what authorization policies to apply. See
the svnserve.conf(5) man page for details of that file format.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Availability | SUNWsvn |
+--------------------+-----------------+
|Interface Stability | Committed |
+--------------------+-----------------+
NOTES
Source for Subversion is available on http://opensolaris.org.
svnserve(8)