I have **/home/myuser/Desktop/rc/.netrc** file that i want hardlink to **/root**, ie home directory of **root** user. When i do: ln /home/user/Destkop/rc/.netrc /root it gives the following error: > ln: creating hard link /root/.netrc' => .netrc': Invalid > cross-device link but it works when i hardlink the file to **myuser**'s home, ie to **/home/myuser**. So, what's the problem, why it says invalid cross-devices when there is only one file system here? **PS.** I am using **RHEL6**

I have this sort of stanza in my .netrc: machine ftp.mydomain.com login mylogin password mypassword and while I can successfully connect with ftp: ftp ftp.mydomain.com and passing credentials to ncftp: ncftp -umylogin -pmypassword ftp.mydomain.com I get this using only ncftp ftp.mydomain.com NcFTP 3.2.4 (May 16, 2010) by Mike Gleason (http://www.NcFTP.com/contact/) . Connecting to xxx.xxx.0.140... ProFTPD 1.3.1 Server (Debian) [::ffff:xxx.xxx.0.140] Login incorrect. Sleeping 20 seconds...

I am trying to create a script to upload some files to a server via SFTP. I can do that manually by opening an interactive lftp-session and providing username and password there. For the script, I would like to - not hardcode credentials in the script (for obvious reasons) - not mention them on the commandline (I want the command in my .bash_history, but of course not the credentials) - have lftp read the credentials from .netrc or something similar I cannot seem to get this working. My current workaround is a wrapper-script that parses the .netrc for the credentials and adds them to a lftp-script which I delete afterwards. This simulates the steps I perform manually, but seems like re-implementing existing functionality poorly. While this works, the question remains: > Can lftp read .netrc for SFTP-connections? If so, are there special syntax-requirements if customs ports are part of the setup? I need to connect to sftp://username:password1@example.com:12322.

I am trying to write a script which is saving the credentials to a .netrc file and then it is reading from the file in order to pass them to a curl command and saves the returned cookie file for future use. I am interested if this is secure way to pass the username and password and if there is a man in the middle attack would they be able to sniff the credentials if the server which I am trying to reach is over HTTP. #!/bin/bash IP="192.168.0.1" user="Administrator" pass="Password1234" function credentials { mkdir "${HOME}"/.netrc rm "${HOME}"/.netrc/credentials.txt touch "${HOME}"/.netrc/credentials.txt { echo "machine ${IP}"; echo "login ${user}"; echo "password ${pass}"; } >> "${HOME}"/.netrc/credentials.txt chmod 600 "${HOME}"/.netrc/credentials.txt } function cookie { curl -v -c cookie.txt -n "${HOME}"/.netrc/credentials.txt http://"${IP}"/setup.php } credentials cookie I have checked and the credentials.txt file is properly saved in the corresponding directory and the credentials have the right permissions, but when I try to run the cookie function, I got the following error:

't find host 192.168.0.1 in the .netrc file; using defaults

. Why curl is not able to fetch the configured username and password from the credentials.txt file?

Why does curl -n fail in one script but not others? curl 7.67.0 running on MacOS High Sierra The following code in one script: host="ftp.xxxxxx.com/public_html/" /opt/local/bin/curl -n -T $file $host -v Gives me this: > USER xxxx PASS xxxxxxxxxx > USER anonymous PASS ftp@example.com 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0< 530 Login authentication failed * Access denied: 530 Both scripts are bash scripts and located in the same directory of the same machine. There is only one .netrc file. Obviously it is OK as one script uses it with success. The curl code and host variable are the same. In fact, the code in the first script was copied directly from the second script. How do I figure out why one curl command can use the .netrc file but the other can’t? There must be something in the second script that causes the curl failure, but I have no idea what it might be.

Does anyone know which character encoding is used in .netrc? As a German user, I sometimes put umlauts in passwords. So my question is, are these treated as latin1 or may I assume that I am doing fine encoding the file in UTF-8?

I would like a simple (ideally one-liner, without separate script file) command to connect to an ftp server via anonymous login using my email address as the password. My attempt is based on the syntax as shown here of basically ftp username:password@hostname; however this does not work for me when the password itself, being an email address, has an @ sign.. I also tried to provide a netrc file as a heredoc, as so: ftp hostname -N <<< 'login anonymous password user@email.com' but this still prompts me for a password during the ftp login..