Is there an easy way to persist the users home directory (and roots for that matter) during reboots?

i can not start denyhosts, any advice?

 

i install it from telnet, i can see the icon in settings tab but it says "denyhosts is not runnig", clicking start doesnt change anything.

i restart unraid nothing changes

i scan the syslog ang find this line:

 

May 15 21:37:30 Tower logger:   upgradepkg --install-new /boot/config/plugins/denyhosts/DenyHosts-2.6.tar.gz ... Cannot install /boot/config/plugins/denyhosts/DenyHosts-2.6.tar.gz:  invalid package extension
May 15 21:37:30 Tower logger: 
May 15 21:37:30 Tower logger: success

 

i do some research and cant find any solution,

then i try to rename file to .tgz and retry that command:

 

root@Tower:~# upgradepkg --install-new /boot/config/plugins/denyhosts/DenyHosts-2.6.tgz

+==============================================================================
| Installing new package /boot/config/plugins/denyhosts/DenyHosts-2.6.tgz
+==============================================================================

Verifying package DenyHosts-2.6.tgz.
Installing package DenyHosts-2.6.tgz:
PACKAGE DESCRIPTION:
WARNING:  Package has not been created with 'makepkg'
Package DenyHosts-2.6.tgz installed.

 

but with no luck, i cant still cant start the plugin.

ikosa,

 

Tell me, are you also running SimpleFeatures Email Notify plugin?  If so, please can you see last few lines of my second post in this thread.

 

I have installed DenyHosts on a test dev system and it has worked ok.  Actually the error you stated is a bug in the plugin.  It is trying to install the denyhosts file as a package, which is not correct.  But it does not prevent the plugin from installing, it's just a warning.  I have pushed an update to my plugin on Github, so please feel free to get that version as the error will no longer be there. 

 

As I say though, this is not the reason that it does not work for you.  I am hoping you will tell me that SF email notify plugin is being used as I know that this plugin has a setting in that deletes a directory needed by Python.  This is what I mention in my second post on this thread. 

 

I will wait for you to reply before considering other troubleshooting actions.

 

 

Regards,

overbyrn

SimpleFeatures was not running when i install DenyHosts (i install it after a couple hours) but the unMenu version of "unRAID Status Alert sent hourly by e-mail" was installed.

 

i made the changes you point at the second post,

uninstall status alert (the one in the unmenu),

install the updated plugin (no error this time and also no upgradepkg line),

nothing changes still denyhosts is not running

 

other installed plugins/pkgs:

-serviio

-openssh

-cache directories

-SimpleFeatures (now)

-apcupsd

-bwm-ng

-gcc

-cxxlibs

-ssmtp

-ntfs-3g

 

i' ll try to disable all the plugins and try that way,

and waiting for your directions.

thanks very much for your help.

Ok, lets see if we can do some more troubleshooting. 

 

Firstly, remove all other plugins and see if you still get a problem.  Then start adding the others plugins back one by one.

 

Can you capture for me the plugin installing?  ie. can you reboot without the plugin in the plugin directory so that it doesn't install on reboot and then manually install it.  eg. installplg /dir-to-the-plg-file/denyhosts_overbyrn.plg.

 

If using a tool like putty, set your scrollback buffer to a long value, then when the plugin install has completed, highlight everything, zip and post on here.

 

Also, can you tell me what is set for the Work Directory in the settings page?

 

Some other checks to do from command line;

[*]is there a denyhosts python application.  There should be a file called denyhosts.py in /usr/bin.

[*]did the work directory specified in the DenyHosts UnRaid webgui settings page get created?

[*]can you start denyhosts from command line.  eg:

/etc/rc.d/rc.denyhosts start

Check if a process is running:

ps -ef | grep denyhosts | grep -v grep

Should show something like:

root    31453    1  0 19:50 ?        00:00:00 python /usr/bin/denyhosts.py --daemon --config=/boot/config/plugins/denyhosts/denyhosts.cfg > /dev/null 2>&1

 

 

Regards,

overbyrn

 

ermmm ok got the new version installed, seems to work fine.  logged in using FireSSH, try the "top" command and get this,

 

root@Tower:~# top
'xterm-256color': unknown terminal type.

[*]is there a denyhosts python application.  There should be a file called denyhosts.py in /usr/bin.

[*]did the work directory specified in the DenyHosts UnRaid webgui settings page get created?

[*]can you start denyhosts from command line.  eg:

 

1. no denyhosts.py in /usr/bin/

2. it is specified as /usr/local/denyhosts

3. i cant start as seen below

4. no running process as seen below

5. i did these checks after removing all plugins and packages

 

root@Tower:~# /etc/rc.d/rc.denyhosts start
/usr/bin/env: python: No such file or directory
root@Tower:~# ps -ef | grep denyhosts | grep -v grep
root@Tower:~#

 

here is the installation log:

root@Tower:~# installplg /boot/config/plugins/denyhosts_overbyrn.plg
installing plugin: denyhosts_overbyrn
file /tmp/plugin-prepare: successfully wrote INLINE file contents
  /bin/bash /tmp/plugin-prepare ... success
file /boot/config/plugins/denyhosts/denyhosts.png: already exists
file /boot/config/plugins/images/device_status.png: already exists
file /boot/config/plugins/images/new_config.png: already exists
file /boot/config/plugins/images/information.png: already exists
file /boot/config/plugins/denyhosts/DenyHosts-2.6.tar.gz: already exists
file /tmp/plugin-cleanup: successfully wrote INLINE file contents
  /bin/bash /tmp/plugin-cleanup ... success
file /boot/config/plugins/denyhosts/denyhosts.cfg: already exists
file /etc/rc.d/rc.denyhosts: successfully wrote INLINE file contents
  successfully changed file mode
file /usr/local/emhttp/plugins/denyhosts/denyhosts.png: successfully copied LOCAL file
file /usr/local/emhttp/plugins/denyhosts/device_status.png: successfully copied LOCAL file
file /usr/local/emhttp/plugins/denyhosts/new_config.png: successfully copied LOCAL file
file /usr/local/emhttp/plugins/denyhosts/information.png: successfully copied LOCAL file
file /usr/local/emhttp/plugins/denyhosts/denyhosts.php: successfully wrote INLINE file contents
file /usr/local/emhttp/plugins/denyhosts/denyhostsctl.php: successfully wrote INLINE file contents
  successfully changed file mode
file /usr/local/emhttp/plugins/denyhosts/event/disks_mounted: successfully wrote INLINE file contents
  successfully changed file mode
file /usr/local/emhttp/plugins/denyhosts/event/unmounting_disks: successfully wrote INLINE file contents
  successfully changed file mode
file /tmp/plugin-install: successfully wrote INLINE file contents
  /bin/bash /tmp/plugin-install ... DenyHosts-2.6/
DenyHosts-2.6/PKG-INFO
DenyHosts-2.6/denyhosts.py
DenyHosts-2.6/denyhosts.cfg-dist
DenyHosts-2.6/setup.py
DenyHosts-2.6/DenyHosts/
DenyHosts-2.6/DenyHosts/prefs.py
DenyHosts-2.6/DenyHosts/report.py
DenyHosts-2.6/DenyHosts/lockfile.py
DenyHosts-2.6/DenyHosts/__init__.py
DenyHosts-2.6/DenyHosts/plugin.py
DenyHosts-2.6/DenyHosts/denyfileutil.py
DenyHosts-2.6/DenyHosts/deny_hosts.py
DenyHosts-2.6/DenyHosts/regex.py
DenyHosts-2.6/DenyHosts/sync.py
DenyHosts-2.6/DenyHosts/counter.py
DenyHosts-2.6/DenyHosts/old-daemon.py
DenyHosts-2.6/DenyHosts/util.py
DenyHosts-2.6/DenyHosts/daemon.py
DenyHosts-2.6/DenyHosts/python_version.py
DenyHosts-2.6/DenyHosts/allowedhosts.py
DenyHosts-2.6/DenyHosts/filetracker.py
DenyHosts-2.6/DenyHosts/loginattempt.py
DenyHosts-2.6/DenyHosts/restricted.py
DenyHosts-2.6/DenyHosts/purgecounter.py
DenyHosts-2.6/DenyHosts/version.py
DenyHosts-2.6/DenyHosts/constants.py
DenyHosts-2.6/CHANGELOG.txt
DenyHosts-2.6/LICENSE.txt
DenyHosts-2.6/daemon-control-dist
DenyHosts-2.6/plugins/
DenyHosts-2.6/plugins/README.contrib
DenyHosts-2.6/plugins/shorewall_allow.sh
DenyHosts-2.6/plugins/shorewall_deny.sh
DenyHosts-2.6/plugins/test_deny.py
DenyHosts-2.6/scripts/
DenyHosts-2.6/scripts/restricted_from_invalid.py
DenyHosts-2.6/scripts/restricted_from_passwd.py
DenyHosts-2.6/README.txt
DenyHosts-2.6/MANIFEST.in
/usr/bin/env: python: No such file or directory
success
file /usr/local/emhttp/plugins/denyhosts/denyhosts.page: successfully wrote INLINE file contents
file /var/log/plugins/denyhosts: successfully wrote INLINE file contents
file /tmp/plugin-development: successfully wrote INLINE file contents
  /bin/bash /tmp/plugin-development ... success
