<div>
You best try to run the command and see whether the expect should be in the form that you are looking which is explicit and exact where a simple 
expect &quot;password: &quot;&nbsp; 
 
note the response is commonly ended with a space also adding unnecessary .... 
 
use single quotes or you have to escape the &amp;&nbsp;another option is to assign these to a variable first 
username='username@ftpprd.host.com' 
password='r10@4g@$^#a&amp;r*a^^$%' 
 
spawn sftp $username 
expect 'password: ' 
send &quot;$password&quot; 
expect 'sftp&gt; ' 
#connection established do stuff.
</div>

<div>
it you can use an ip address it would be better. 
on expect, you can use only the last characters, not the entire prompt. 
on the password i use \r instead of \n 
 
#!/usr/bin/expect 
spawn sftp username@ipaddress 
expect &quot;assword: &quot; 
send &quot;r10@4g@$^#a&amp;r*a^^$%\r&quot;
</div>

<div>
In Expect (or Tcl in general) text in braces ({}) does not require escaping, whereas text in double-quotes does. So in <a href="https:#a42676112" rel="ugc">https:#a42676112</a>, substitute send {r10@4g@$^#a&amp;r*a^^$%}; send \r 
While debugging, you also might like to insert exp_internal 1 near the start of your script. This will confirm to you what is being sent, and also shows what comes back.
</div>

<div>
Thanks - I'm having a weird, different issue: &nbsp;The script seems to be sending the right data, but the commands aren't getting executed in SFTP. &nbsp;At the end of the script I'm trying to do an 'ls' and a 'put', but neither command is getting executed. &nbsp;Can I get another hint? 
&nbsp; 
Sample output below (I set exp_internal 1 to show me the inputs and outputs, and changed the server names / passwords) 
 
danp@qvarzpcldb03:~$ ./sftp2.sh 
spawn sftp 0725@ftpprd.bank.com 
parent: waiting for sync byte 
parent: telling child to go ahead 
parent: now unsynchronized from child 
spawn: returns {116608} 
 
expect: does &quot;&quot;&nbsp;(spawn_id exp5) match glob pattern &quot;assword: &quot;? no 
Connecting to ftpprd.bank.com... 
 
expect: does &quot;Connecting to ftpprd.bank.com...\r\n&quot; (spawn_id exp5) match glob pattern &quot;assword: &quot;? no 
Access to this site is entirely prohibited unless permission has been granted. 
 
expect: does &quot;Connecting to ftpprd.bank.com...\r\nAccess to this site is entirely prohibited unless permission has been granted.\r\n&quot; (spawn_id exp5) match glob pattern &quot;assword: &quot;? no 
Authenticated with partial success. 
 
expect: does &quot;Connecting to ftpprd.bank.com...\r\nAccess to this site is entirely prohibited unless permission has been granted.\r\nAuthenticated with partial success.\r\r\n&quot; (spawn_id exp5) match glob pattern &quot;assword: &quot;? no 
0725@ftpprd.bank.com's password: 
expect: does &quot;Connecting to ftpprd.bank.com...\r\nAccess to this site is entirely prohibited unless permission has been granted.\r\nAuthenticated with partial success.\r\r\0725@ftpprd.bank.com's password: &quot;&nbsp;(spawn_id exp5) match glob pattern &quot;assword: &quot;? yes 
expect: set expect_out(0,string) &quot;assword: &quot; 
expect: set expect_out(spawn_id) &quot;exp5&quot; 
expect: set expect_out(buffer) &quot;Connecting to ftpprd.bank.com...\r\nAccess to this site is entirely prohibited unless permission has been granted.\r\nAuthenticated with partial success.\r\r\n0725@ftpprd.bank.com's password: &quot; 
send: sending &quot;some@$#p&amp;h*apassword&quot; to { exp5 } 
send: sending &quot;ls&quot; to { exp5 } 
send: sending &quot;bye&quot; to { exp5 } 
 
 
Script is here: 
#!/usr/bin/expect 
exp_internal 1 
spawn sftp 0725@ftpprd.bank.com 
expect &quot;assword: &quot; 
send &quot;some@$#p&amp;h*assword\r&quot; 
send &quot;put /home/danp/test1.txt&quot; 
send &quot;ls&quot; 
send &quot;bye&quot;
</div>

Dan Packer

<div>
Thank you for your help! 
 
-Dan
</div>

<div>
<div class="content wysiwyg-content">
I'm having trouble with an Expect script on Red Hat Enterprise Server 6.10. &nbsp;I would think that the script below would spawn SFTP, then send the password. &nbsp;I'm getting a Password error, which I am guessing is due to lots of escapable characters. 
 
The script below gets me a &quot;permission denied&quot; error. &nbsp;My password ( I changed some characters) is something like &nbsp;r10@4g@$^#a&amp;r*a^^$% &nbsp;. &nbsp;I have tried escaping the 'special' characters with \ and also tried escaping every character (so it looks like \r\1\0\@\4\g\@\$\^\#\a\&amp;\r\*\a\^\^\$\%). &nbsp;When I manually connect to the site and manually enter a password it works fine. 
 
Can someone tell me what I might be missing? 
 
Thanks for any advice you can provide, 
 
-Dan 
 
#!/usr/bin/expect 
spawn sftp username@ftpprd.host.com 
expect &quot;username\@ftpprd.host.com\'s password: &quot; 
send &quot;r10@4g@$^#a&amp;r*a^^$%\n&quot; 
 
 
T
</div>
</div>

I'm having trouble with an Expect script on Red Hat Enterprise Server 6.10.  I would think that the script below would spawn SFTP, then send the password.  I'm getting a Password error, which I am guessing is due to lots of escapable characters.

The script below gets me a "permission denied" error.  My password ( I changed some characters) is something like  r10@4g@$^#a&r*a^^$%  .  I have tried escaping the 'special' characters with \ and also tried escaping every character (so it looks like \r\1\0\@\4\g\@\$\^\#\a\&\r\*\a\^\^\$\%).  When I manually connect to the site and manually enter a password it works fine.

Can someone tell me what I might be missing?

Thanks for any advice you can provide,

-Dan

#!/usr/bin/expect
spawn sftp username@ftpprd.host.com
expect "username\@ftpprd.host.com\'s password: "
send "r10@4g@$^#a&r*a^^$%\n"


T

Trying to troubleshoot an SFTP script that uses Expect

Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.

Linux

The File Transfer Program (FTP) is a standard network protocol used to transfer computer files between a client and server on a computer network. Built on a client-server model architecture, it separates control and data connections between the client and the server. Users may access the server through a sign-in protocol, typically in the form of a username and password.

The term 'shell' refers to a general class of text-based command interpreters most often associated with the UNIX and Linux operating systems. Popular shells include Bourne, Debian Almquist (dash), Korn (ksh), Bourne Again (bash) and the C shell family (csh). Some view the DOS 'cmd' prompt as a minimal shell of sorts. It is also possible to install Cygwin on Windows and emulate a full Unix environment with complete shell capabilities. Terminal emulators, such as xterm, GNOME Terminal and OS X Terminal, can be used to access shell.