Sponsored Content
Top Forums UNIX for Dummies Questions & Answers SSH using the shell on the client side -- possible? Post 302458405 by SilversleevesX on Thursday 30th of September 2010 04:11:52 PM
Old 09-30-2010
SSH using the shell on the client side -- possible?

I have identical scripts on two machines: one a laptop running Ubuntu 9.04, and the other a Windows XP desktop running Cygwin. The files I'd like to process are on the Windows machine. Running the script in Cygwin engages eight calls to an external executable and spins off who knows how many forks and child processes -- the end-up is that it's as slow as a turtle in a half-Nelson negotiating a waterfall. On the Linux box, both with local files and folders and shared folders over my two-machine LAN (hope that rates as one; I don't know what else to call it), it is of course galaxies faster.

I'd prefer not to make every directory I intend to evaluate with this script into a share point, so I was wondering if there was any way to configure SSH or something similar to log into the Windows box and use the Linux shell and system files to run the script.

Looking forward to well-considered answers.

BZT
 

7 More Discussions You Might Find Interesting

1. Cybersecurity

What's the difference between an SSH Client and an SSH Server?

Eh... yeah. What the title says. :D (1 Reply)
Discussion started by: PSC
1 Replies

2. UNIX for Dummies Questions & Answers

Running server side application on client demand

Ive written a java based "webscraper to rss feed" which resides on my college web space when I execute the app from putty it creates the feed and sets the permissions perfectly.I then wrote a php script to execute the app on demand from the browser using ... system("java -cp... (1 Reply)
Discussion started by: gleesonger
1 Replies

3. UNIX for Advanced & Expert Users

NFS client-side userid mapping

Folks, I am trying to solve the following problem. I have a process on machine A running as root that needs to mount and access an NFS partition being exported from machine B. However, I cannot have 'no_root_squash' option given on B, hence I see NFS requests from machine A end up as 'nobody'... (1 Reply)
Discussion started by: helpmelearn
1 Replies

4. AIX

sftp : have to specify subsystem from client side

I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies

5. Red Hat

Not able to mount NFS share on client side

When i tried to mount the nfs i see this error message mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied and the /etc/exports file in the host side looks like this /remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies

6. Programming

acknowledgement in client side with JMS and AMQP

Hi guys, I have two questions about acknowledgement in client side with JMS and AMQP: 1. what happens if we set CLIENT_ACKNOWLEDGE in producer side in JMS? 2. if basic.publish finishes executing and there is no exception thrown, this means message has been received in message server? or we... (0 Replies)
Discussion started by: majid.merkava
0 Replies

7. AIX

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that: print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3. My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
SSH-AGENT(1)						    BSD General Commands Manual 					      SSH-AGENT(1)

NAME
ssh-agent -- authentication agent SYNOPSIS
ssh-agent [-c | -s] [-dx] [-a bind_address] [-t life] [command [arg ...]] ssh-agent [-c | -s] -k DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA, ECDSA, ED25519). 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 pro- gram. 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 $TMPDIR/ssh-XXXXXXXXXX/agent.<ppid>. -c Generate C-shell commands on stdout. This is the default if SHELL looks like it's a csh style of shell. -d Debug mode. When this option is specified ssh-agent will not fork. -k Kill the current agent (given by the SSH_AGENT_PID environment variable). -s Generate Bourne shell commands on stdout. This is the default if SHELL does not look like it's a csh style of shell. -t life Set a default value for the maximum lifetime of identities added to the agent. The lifetime may be specified in seconds or in a time format specified in sshd_config(5). A lifetime specified for an identity with ssh-add(1) overrides this value. Without this option the default maximum lifetime is forever. -x Exit after the last client has disconnected. 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 ~/.ssh/id_rsa, ~/.ssh/id_dsa, ~/.ssh/id_ecdsa, ~/.ssh/id_ed25519 and ~/.ssh/identity. If the identity has a passphrase, ssh-add(1) asks for the passphrase on the terminal if it has one or from a small X11 program if running under X11. If neither of these is the case then the authentication will fail. It then sends the identity to the agent. Several identities can be stored in the agent; the agent can auto- matically 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 set up: The first is that the agent starts a new subcommand into which some environment variables are exported, eg ssh-agent xterm &. The second is that the agent prints the needed shell commands (either sh(1) or csh(1) syntax can be gener- ated) which can be evaluated in the calling shell, eg eval `ssh-agent -s` for Bourne-type shells such as sh(1) or ksh(1) and eval `ssh-agent -c` for csh(1) and derivatives. 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
~/.ssh/identity Contains the protocol version 1 RSA authentication identity of the user. ~/.ssh/id_dsa Contains the protocol version 2 DSA authentication identity of the user. ~/.ssh/id_ecdsa Contains the protocol version 2 ECDSA authentication identity of the user. ~/.ssh/id_ed25519 Contains the protocol version 2 ED25519 authentication identity of the user. ~/.ssh/id_rsa Contains the protocol version 2 RSA authentication identity of the user. $TMPDIR/ssh-XXXXXXXXXX/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. SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(8) 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. BSD
December 7, 2013 BSD
All times are GMT -4. The time now is 04:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy