<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: how to store passwd in shell scripts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161683#M748372</link>
    <description>Geoff, sorry to disagree, but the .netrc should not be owned by root, but by the user running ftp and be located in his/her homedirectory... And some FTP servers also request a homedirectory not writable by others.&lt;BR /&gt;&lt;BR /&gt;As for the mail variant: you can use any encryption algorithm on the data transferred you like. There are no passwords in it, only the send-script and receive-script (or better, program) need to know how to en- and decrypt the data. So it might be a good solution. And if you configure the receive script as mail-filter in your aliases file, the mail is processed the moment it comes in, so you don't have to schedule and poll for new mail...</description>
    <pubDate>Mon, 19 Jan 2004 01:42:17 GMT</pubDate>
    <dc:creator>Elmar P. Kolkman</dc:creator>
    <dc:date>2004-01-19T01:42:17Z</dc:date>
    <item>
      <title>how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161676#M748365</link>
      <description>I need to create some shell scripts that will have FTP username and password info.  I know this is not secure, but I dont know what alternatives there are for me.  I'm ready to explain the security risks to my users, but want to have some options besides:&lt;BR /&gt;1. "You have to type the passwd each time you run the script", and 2. &lt;BR /&gt;"The password is in a world readable file, say goodbye to all security."&lt;BR /&gt;&lt;BR /&gt;Do I have any other options?&lt;BR /&gt;&lt;BR /&gt;TIA</description>
      <pubDate>Mon, 12 Jan 2004 08:03:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161676#M748365</guid>
      <dc:creator>David Greenberg_3</dc:creator>
      <dc:date>2004-01-12T08:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161677#M748366</link>
      <description>Hi Tia,&lt;BR /&gt;&lt;BR /&gt;The alternative is called scp.&lt;BR /&gt;check:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=350906" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=350906&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Gideon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Jan 2004 08:08:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161677#M748366</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2004-01-12T08:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161678#M748367</link>
      <description>Check the thread.&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=350906" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=350906&lt;/A&gt;&lt;BR /&gt;sks</description>
      <pubDate>Mon, 12 Jan 2004 08:09:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161678#M748367</guid>
      <dc:creator>Sanjay Kumar Suri</dc:creator>
      <dc:date>2004-01-12T08:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161679#M748368</link>
      <description>To pass user names and passwords to FTP program, there is a way using .netrc file. This file should exist with file permission 600 in your home directory. &lt;BR /&gt;Syntax:&lt;BR /&gt;&lt;BR /&gt;machine &lt;MACHINE&gt; login &lt;LOGINNAME&gt; password &lt;PASSWORD&gt;&lt;BR /&gt;&lt;BR /&gt;When you use ftp command, this will check this file and authnticated.&lt;BR /&gt;&lt;BR /&gt;Also, you can go for exchanging public keys in SCP.&lt;BR /&gt;&lt;BR /&gt;-Thanks&lt;BR /&gt;Vijay&lt;/PASSWORD&gt;&lt;/LOGINNAME&gt;&lt;/MACHINE&gt;</description>
      <pubDate>Mon, 12 Jan 2004 08:17:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161679#M748368</guid>
      <dc:creator>Vijaya Kumar_3</dc:creator>
      <dc:date>2004-01-12T08:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161680#M748369</link>
      <description>Try not to do it with passwords in scripts or .netrc files. If a user can login to the server and the file is readable... but you know the risks.&lt;BR /&gt;&lt;BR /&gt;If you don't want to install additional software, you could use rcp. You don't need passwords, just the correct .rhosts file on the remote machine.&lt;BR /&gt;&lt;BR /&gt;If you can install additional software, or have it already installed, install ssh and use scp or sftp. The above thread contains a configuration document in SEP's response.&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Jan 2004 08:22:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161680#M748369</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-12T08:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161681#M748370</link>
      <description>You can use .netrc - just make sure the file is 400 and owned by root.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Mon, 12 Jan 2004 08:51:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161681#M748370</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-01-12T08:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161682#M748371</link>
      <description>I've successfully used mail to transfer information between systems.  I write a program (generally Perl) to "catch" the data on the target system and use an alias in /etc/mail/aliases:&lt;BR /&gt;&lt;BR /&gt;myalias: |/usr/local/bin/myprogram&lt;BR /&gt;&lt;BR /&gt;to strip the headers and do something with the data that was sent to it.&lt;BR /&gt;&lt;BR /&gt;The advantages IMO are that it's audited (look at /var/adm/syslog/mail.log) and seems more reliable (it queues when a host is down instead of going into the bit bucket).  A disadvantage is that by default it's plain text, but so is FTP.  :)&lt;BR /&gt;&lt;BR /&gt;Mic</description>
      <pubDate>Sun, 18 Jan 2004 23:56:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161682#M748371</guid>
      <dc:creator>Mic V.</dc:creator>
      <dc:date>2004-01-18T23:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161683#M748372</link>
      <description>Geoff, sorry to disagree, but the .netrc should not be owned by root, but by the user running ftp and be located in his/her homedirectory... And some FTP servers also request a homedirectory not writable by others.&lt;BR /&gt;&lt;BR /&gt;As for the mail variant: you can use any encryption algorithm on the data transferred you like. There are no passwords in it, only the send-script and receive-script (or better, program) need to know how to en- and decrypt the data. So it might be a good solution. And if you configure the receive script as mail-filter in your aliases file, the mail is processed the moment it comes in, so you don't have to schedule and poll for new mail...</description>
      <pubDate>Mon, 19 Jan 2004 01:42:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161683#M748372</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-19T01:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161684#M748373</link>
      <description>Hello and Thanks for your ideas.&lt;BR /&gt;There were more passwords involved than I mentioned in my original message.  I have decided to secure the script with SUDO.&lt;BR /&gt;&lt;BR /&gt;Thank you for all your help.</description>
      <pubDate>Wed, 21 Jan 2004 10:18:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161684#M748373</guid>
      <dc:creator>David Greenberg_3</dc:creator>
      <dc:date>2004-01-21T10:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161685#M748374</link>
      <description>use ssl encrytpion. or shoot your programmer.</description>
      <pubDate>Wed, 21 Jan 2004 11:33:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161685#M748374</guid>
      <dc:creator>Donny Jekels</dc:creator>
      <dc:date>2004-01-21T11:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: how to store passwd in shell scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161686#M748375</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;My personal preference for the solution is using scp with public key trust setup. But just to add on to above ideas and thinking out of the box, there is also shc (shell compiler) you can use to obfuscate cleartext to a certain extent. the downside is that it reduces efficiency of the script because the generated binary file is much larger. &lt;BR /&gt;&lt;BR /&gt;shc is primarily for those shell script writers who want to "hide" their code. &lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Wed, 21 Jan 2004 12:05:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-store-passwd-in-shell-scripts/m-p/3161686#M748375</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2004-01-21T12:05:50Z</dc:date>
    </item>
  </channel>
</rss>

