[HowTo] Make ispCP more Secure ! - Printable Version +- ispCP - Board - Support (http://www.isp-control.net/forum) +-- Forum: ispCP Omega Contributions Area (/forum-40.html) +--- Forum: Howtos (/forum-41.html) +--- Thread: [HowTo] Make ispCP more Secure ! (/thread-257.html) |
RE: [HowTo] Make ispCP more Secure ! - Boter - 01-15-2010 03:26 AM Hey! For disabling Apache ServerInfo in debian, you probably even don't have included httpd.conf, so include it in apache2.conf OR add ServerSignature Off ServerTokens Prod in apache2.conf RE: [HowTo] Make ispCP more Secure ! - Diego - 04-07-2010 01:28 PM Thanks, but the link from the first post is broken. RE: [HowTo] Make ispCP more Secure ! - gOOvER - 04-07-2010 02:17 PM I updated the link in the first post. Now it works again RE: [HowTo] Make ispCP more Secure ! - kfa - 07-03-2010 10:31 AM First post, so Hey All! =) Now to subject. On ubuntu 8.04 (hardy), enabling secure connection on proftpd wont work, as ubuntu repo's have old 2.06 proftpd as it seems...anytime user tries to connect with up to date filezilla on secure connection they fail with error: __ Status: Server did not properly shut down TLS connection Error: Could not read from transfer socket: ECONNABORTED - Connection aborted .. __ I was googling around a little and find a solution (http://forum.filezilla-project.org/viewtopic.php?f=2&t=13034) that worked for me; Quote:vim /etc/apt/sources.list Add 2 sources to list: Quote:deb http://ppa.launchpad.net/cschieli/ppa/ubuntu hardy main And simply run: Quote:sudo aptitude Update and upgrade of proftpd solved my problems..got few warnings for repo's as they are unofficial, but well..it worked Please note, that i'm a linux newb...so use it on your own risk. In any case, hope it will help to anyone. GreetZ [Solved] RE: [HowTo] Make ispCP more Secure ! - Mr.Sisko - 02-25-2011 03:49 AM Since ispPC 1.0.7 the Options for allow-recursion must be placed in /etc/bind/named.conf.options like Quote:options { This only work for me. Greetz Update: shit,... now i've got some errors like network unreachable resolving 'ns2.lacnic.net/AAAA/IN' Update2: okay, looks like troubles with ipv6 Support, how can i fix this? My Server dosn't have ipv6 Update3: i'm so stupid Just enable IPV6-Support for the Server and that's it. Problem Solved |