plugin successfully installed

 

thahks for your help again & again

ermmm ok got the new version installed, seems to work fine.  logged in using FireSSH, try the "top" command and get this,

 

root@Tower:~# top
'xterm-256color': unknown terminal type.

 

I'd suggest your SSH program (FireSSH) is setting the wrong terminal emulation.  The top command is working fine via Putty/RoyalTS on my server (yes I use this SSH plugin )

ikosa, I have made an amendment to the plugin.  Please grab v1.1 from my github.  I think that should solve the issue.  Try first without other plugins, then with others also.

 

 

 

Regards,

overbyrn.

ermmm ok got the new version installed, seems to work fine.  logged in using FireSSH, try the "top" command and get this,

 

root@Tower:~# top
'xterm-256color': unknown terminal type.

 

I'd suggest your SSH program (FireSSH) is setting the wrong terminal emulation.  The top command is working fine via Putty/RoyalTS on my server (yes I use this SSH plugin )

 

hmmm i can't argue based on the evidence, but i didn't have this problem with the older version of SSH.  So that just leads me to wonder where I'm going to have to look for that.  FireSSH doesn't have many settings that i recall (can't look at it here at work ... stupid IE)

ikosa, I have made an amendment to the plugin.  Please grab v1.1 from my github.  I think that should solve the issue.  Try first without other plugins, then with others also.

 

yeap, now it is running thanks again.

 

i have a tiny last question:

my current setup has no cache disk and i have a 500gb usb disk mounting at the boot with ntfs-3g;

on which disk do i have to put my work directory: flash, usb or mounting another usb flash drive?

I am happy to hear you have it running. 

 

The work directory is best stored on either cache or non-array disk.  If on array, then I suspect it will prevent the disk from spinning down.  If on flash, you run the risk of reducing the lifespan through more writes than necessary.  You don't HAVE to have workdir on persistent storage.  It could go to a location that is in ram.  eg.  /usr/local/denyhosts or some such, but you will lose the history that it builds up on failed login names and hosts etc.  But DenyHosts doesn't absolutely need these things to help protect your system as it'll still continue to watch your syslog for failed SSH attempts so long as it's running.

 

 

 

Regards,

overbyrn

 

 

Hi,

 

I've got Crashplan installed via SeeDrs UI/Installer (http://lime-technology.com/forum/index.php?topic=15921.0), and the service is running, however when I setup an SSH tunnel as per instructions here:

 

http://support.crashplan.com/doku.php/how_to/configure_a_headless_client#uiproperties_file_location

 

I get an error on my unRAID terminal session when opening my desktop Crashplan app saying:

 

channel 3: open failed: connect failed: Connection refused

 

If I try and telnet from my desktop to my unRAID (ie telnet 10.0.0.241 4200) I get:

 

telnet: connect to address 10.0.0.241: Connection refused
telnet: Unable to connect to remote host

 

Help?

 

Thanks,

Shane.

did anyone try to use denyhosts with vsftp?

googled ant tried something but no success.

My SSH sessions is now refused, and i tested to disable the DenyHost app and does not work anyway...

 

Edit: ssh_exchange_identification: Connection closed by remote host

My SSH sessions is now refused, and i tested to disable the DenyHost app and does not work anyway...

 

Edit: ssh_exchange_identification: Connection closed by remote host

 

I am sorry, you have not provided enough information to fully explain the problem you are having.

 

Are you using OpenSSH and Denyhosts plugins?  What versions are you using?  How have you configured them?  Please give more information and then perhaps someone will be able to help you.

 

He probably did what I just did.  I can't believe I haven't done this sooner. Since the threshold for root was one, I had cap locks on when I tried to log in and a little bit later I was booted from my sessions and was banned from my server.  Had to login from another machine and edit the hosts-restricted file in the plugin data directory and remove my computers ip address.  Or I could have waited two weeks for the ban to be lifted :-).

