- WLUG - wlug.mailman3.com

ftp in bash script

by Gregory Avedissian

I'm writing a bash script to download a logfile from a site, archive it, then upload the archive to the site. I want the script to stop if the file doesn't download correctly, and I think I've accomplished this. (i.e. it works right when I set it up to download a non-existent file.) Question: will ftp always return an error if the file is downloaded incorrectly or incompletely? This is important, because the last part of the script will replace the file on the ftp server with a blank file of the same name. I don't want to wipe out the original logfile if I don't have it all. (secondary question: Is there a way to pass the "delete" argument without using the interactive shell?) Here's what the first section of the script looks like. Third question: If I set this up to run as a cron job, what happens to my echo messages? Will they appear in /var/log/messages? #download logfile if ftp ftp://user:password@ftp.site.net/logfile.log; then echo echo "File has been downloaded" echo else echo "Download failed" exit fi Thanks, Greg

Dec. 7, 2005

Re: [Wlug] Grub problems after imaging drive

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dick Goodman wrote: > I recently configured a RedHat 9 system with OpenVPN . The original > configuration was done on an old junk box. This is a single boot w/grub > system > > As of last week I knew nothing about grub; I now know marginally more. > > As it was working successfully, it was decided to build a new box for it. > The hard drive was imaged with Ghost Corporate 8.x and restored onto the > new drive. There are some known issues with 8.x and grub > > The grub screen comes up on booting the new box, but when selecting the > (one) entry for RH9, after a short pause it comes back to the grub > screen. I read the grub manual, and from the grub screen did c-command, > then > > root (hd0,0) > setup (hd0) > quit > > The messages after setup did not look like error messages. The behavior > is the same, although I see a message about stage 1.5 flicker by. > I figured out how to look at the hard drive with Knoppix 3.8.2 Live CD > and the partitions and contents look "ok", so it appears to just be a > boot issue. > > How do I resolve this? What additional information do you need? Is there > a better way to clone Linux drive -> Linux drive? > > Dick > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > Here's what I use for boot commands in GRUB on my system. Its SuSE, but I don't think it should make a difference. root (hd0,0)/vmlinuz <boot parameters> initrd (hd0,0)/initrd - From a GRUB command line, make sure (by using the TAB key) that (hd0,0) is a legitimate partition, and that it can find /vmlinuz (or whatever kernel image you are using). If you need initrd, you can use the same trick with the TAB key to get a poor man's directory listing. After you enter those lines, or edit the existing lines to make them look as above, boot it and you should at least get the kernel to start. You may need to specify "root=/dev/xxx" as one of the boot parameters on the "root" command. If you get a panic when it tries to mount root, it is either because you didn't specify "root=/dev/xxx", or because the code for the root device isn't present in the kernel (for example, a SCSI driver or a reiserfs module, as appropriate). I hope root isn't part of LVM...that's a can of worms you should avoid, but I digress. I hope this helps, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDlnkCHl0iXDssISsRAuiaAJ0ZhX3Il4sFM2Yt2cCG1IQBZMy11wCfZIcn bPoThROtkjrTtXGgaHq2Vms= =J3lU -----END PGP SIGNATURE-----

Dec. 7, 2005

Grub problems after imaging drive

by Dick Goodman

I recently configured a RedHat 9 system with OpenVPN . The original configuration was done on an old junk box. This is a single boot w/grub system As of last week I knew nothing about grub; I now know marginally more. As it was working successfully, it was decided to build a new box for it. The hard drive was imaged with Ghost Corporate 8.x and restored onto the new drive. There are some known issues with 8.x and grub The grub screen comes up on booting the new box, but when selecting the (one) entry for RH9, after a short pause it comes back to the grub screen. I read the grub manual, and from the grub screen did c-command, then root (hd0,0) setup (hd0) quit The messages after setup did not look like error messages. The behavior is the same, although I see a message about stage 1.5 flicker by. I figured out how to look at the hard drive with Knoppix 3.8.2 Live CD and the partitions and contents look "ok", so it appears to just be a boot issue. How do I resolve this? What additional information do you need? Is there a better way to clone Linux drive -> Linux drive? Dick

Dec. 7, 2005

Re: [Wlug] SSH without passwords

by Mike Leo

