DSM-G600, DNS-3xx and NSA-220 Hack Forum

Just tried your python package and I managed to install and run trac ( http://trac.edgewall.org/ ).
Very cool!

forre wrote:

openssh was needed to recompile with --with-tcp-wrappers

I've updated my openssh package and recompiled with --with-tcp-wrappers, so you don't need to maintain a separate version.

fonz wrote:

Just tried your python package and I managed to install and run trac ( http://trac.edgewall.org/ ).
Very cool!

Fonz, what additional steps did you have to do to get trac running? I am still struggeling getting this to work...

Geir

fonz wrote:

reddwarf wrote:

Fonz, what additional steps did you have to do to get trac running? I am still struggeling getting this to work...

I didn't do anything special, and only followed their instructions: http://trac.edgewall.org/wiki/TracInstall and then ran the standalone server tracd.
It's a little slow, though.

I have Python, have sqlite, and have downloaded Trac. When I try to install I get the following error message:

root@dlink-68633D:/mnt/HD_a2/Trac-0.11b2# python setup.py install
Traceback (most recent call last):
  File "setup.py", line 15, in <module>
    from setuptools import setup, find_packages
ImportError: No module named setuptools

I have checked the Python package directory and have not found the setuptools there... Did you download this separately?

Cheers,

Geir

After struggling for some time to get this to work, Im writing the two problems I had and the solutions to them in case someone else run into them.

first: I only got one syslog event from my sshd at boot and then no more despite successful and failed login attempts.
solution: While installing chrooted Pure-ftpd in debian, I activated debian syslogd/klogd and with two syslogd running on my system, the sshd messages were lost. I.e. with syslog running in ffp, do not run it in debian as well

second: I had an error with the binary tcpd could not be found. This was solved by downloading the ffp 0.5 package tcp-wrappers and installing

with these two modifications, I have now denyhosts up and running!

bvanveelen wrote:

Do you guys have any idea how I can connect to my NAS via the PuTTY client now?

http://dns323.kood.org/howto:ffp#the_root_user

See 'Reactivating telnet' near the end of that section.

bvanveelen wrote:

PS: I don't really understand why I would want to shut down either telnet or ssh permanantly in any case. What's the reason behind this?

Security?  If ssh/telnet aren't running nobody can get console access to your box and do anything nasty!  Of course you may have other security like firewall or router blocking the ports that they use, but why have them running if you don't need them?  If you need access then use ssh and disable telnet.
lu

from earlier:

saltisol wrote:

second: I had an error with the binary tcpd could not be found. This was solved by downloading the ffp 0.5 package tcp-wrappers and installing

as reference to anyone else who's encountering a problem with tcpd being missing:

my tcpd was missing from /ffp/sbin as well, so I uninstalled tcp-wrapper and reinstalled.

For some reason the binaries weren't being copied to /ffp/sbin, so I needed to manually copy the files from the tgz via scp.

Don't know why the installer wasn't working for tcp-wrapper, but the installation of DenyHosts worked after that.

Hello all,

I've recently setup deny hosts following your instructions which works perfectly when left on the default port 22.  So when I try to change to a different port I tried changing these lines in inetd.sh:

if ! grep '^ssh' /etc/services >/dev/null; then
     echo "ssh                3322/tcp" >> /etc/services

which seems to work for the SSHD port but denyhosts does not seem to pickup on the invalid logins.

Since the start script launches SSHD through inetd.sh now required_files="/ffp/etc/ssh/sshd_config" isn't specified in start script inetd.sh like it is in sshd.sh however it still seems to effect the settings so I also changed it specifying port 3322. 


Any ideas why this doesn't work ?

Thanks.

Last edited by Hovertron (2009-04-17 01:31:04)

I discovered a small bug in the script. The "sh /ffp/start/denyhost.sh status" command is not working because of the following typo in /ffp/start/denyhost.sh:

staus_cmd="denyhosts_status"

replace it by

status_cmd="denyhosts_status"

Other than that and the lock file, it is working great!!

link is dead for denyhosts repo, someone have this for funplug 0.5?