ssh
Hi: Is any 'send file' command to make so that two machines (an amd64 multisocket and a simple i386, both lenny) talk scp with one another through a router (attached to adsl) fully without asking the password? With 'fully' I mean that command: ssh target_machine_name date gives the date without asking a password. The mere sending id_rsa.pub to create the authorized_keys file only works (without asking the password) for command: ssh target_machine_name but if 'date' is also requested, the password is needed (at least in my hands). I know how to solve the issue, i.e. by cross appending the authorized_keys files, in order that each machine knows itself. But there must be a simpler way. Why that need? Certain parallelized computational codes only work if the above 'fully' is met. I came once again across the issue in reinstalling i386 following a died HD. Thanks francesco pietra -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh
Francesco Pietra chiendar...@gmail.com writes: ssh target_machine_name date gives the date without asking a password. The mere sending id_rsa.pub to create the authorized_keys file only works (without asking the password) for command: ssh target_machine_name In the case of the first command, are you running it interactively or non-interactively from, say, cron or a batch job system? If the latter is the case, you either must use passphrase-less SSH keys (insecure) or load an ssh-agent once interactively and cause all subsequent, non-interactive access to find and use that loaded agent. The keychain package might help here. OTOH, if you are indeed running the remote date command interactively then I have no clue Luck, -Brett. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh
Is any 'send file' command to make so that two machines (an amd64 multisocket and a simple i386, both lenny) talk scp with one another through a router (attached to adsl) fully without asking the password? With 'fully' I mean that command: ssh target_machine_name date gives the date without asking a password. The mere sending id_rsa.pub to create the authorized_keys file only works (without asking the password) for command: ssh target_machine_name but if 'date' is also requested, the password is needed (at least in my hands). I know how to solve the issue, i.e. by cross appending the authorized_keys files, in order that each machine knows itself. But there must be a simpler way. That's odd. I am able to get commands to work over SSH without a password. I copied the contents of ~/.ssh/id_rsa.pub on my work computer into ~/.ssh/authorized_keys on my home computer. Now I can SSH from my work computer to my home computer like this: ssh m...@myhomepc date And it logs into my home computer and then runs the date command. I did not have to do anything with the authorized_keys file on my work computer to make this happen. - Dave -- Dave Parker Utica College Integrated Information Technology Services (315) 792-3229 Registered Linux User #408177 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
passwordless ssh
Other alternatives (that doesn't work as well over internet) - and only if there is a limited number of programs that you need access to would be to use snmp or inetd. SNMP: Set up a own oid to return the values you are asking for. Inetd/Xinetd: telnet to a specific port - will start a program on the master that returns some output. But if we are talking about a arbitrary program - and especially over the internet - ssh with exchanged keys are preferable. If you find any of the above alternatives attractive - please let me know and I can give you some examples. Johan Elmerfjord Manager, Unix Systems Administration EMEA Omniture -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh
On Tue, Jan 20, 2009 at 11:06 AM, David A. Parker dpar...@utica.edu wrote: Is any 'send file' command to make so that two machines (an amd64 multisocket and a simple i386, both lenny) talk scp with one another through a router (attached to adsl) fully without asking the password? With 'fully' I mean that command: ssh target_machine_name date gives the date without asking a password. The mere sending id_rsa.pub to create the authorized_keys file only works (without asking the password) for command: ssh target_machine_name but if 'date' is also requested, the password is needed (at least in my hands). I know how to solve the issue, i.e. by cross appending the authorized_keys files, in order that each machine knows itself. But there must be a simpler way. That's odd. I am able to get commands to work over SSH without a password. I copied the contents of ~/.ssh/id_rsa.pub on my work computer into ~/.ssh/authorized_keys on my home computer. Now I can SSH from my work computer to my home computer like this: ssh m...@myhomepc date And it logs into my home computer and then runs the date command. I did not have to do anything with the authorized_keys file on my work computer to make this happen. That's all appropriate. You only need to modify authorized_keys in both places if you want the symmetric relationship that either machine can log into the other. What's going on is that when you copy id_rsa.pub (or id_dsa.pub, or some other *.pub that might be specifically configured) from host A into ~/.ssh/authorized_keys on host B, then this authorizes connections from A to B. If you put that file into ~/.ssh/authorized_keys on host *A*, then that would enable connections from B to A. Copy the data twice, and you get two results. As for the original poster's question about other mechanisms, it's certainly *possible* to come up with other ways to connect without using a password, but that seems likely to be somewhat risky, security-wise. The package openssh-client includes a utility called ssh-copy-id which provides a way to copy a key into ~/.ssh/authorized_keys a bit more easily. Typical usage would be: $ ssh-agent bash [this starts up an ssh agent, which ssh-copy-id needs in order to be able to know where to get a key to copy over...] $ ssh-add ~/.ssh/id_rsa [this tells the ssh agent about this key. This could require entering a password, depending on how the key was set up] $ ssh-copy-id some-u...@some-host Password: [You'll need to enter the password, the first time; ssh-copy-id then copies the public key into place...] After that, you'd be able to submit, without further password requests, or any further copying of ssh data... $ ssh some-u...@somehost date and get the expected result. -- http://linuxfinances.info/info/linuxdistributions.html Katharine Hepburn - Death will be a great relief. No more interviews. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh
Christopher Browne wrote: On Tue, Jan 20, 2009 at 11:06 AM, David A. Parker dpar...@utica.edu wrote: Is any 'send file' command to make so that two machines (an amd64 multisocket and a simple i386, both lenny) talk scp with one another through a router (attached to adsl) fully without asking the password? With 'fully' I mean that command: ssh target_machine_name date gives the date without asking a password. The mere sending id_rsa.pub to create the authorized_keys file only works (without asking the password) for command: ssh target_machine_name but if 'date' is also requested, the password is needed (at least in my hands). I know how to solve the issue, i.e. by cross appending the authorized_keys files, in order that each machine knows itself. But there must be a simpler way. That's odd. I am able to get commands to work over SSH without a password. I copied the contents of ~/.ssh/id_rsa.pub on my work computer into ~/.ssh/authorized_keys on my home computer. Now I can SSH from my work computer to my home computer like this: ssh m...@myhomepc date And it logs into my home computer and then runs the date command. I did not have to do anything with the authorized_keys file on my work computer to make this happen. That's all appropriate. You only need to modify authorized_keys in both places if you want the symmetric relationship that either machine can log into the other. Correct. I mentioned that I did not have to alter the authorized_keys file on my work PC in response to the OP's statement: I know how to solve the issue, i.e. by cross appending the authorized_keys files, in order that each machine knows itself. But there must be a simpler way. I have no idea why you would need to do something like that. I have never had to cross-append anything in order to make this work. I just wanted to clarify for the OP that the keys only need to be shared in one direction to do this. He seems to indicate that the passwordless login works just fine unless he tries to run a command through the ssh command line. I don't know why that would make a difference. He also mentioned scp, and I think the better alternative would be to run sftp with a batch file. - Dave -- Dave Parker Utica College Integrated Information Technology Services (315) 792-3229 Registered Linux User #408177 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: VMware server
I strongly suggest to use a newer version... On Mon, Jan 19, 2009 at 8:59 PM, Umarzuki Mochlis umarz...@gmail.com wrote: I tried installing vmware server 1.0.8 on my debian lenny referring to http://wiki.debian.org/Manual-Howto#head-c9e998d4806797452cd58fce417b6fb00fbc60be and got Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.26-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-amd64' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o /tmp/vmware-config0/vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer /tmp/vmware-config0/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type /tmp/vmware-config0/vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer /tmp/vmware-config0/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-amd64' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at http://www.vmware.com/download/modules/modules.html; and http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html;. Execution aborted. I changed the default gcc to 4.1.2 as it says my kernel compiled with it # export CC=/usr/bin/gcc-4.1.2 -- Regards, Umarzuki Mochlis http://gameornot.net -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Arquitecto de Soluciones Cel: +52 (55) 1021 0774 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: VMware server
This http://www.howtoforge.com/debian_etch_vmware_server_howto works great with newest VMWare 2.x / Dennis Johansen On Tue, Jan 20, 2009 at 11:49 PM, Jaime Ochoa Malagón chp...@gmail.comwrote: I strongly suggest to use a newer version... On Mon, Jan 19, 2009 at 8:59 PM, Umarzuki Mochlis umarz...@gmail.com wrote: I tried installing vmware server 1.0.8 on my debian lenny referring to http://wiki.debian.org/Manual-Howto#head-c9e998d4806797452cd58fce417b6fb00fbc60be and got Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.26-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-amd64' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o /tmp/vmware-config0/vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer /tmp/vmware-config0/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type /tmp/vmware-config0/vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer /tmp/vmware-config0/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-amd64' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at http://www.vmware.com/download/modules/modules.html; and http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html . Execution aborted. I changed the default gcc to 4.1.2 as it says my kernel compiled with it # export CC=/usr/bin/gcc-4.1.2 -- Regards, Umarzuki Mochlis http://gameornot.net -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Arquitecto de Soluciones Cel: +52 (55) 1021 0774 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- Med venlig hilsen Dennis Johansen Hegnstoften 63 2630 Taastrup Tlf: 4371 8584 Mob: 27 515 217 E-mail: dennis.johan...@hegnstoften.net www.hegnstoften.net