Just for the record, i did not have to make any changes from the default sshd_config file to get this to work. --- Chuck Anderson <cra(a)WPI.EDU> wrote: > Make sure public key auth is enabled on the client > and server: > > /etc/ssh/sshd_config: > > RSAAuthentication yes > PubkeyAuthentication yes > AuthorizedKeysFile .ssh/authorized_keys > > /etc/ssh/ssh_config: > > Host * > RSAAuthentication yes > PubkeyAuthentication yes > > (these are defaults, and so they are commented out > in my files) > > SSH version 1 uses RSAAuthentication, SSH version 2 > uses > PubkeyAuthentication. > > Make sure the perms on the directories and files are > tight enough > (sshd checks): > > chmod 700 ~/.ssh > chmod 600 ~/.ssh/* > > > Finally, are both the server/client the same > implementation of SSH? > SSH.COM uses slightly different formats than OpenSSH > for the public > keys. ssh-keygen can convert between the formats. > > On Wed, Nov 30, 2005 at 01:27:54PM -0800, Mike Leo > wrote: > > i do exactly that, yet it still prompts me for a > > password when ssh'ing. > > > > thoughts? > > > > --- Mike Frysinger <vapier(a)gentoo.org> wrote: > > > > > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike > Leo > > > wrote: > > > > Basically we are ssh-keygen -t (dsa/rsa) the > keys, > > > > copy them to the "remote" servers ~/.ssh/ > > > > > > what are you copying ? for example, i create my > dsa > > > keys: > > > ~/.ssh/id_dsa ~/.ssh/id_dsa.pub > > > then i export my pub key to the remote server: > > > $ scp ~/.ssh/id_dsa.pub remotebox:~/ > > > $ ssh remotebox # <- enter my pw > > > $ cat ~/id_dsa.pub >> ~/.ssh/authorized_keys > > > $ rm ~/id_dsa.pub > > > $ logout > > > $ ssh remotebox # <- no pw needed > > > > > > > There are conflicting doc's at this > point...some > > > say > > > > you need an ssh-agent, some don't mention it. > > > Some > > > > use passphrases, some don't. But if i have to > > > enter > > > > an ssh passphrase everytime, why not just use > the > > > > account password? > > > > > > passphrases are not required, but many people > like > > > to use them > > > > > > ssh-agent allows you to cache the passphrase for > a > > > certain amount > > > of time, thus finding some ground between the > > > 'always use pw' and the > > > 'never use pw' ground of authentication > > > -mike > > > _______________________________________________ > > > Wlug mailing list > > > Wlug(a)mail.wlug.org > > > http://mail.wlug.org/mailman/listinfo/wlug > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > -- > Chuck R. Anderson <cra(a)wpi.edu> / > http://angus.ind.wpi.edu/~cra/ > PGP Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 > A0F9 49BB 5886 > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 1, 2005

Re: [Wlug] SSH without passwords

by Mike Leo

YAAHAHAHAHAHAA!!! Accurate Oracle documents??!?!? HAHHAHAHAAHA --- Jared Greenwald <greenwaldjared(a)gmail.com> wrote: > Oh yea, I forgot that. That one bit me the first 10 > times I did > this... Strange, though that if this is a RAC > requirement it wouldn't > be outlined in the RAC docs... > > -Jared > > On 11/30/05, Mike Leo <mleo963(a)yahoo.com> wrote: > > I got it!! > > > > weird, but i had to change the permissions on the > auth > > file to 640, and then it worked. > > > > Weird is that with less restrictive permissions > (644) > > it failed, but more secure works. > > > > Anyway, thanks for the feedback! > > > > --- Mike Frysinger <vapier(a)gentoo.org> wrote: > > > > > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike > Leo > > > wrote: > > > > Basically we are ssh-keygen -t (dsa/rsa) the > keys, > > > > copy them to the "remote" servers ~/.ssh/ > > > > > > what are you copying ? for example, i create my > dsa > > > keys: > > > ~/.ssh/id_dsa ~/.ssh/id_dsa.pub > > > then i export my pub key to the remote server: > > > $ scp ~/.ssh/id_dsa.pub remotebox:~/ > > > $ ssh remotebox # <- enter my pw > > > $ cat ~/id_dsa.pub >> ~/.ssh/authorized_keys > > > $ rm ~/id_dsa.pub > > > $ logout > > > $ ssh remotebox # <- no pw needed > > > > > > > There are conflicting doc's at this > point...some > > > say > > > > you need an ssh-agent, some don't mention it. > > > Some > > > > use passphrases, some don't. But if i have to > > > enter > > > > an ssh passphrase everytime, why not just use > the > > > > account password? > > > > > > passphrases are not required, but many people > like > > > to use them > > > > > > ssh-agent allows you to cache the passphrase for > a > > > certain amount > > > of time, thus finding some ground between the > > > 'always use pw' and the > > > 'never use pw' ground of authentication > > > -mike > > > _______________________________________________ > > > Wlug mailing list > > > Wlug(a)mail.wlug.org > > > http://mail.wlug.org/mailman/listinfo/wlug > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 1, 2005

Re: [Wlug] SSH without passwords

by Chuck Anderson

I usually create service-specific unpriviliged accounts with their own SSH keys with no passphrases for this purpose. If there are many services/users that need to log in between the boxes, and you don't mind the boxes trusting each other completely, you can use HostBasedAuthentication, which is sort of like rhosts, but with SSH Public Key authentication. Then any user can SSH between boxes that are in /etc/ssh/shosts.equiv with no password, and no user-specific key/passphrase required. On Wed, Nov 30, 2005 at 01:38:42PM -0800, Mike Leo wrote: > that was all good info...thanks. > > We need to ssh via a service so we can't use a > username/password scheme, and, well, it should work!! > > also, oracle requires this ability to setup their > Oracle RAC database, to/from each node in the cluster.

Dec. 1, 2005

Re: [Wlug] SSH without passwords

by Jared Greenwald

Oh yea, I forgot that. That one bit me the first 10 times I did this... Strange, though that if this is a RAC requirement it wouldn't be outlined in the RAC docs... -Jared On 11/30/05, Mike Leo <mleo963(a)yahoo.com> wrote: > I got it!! > > weird, but i had to change the permissions on the auth > file to 640, and then it worked. > > Weird is that with less restrictive permissions (644) > it failed, but more secure works. > > Anyway, thanks for the feedback! > > --- Mike Frysinger <vapier(a)gentoo.org> wrote: > > > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike Leo > > wrote: > > > Basically we are ssh-keygen -t (dsa/rsa) the keys, > > > copy them to the "remote" servers ~/.ssh/ > > > > what are you copying ? for example, i create my dsa > > keys: > > ~/.ssh/id_dsa ~/.ssh/id_dsa.pub > > then i export my pub key to the remote server: > > $ scp ~/.ssh/id_dsa.pub remotebox:~/ > > $ ssh remotebox # <- enter my pw > > $ cat ~/id_dsa.pub >> ~/.ssh/authorized_keys > > $ rm ~/id_dsa.pub > > $ logout > > $ ssh remotebox # <- no pw needed > > > > > There are conflicting doc's at this point...some > > say > > > you need an ssh-agent, some don't mention it. > > Some > > > use passphrases, some don't. But if i have to > > enter > > > an ssh passphrase everytime, why not just use the > > > account password? > > > > passphrases are not required, but many people like > > to use them > > > > ssh-agent allows you to cache the passphrase for a > > certain amount > > of time, thus finding some ground between the > > 'always use pw' and the > > 'never use pw' ground of authentication > > -mike > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Nov. 30, 2005

Re: [Wlug] SSH without passwords

by Mike Leo

I got it!! weird, but i had to change the permissions on the auth file to 640, and then it worked. Weird is that with less restrictive permissions (644) it failed, but more secure works. Anyway, thanks for the feedback! --- Mike Frysinger <vapier(a)gentoo.org> wrote: > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike Leo > wrote: > > Basically we are ssh-keygen -t (dsa/rsa) the keys, > > copy them to the "remote" servers ~/.ssh/ > > what are you copying ? for example, i create my dsa > keys: > ~/.ssh/id_dsa ~/.ssh/id_dsa.pub > then i export my pub key to the remote server: > $ scp ~/.ssh/id_dsa.pub remotebox:~/ > $ ssh remotebox # <- enter my pw > $ cat ~/id_dsa.pub >> ~/.ssh/authorized_keys > $ rm ~/id_dsa.pub > $ logout > $ ssh remotebox # <- no pw needed > > > There are conflicting doc's at this point...some > say > > you need an ssh-agent, some don't mention it. > Some > > use passphrases, some don't. But if i have to > enter > > an ssh passphrase everytime, why not just use the > > account password? > > passphrases are not required, but many people like > to use them > > ssh-agent allows you to cache the passphrase for a > certain amount > of time, thus finding some ground between the > 'always use pw' and the > 'never use pw' ground of authentication > -mike > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Nov. 30, 2005

Re: [Wlug] SSH without passwords

by Chuck Anderson

Make sure public key auth is enabled on the client and server: /etc/ssh/sshd_config: RSAAuthentication yes PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys /etc/ssh/ssh_config: Host * RSAAuthentication yes PubkeyAuthentication yes (these are defaults, and so they are commented out in my files) SSH version 1 uses RSAAuthentication, SSH version 2 uses PubkeyAuthentication. Make sure the perms on the directories and files are tight enough (sshd checks): chmod 700 ~/.ssh chmod 600 ~/.ssh/* Finally, are both the server/client the same implementation of SSH? SSH.COM uses slightly different formats than OpenSSH for the public keys. ssh-keygen can convert between the formats. On Wed, Nov 30, 2005 at 01:27:54PM -0800, Mike Leo wrote: > i do exactly that, yet it still prompts me for a > password when ssh'ing. > > thoughts? > > --- Mike Frysinger <vapier(a)gentoo.org> wrote: > > > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike Leo > > wrote: > > > Basically we are ssh-keygen -t (dsa/rsa) the keys, > > > copy them to the "remote" servers ~/.ssh/ > > > > what are you copying ? for example, i create my dsa > > keys: > > ~/.ssh/id_dsa ~/.ssh/id_dsa.pub > > then i export my pub key to the remote server: > > $ scp ~/.ssh/id_dsa.pub remotebox:~/ > > $ ssh remotebox # <- enter my pw > > $ cat ~/id_dsa.pub >> ~/.ssh/authorized_keys > > $ rm ~/id_dsa.pub > > $ logout > > $ ssh remotebox # <- no pw needed > > > > > There are conflicting doc's at this point...some > > say > > > you need an ssh-agent, some don't mention it. > > Some > > > use passphrases, some don't. But if i have to > > enter > > > an ssh passphrase everytime, why not just use the > > > account password? > > > > passphrases are not required, but many people like > > to use them > > > > ssh-agent allows you to cache the passphrase for a > > certain amount > > of time, thus finding some ground between the > > 'always use pw' and the > > 'never use pw' ground of authentication > > -mike > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Chuck R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Nov. 30, 2005

Re: [Wlug] SSH without passwords

by Mike Leo

that was all good info...thanks. We need to ssh via a service so we can't use a username/password scheme, and, well, it should work!! also, oracle requires this ability to setup their Oracle RAC database, to/from each node in the cluster. --- Chuck Anderson <cra(a)WPI.EDU> wrote: > On Wed, Nov 30, 2005 at 12:37:19PM -0800, Mike Leo > wrote: > > There are conflicting doc's at this point...some > say > > you need an ssh-agent, some don't mention it. > Some > > use passphrases, some don't. But if i have to > enter > > an ssh passphrase everytime, why not just use the > > account password? > > > Passwords get sent tunneled through the encrypted > SSH connection. A > trojaned ssh server could steal your password. > Passphrases and > private keys are never sent anywhere outside of your > box (unless you > want them to). > > If an account password gets compromised, you may > have to change it on > many boxes, and it may be shared with other > unrelated accounts > elsewhere. If a passphrase gets compromised, it > doesn't allow anyone > to do anything without your private key file--you > need both the > private key and the passphrase. > > You can share your passphrase for many different > private keys, but > still have different passwords on unrelated remote > systems. > > You can cache the passphrase in the memory of your > local box > (ssh-agent) so you don't need to enter anything to > ssh to remote > boxes. > > Using a private key with a blank passphrase means > someone could steal > your private key file and use it to log in as you. > This weakens the > requirement for having to steal both the private key > and the > passphrase. Since the private key sits on disk for > a long time, > someone down the road could steal it and you may > never know. This is > even worse if you use a network filesystem for your > home directory. > The passphrase encrypts your private key. > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Nov. 30, 2005