I am running v 1.3 of the plugin.. but I can't get ssh keys to work.. I copied the authorized_keys file in /boot/config/plugins/ssh/root/.ssh

I checked and it does copy the file to /root/.ssh/authorized_keys

But ssh still keeps asking for the password.. (my key file is fine, I use that same file on a dozen other servers..)

 

Any ideas?

I am running v 1.3 of the plugin.. but I can't get ssh keys to work.. I copied the authorized_keys file in /boot/config/plugins/ssh/root/.ssh

I checked and it does copy the file to /root/.ssh/authorized_keys

But ssh still keeps asking for the password.. (my key file is fine, I use that same file on a dozen other servers..)

 

Any ideas?

Stupid question, but have you disabled password auth in the webgui settings?  If not, it'll ask for password regardless of if there's a key.

 

 

I am running v 1.3 of the plugin.. but I can't get ssh keys to work.. I copied the authorized_keys file in /boot/config/plugins/ssh/root/.ssh

I checked and it does copy the file to /root/.ssh/authorized_keys

But ssh still keeps asking for the password.. (my key file is fine, I use that same file on a dozen other servers..)

 

Any ideas?

Stupid question, but have you disabled password auth in the webgui settings?  If not, it'll ask for password regardless of if there's a key.

 

If I disable password auth i get this:

 

Mikes-MacBook-Air:~ Mike$ ssh tower

Permission denied (publickey,keyboard-interactive).

Mikes-MacBook-Air:~ Mike$

 

from my local config file for the tower entry:

 

Host tower

    HostName 192.168.234.10

    Port 22

    User root

I am running v 1.3 of the plugin.. but I can't get ssh keys to work.. I copied the authorized_keys file in /boot/config/plugins/ssh/root/.ssh

I checked and it does copy the file to /root/.ssh/authorized_keys

But ssh still keeps asking for the password.. (my key file is fine, I use that same file on a dozen other servers..)

 

Any ideas?

Stupid question, but have you disabled password auth in the webgui settings?  If not, it'll ask for password regardless of if there's a key.

 

If I disable password auth i get this:

 

Mikes-MacBook-Air:~ Mike$ ssh tower

Permission denied (publickey,keyboard-interactive).

Mikes-MacBook-Air:~ Mike$

 

from my local config file for the tower entry:

 

Host tower

    HostName 192.168.234.10

    Port 22

    User root

 

Do you have the private key on the client you're connecting from?  ie. the Macbook Air? 

 

Let's just go over the basic steps...

 

On your Unraid server (lets call it TOWER), you should have a user setup for ssh.  Lets call him "sshtest".  For that user you have an authorized_keys file inside the users directory under the plugins directory on the flash drive

You have password authentication = NO in the webgui

You have stopped and restarted SSH

You have checked /home/sshtest/.ssh on the Unraid server and there exists authorized_keys there also (automatically taken from the plugin dir during stop/start).

On the computer are connecting from, you have placed a copy of the *private* key file "id_rsa" as found in the plugin directory on flash drive.  eg.  /boot/config/plugins/openssh/sshtest/id_rsa.

Let's assume the PC your are wanting to connect from is called "Mikes-MacBook-Air" and the user on that PC is "Mike"

