Package rssh (2.3.2-1) installed in root is up to date.
Configuring openssh
//opt/ipkg/info/openssh.postinst: line 3: /opt/bin/update-alternatives: not found
//opt/ipkg/info/openssh.postinst: line 4: /opt/bin/update-alternatives: not found

Generating RSA Key…
/opt/bin/ssh-keygen: relocation error: /opt/bin/ssh-keygen: symbol __stack_chk_guard, version GLIBC_2.4 not defined in file ld-linux.so.3 with link time reference
Generating RSA Key…
/opt/bin/ssh-keygen: relocation error: /opt/bin/ssh-keygen: symbol __stack_chk_guard, version GLIBC_2.4 not defined in file ld-linux.so.3 with link time reference
Generating DSA Key…
/opt/bin/ssh-keygen: relocation error: /opt/bin/ssh-keygen: symbol __stack_chk_guard, version GLIBC_2.4 not defined in file ld-linux.so.3 with link time reference
Fixing permissions on the /tmp directory…
killall: /opt/sbin/sshd: no process killed
/opt/sbin/sshd: relocation error: /opt/sbin/sshd: symbol __stack_chk_guard, version GLIBC_2.4 not defined in file ld-linux.so.3 with link time reference
postinst script returned status 127
ERROR: openssh.postinst returned 127
Nothing to be done
Successfully terminated.

I have struggled several hours with a rebooting issue - after rebooting from the console (after ssh login) or from the web interface, the ssh port was closed again and sshd was not running anymore. I have removed the S50ssh script from /etc/rc2.d and inserted it in /etc/rcS.d (symlink on ../init.d/sshd); now, it’s reboot persistent. Good night!

So, if in doubt give it the microsoft windows treatment

Any ideas anyone?

Equally odd, I have the print server working fine for my PC, but it doesn’t work from the Mac. Quite frustrating

I want help because I buy Iomega IX2 without hard disk and I want to put in two of mine.
It’s possible to install this two hard drive with a firmware and how do ?
Tks a lot for your help

“cd /mnt/soho_storage/samba/”

accidentally added “shares” in the last post.

I’m running OSX Snow Leopard and I have a few different administrator accounts setup for my storcenter. For some reason, files created by admin1 could not be read by admin2, despite the fact that all permissions were set correctly via the iomega storcenter application. Iomega support was unable to fix it.

After some poking around, I realized that the group membership information for many of the inaccessible folders was inconsistent.

I found this article and followed these steps to fix it on my own:

I couldn’t change the group membership via FTP, so I typed: “[storecenter ip]/support.html” into my web browser and clicked Support Access –> Allow remote access for support (SSH and SFTP). I then opened the terminal application and logged in via SSH:

ssh root@[storecenter ip]
sohoMYPASSWORD

cd /mnt/soho_storage/samba/shares

chgrp -R users shares

This changed the group membership of all of my files to “users” (which somehow translates into group “100″ when viewed via FTP). This fixed the otherwise unfixable permissions problem. Hope this helps someone.

I’m trying to ssh/scp to the iomega storage without specifying the password but setting up using SSH public keys. i have created public keys using

ssh-keygen -t rsa

on my local linux and copied the key found in ssh_rsa.pub to the /root/.ssh/authorized_keys file on the iomega storage.
I’ve chmod 400 /root/.ssh/authorized_keys and it is not accepting the public key.

From my linux to storage in with ssh in verbose mode:

debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password

the public key is not accepted.

I’ve also set this up vice-versa. e.g. iomega storage to my linux and it works fine.

e.g.

debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Trying private key: /.ssh/identity
debug1: Offering public key: /.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.

Has anyone encountered this problem? i’m trying to set this up so that i can use rsync in a script without having to specify the password.