02-28-2008
I copied the id_dsa.pub key to authorized keys and now scp works
but I still get following error for SFTP
machine1[/home/user1] ==>
machine1[/home/user1] ==>sftp ~/SFTP_test_file machine2:/home/user2/ftptest
Connecting to /home/user2/SFTP_test_file...
ssh: /home/user2/SFTP_test_file: no address associated with name
Connection closed
machine1[/home/user1] ==>
machine1[/home/user1] ==>
=======================
However this is the public key which I don't want to use. I want to use the private key so that noone else can log in.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I tried the following script to copy one file automatically:
#!/bin/csh -f
su - root -c "rcp 150.10.128.1:/export/home/sn408Xl/sn408Sol/$fn $fn
This works fine but is there a better way to copy remotely without entering the username and password? Moreover, after the file is copied a... (1 Reply)
Discussion started by: ilak1008
1 Replies
2. Shell Programming and Scripting
Hello All,
I am trying to write a script when executed, asks you for the password, and confirm password; it should save to a file and also entered password should not be in clear text on the console - should be as ****
Can somebody give me direction in writing this in shell?
Thanks
Chiru (4 Replies)
Discussion started by: chiru_h
4 Replies
3. Cybersecurity
Hi,
How can I specify a password on the scp command line so that it should not prompt for the password?
Shabu (3 Replies)
Discussion started by: shabu
3 Replies
4. Shell Programming and Scripting
Hi,
I am using below syntax -
sftp -b passwordfile userid@ipaddress
passwordfile is a file, in which I have just kept a password of userid.
But by this, an error is coming like -
Permission denied (publickey,password,keyboard-interactive).
Please suggest me on this..as I dont... (6 Replies)
Discussion started by: Monalisa
6 Replies
5. Shell Programming and Scripting
Hi,
i want to run the command in remote server through ssh and every time when i run the script its asking to enter the password. I dnt want to enter the password, when i enter the ip address and directly the command shuld execute.
Script:
#!/bin/bash
echo "Enter Server IP Address:"
read... (2 Replies)
Discussion started by: bapu1981
2 Replies
6. Shell Programming and Scripting
Hi, I'm writing a script,
in the script I need to use tcpdump to capture some packets
however it needs root priviledge
my computer is configured by school and I have no real root priviledge
so I can't use sudo on my computer,like
Code:
sudo tcpdump ......
I have to use a limited... (1 Reply)
Discussion started by: esolve
1 Replies
7. Shell Programming and Scripting
Hi all,
i have to sftp a file to another server
I don't have "expect" or sshpass on my machine its solaris 10,
i want to pass password in command line or
after doing this
sftp user@server how to automatically provide the password as input ( stored in some variable or so)
... (1 Reply)
Discussion started by: zozoo
1 Replies
8. HP-UX
I am trying to connect to remote server in hp-ux, using sftp command (using sftp username@ip and password ) able to connect to remote server but, in this case sftp prompt for password and user need to manually enter it.
I want sftp can read a password define in script or from file, so it can... (1 Reply)
Discussion started by: ketanraut
1 Replies
9. Solaris
Hi All,
I am not able to get the command prompt after entering the login password on solaris server
Only access is through console.
Server type : sun4u sparc SUNW,Netra-T12
bsnl-north-in > ssh 10.147.17.207 jtoin
Connecting to 10.147.17.207 as user jtoin
Password:
Last login: Wed Mar 5... (1 Reply)
Discussion started by: sandeep_kmehra
1 Replies
10. Shell Programming and Scripting
Using useradd abc --password password (5 Replies)
Discussion started by: Jagruti Rml
5 Replies
talk(1) General Commands Manual talk(1)
Name
talk, otalk - talk to another user
Syntax
talk person [ttyname]
otalk person [ttyname]
Description
The command is a visual communication program which copies lines from your terminal to that of another user.
If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
host, then person is of the form :
host!user
or
host.user
or
host:user
or
user@host
The form user@host is perhaps preferred.
If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.
When first called, it sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing Ctrl-L will cause the screen to be reprinted,
while your erase, kill, and word kill characters will work in talk as normal. To exit, just type your interrupt character; then moves the
cursor to the bottom of the screen and restores the terminal.
Permission to talk may be denied or granted by use of the mesg command. At the outset talking is allowed. Certain commands, in particular
and disallow messages in order to prevent messy output.
In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session with
the command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
gram with the command. See the Restrictions section.
Examples
The following example demonstrates how to use the command. In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates a
session with user2, whose system (system2) is running ULTRIX V3.0. User1 types the following:
system1> talk user2@system2
The following message appears on the screen of user2:
Message from Talk_Daemon@system2 at 12:37 ...
talk: connection requested by user1@system1.
talk: respond with: otalk user1@system1
To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
system2> otalk user1@system1
Restrictions
The version of released with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3 BSD or versions of
UNIX based on 4.3 BSD.
The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
which has DECMCS characters in its alphabet.
Files
to find the recipient's machine
to find the recipient's tty
See Also
mail(1), mesg(1), who(1), write(1), talkd(8c)
talk(1)