Make sure there is a copy of id_rsa at /home/Mike/.ssh

chmod 600 id_rsa

ssh sshtest@TOWER

root@debian:~/.ssh# ssh sshtest@tower

Enter passphrase for key '/root/.ssh/id_rsa':

Linux 3.9.6p-unRAID.

(in my above example, I had set a passphrase)

 

 

Regards,

overbyrn

 

I am trying to use your OpenSSH plugin, but I didn't manage to make a connection between Putty and the Tower (unRaid server).

i have unRaid 5.0-rc14, this are my installation steps:

1.) I installed your OpenSSH v1.3

2.) OpenSSH appeared in Network Services

3.) under MENU->Setting->Open SSH I configured the SSH with following parameters: Enable SSH (Yes), Permit Root login (Yes), Max Auth Retries (6), Password Authentication (No), Permit empty password (Yes), Gateway ports (Yes).

4.) I generated id_rsa, id_rsa.pub in the directory \\TOWER\flash\config\plugins\ssh\root\.ssh\

5.) cp id_rsa.pub authorized_keys

6.) generated id_rsa.ppk with puttygen

7.) copied authorized_keys from \\TOWER\flash\config\plugins\ssh\root\.ssh\ to \\TOWER\flash\config\plugins\ssh\  (may be not needed ?)

8.) Restart SSH Daemon

9.) in Putty->Connection->SSH->Auth->Private key file for authentication: c:\...\id_rsa.ppk

10.) Open Putty sesstion to Tower (SSH) on port 22

11.) Putty complains: Server unexpectedly closed network connection

12.)  Unraid LOG: Tower sshd[12842]: refused connect from 192.168.x.x (192.168.x.x)

13.) \\TOWER\root\.ssh\authorized_keys is present in filesystem

14.) \\TOWER\home directory is completely empty. not even the subdirectory \root is there

 

thanks for any hints.

 

 

I am trying to use your OpenSSH plugin, but I didn't manage to make a connection between Putty and the Tower (unRaid server).

i have unRaid 5.0-rc14, this are my installation steps:

1.) I installed your OpenSSH v1.3

2.) OpenSSH appeared in Network Services

3.) under MENU->Setting->Open SSH I configured the SSH with following parameters: Enable SSH (Yes), Permit Root login (Yes), Max Auth Retries (6), Password Authentication (No), Permit empty password (Yes), Gateway ports (Yes).

4.) I generated id_rsa, id_rsa.pub in the directory \\TOWER\flash\config\plugins\ssh\root\.ssh\

5.) cp id_rsa.pub authorized_keys

6.) generated id_rsa.ppk with puttygen

7.) copied authorized_keys from \\TOWER\flash\config\plugins\ssh\root\.ssh\ to \\TOWER\flash\config\plugins\ssh\  (may be not needed ?)

8.) Restart SSH Daemon

9.) in Putty->Connection->SSH->Auth->Private key file for authentication: c:\...\id_rsa.ppk

10.) Open Putty sesstion to Tower (SSH) on port 22

11.) Putty complains: Server unexpectedly closed network connection

12.)  Unraid LOG: Tower sshd[12842]: refused connect from 192.168.x.x (192.168.x.x)

13.) \\TOWER\root\.ssh\authorized_keys is present in filesystem

14.) \\TOWER\home directory is completely empty. not even the subdirectory \root is there

 

thanks for any hints.

 

For step 5 above, did you do this manually or did you let the plugin do it?  If you manually did a "cp" of the file from plugin dir to /root/.ssh then you'll need to chmod 666 authorized_keys.  SSH refuses to allow a connection unless that file has those permissions.  You can let the plugin do it.  With /root/.ssh empty, stop and start the plugin (not restart button).  It'll copy the id_rsa from plugin dir to /root/.ssh and change the permissions.

 

For step 14, that's correct, as you're not creating a non-root user, so /home will be empty.

 

 

 

 

For step 5 above, did you do this manually or did you let the plugin do it?  If you manually did a "cp" of the file from plugin dir to /root/.ssh then you'll need to chmod 666 authorized_keys.  SSH refuses to allow a connection unless that file has those permissions.  You can let the plugin do it.  With /root/.ssh empty, stop and start the plugin (not restart button).  It'll copy the id_rsa from plugin dir to /root/.ssh and change the permissions.

 

