Re: opened OpenSSL port

2011-03-05 Thread Chris Davies
> Chris Davies a écrit : >> /etc/hosts.allow could provide a level of protection for names matching, >> e.g. "*.dyndns.org". Pascal Hambourg wrote: > This won't work, because usually the reverse DNS is not in *.dyndns.org. > somename.dyndns.org -> IP address -> some other name defined by the ISP

Re: opened OpenSSL port

2011-03-05 Thread Pascal Hambourg
Hello, Chris Davies a écrit : > erikmccaskey64 wrote: > >> Are there any iptables rule for restricting connections to dyndns names? >> e.g.: only allow connection from "asdfasdf.dyndns.com" and >> "asdfasdf2.dyndns.com" and "asdfasdf3.dyndns.com"? > > No. Iptables is about IP addresses (and por

Re: opened OpenSSL port

2011-03-02 Thread Chris Davies
erikmccaskey64 wrote: > Main question: is it safe, to open a port for an openssl server? No, it's not 100% safe. One has to evaluate the risk vs requirement and act accordingly. > Is it secure? - it could be DOSed' [DenialofService] or could it be > attacked in any way? Yes, of course it can.

Re: opened OpenSSL port

2011-02-27 Thread Jeffrin Jose
On Sun, Feb 27, 2011 at 01:50:24AM -0800, erikmccaskey64 wrote: > Main question: is it safe, to open a port for an openssl server? It may be safe not to open a port because it can cause attacks. It may not be safe to close a port because you may not be able to run the service. So it may be safe

opened OpenSSL port

2011-02-27 Thread erikmccaskey64
Main question: is it safe, to open a port for an openssl server? e.g.: server side - generate a self-signed cert. time openssl req -x509 -nodes -days 365 -newkey rsa:8192 -keyout mycert.pem -out mycert.pem openssl s_server -accept 52310 -cert mycert.pem Is it secure? - it could be DOSed' [