For step 14, that's correct, as you're not creating a non-root user, so /home will be empty.

 

 

i did actually manually execute this (in Windows with Total Commander, but the result is the same):

cp \\TOWER\flash\config\plugins\ssh\root\.ssh\id_rsa.pub \\TOWER\flash\config\plugins\ssh\root\.ssh\authorized_keys

 

i didn't manually copy the authorized_keys to \TOWER\root\.ssh\authorized_keys, it was done by the script.

 

What do you mean by "start the plugin" ? Do you mean rebooting unRaid ?

should i delete the  /root/.ssh/id_rsa before reboot (plugin will be installed after the reboot automatically, if i understand this correctly) ?

 

 

i did actually manually execute this (in Windows with Total Commander, but the result is the same):

cp \\TOWER\flash\config\plugins\ssh\root\.ssh\id_rsa.pub \\TOWER\flash\config\plugins\ssh\root\.ssh\authorized_keys

 

i didn't manually copy the authorized_keys to \TOWER\root\.ssh\authorized_keys, it was done by the script.

 

What do you mean by "start the plugin" ? Do you mean rebooting unRaid ?

should i delete the  /root/.ssh/id_rsa before reboot (plugin will be installed after the reboot automatically, if i understand this correctly) ?

 

Hmm, whatever is wrong is something very simple I suspect.  We just need to get to the bottom of it.  Before writing this I did all the steps here to make sure nothing was missing.  I'm pretty sure my steps match yours but I'll describe them here in case something obvious shows up that's different :-

 

1. Starting with a vanilla copy of UnRAID rc15a (only SimpleFeatures installed, no other plugins)

2. installplg /boot/config/plugins/openssh_overbyrn.plg

3. In OpenSSH UnRAID WebGUI page:

  Enable SSH Service : Yes

  Permit Root Login: Yes

  Max Auth Retries: 6

  Password Authentication: No

  Permit Empty Passwords: Yes

  Gateway Ports: Yes

  Apply (SSH starts)

 

4. Using Putty, telnet to UnRAID server, generate a private / public keypair:

ssh-keygen -t rsa -f /boot/config/plugins/ssh/root/.ssh/id_rsa

Generating public/private rsa key pair.

Created directory '/root/.ssh'.

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /boot/config/plugins/ssh/root/.ssh/id_rsa.

Your public key has been saved in /boot/config/plugins/ssh/root/.ssh/id_rsa.pub.

 

5. Create "authorized_keys" file from "id_rsa.pub":

cp /boot/config/plugins/ssh/root/.ssh/id_rsa.pub /boot/config/plugins/ssh/root/.ssh/authorized_keys

 

6. Create putty compatible version of the private key:

puttygen /boot/config/plugins/ssh/root/.ssh/id_rsa -o /boot/config/plugins/ssh/root/.ssh/id_rsa.ppk

 

7. From OpenSSH UnRaid WebGUI settings page, Stop SSH Daemon, Start SSH Daemon

8. Verify "authorized_keys" file has been assigned to root user:

root@Tower:~# ls -la /root/.ssh

drwx------ 2 root root  0 2013-06-21 16:26 ./

drwx--x--- 3 root root  0 2013-06-21 16:25 ../

-rw------- 1 root root 392 2013-06-21 16:25 authorized_keys

 

9. Open up Putty and create new session:

Hostname: tower

Port: 22

Connection -> SSH -> Auth: browse to my Unraid where .ppk file is.  eg. \\tower\flash\config\plugins\ssh\root\.ssh\id_rsa.ppk

 

10. Connect

      Login as root

login as: root

Authenticating with public key "imported-openssh-key"

Last login: Fri Jun 21 16:28:12 2013 from office.lan

Linux 3.9.6p-unRAID.

root@Tower:~#

 

As I say, I do not think I have done as you also, but there must be some minor thing that is different as for me the process worked.  I can only suggest you review the steps and perhaps repeat in case something was missed the first time.

 

 

Regards,

overbyrn