i just started using KISS.. but i face the problem of ssh dropping connections after i enter the correct password. any idea what's going on?
here's the verbose output from the ssh client
debug1: Next authentication method: password [email protected]'s password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: ssh_session2_setup: id 0
debug1: channel 0: request pty-req
debug1: channel 0: request shell
debug2: callback done
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: channel_free: channel 0: client-session, nchannels 1
Connection to mydomain.com closed by remote host.
Connection to mydomain.com closed.
debug1: Transferred: stdin 0, stdout 0, stderr 95 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 1280.5
debug1: Exit status -1
restarting sshd service will allow me to connect once. but once i disconnect that session and try to connect again from a different computer, the same problem comes back again. i can't keep going back to the server to restart sshd all the time. pls help. thanks.
hi just installed kiss. Now i would like to block SMTP on port 25 in order to prevent user can send mails using: maildomain.com (i like they use mail.thereisp.com)
How do i block port 25 ?
I made the following config but it does not work or in other words i can still send e-mails by using maildomain.com
TCP_IN="20 21 25 53 80 110 143 443 995 2082:2083 2086:2087 2089 2095:2096 3306 8443 10000 19638"
TCP_OUT="21 22 37 43 53 80 443 873 2089 55000"
Actually, just installing one Linksys Model BEFSX41 Firewall Router (less than US$99) per webserver is the better solution.
1) Issue the public IP address to the outside of the router (the one that was formerly used for the webserver)
2) Issue a static private address for the webserver from the safe side of the router. [As necessary, reconfigure virtual website bindings to the new IP address that's local.]
3) Set up a Static Route for port 80 to the private IP address of the webserver.
4) Optionally, open up the port for VNC or similar remote control software.
* At $100 each you've dedicated it to a single webserver. This is a very nice insurance policy, blocking all kinds of inbound stuff you and your software solution didn't think of.
* Since it's dedicated to one box, it can handle all the bandwidth your webserver can dish out.
* Since it's hardware, it's not robbing your webserver of processing time.
* You can't solve an upstream problem (DDoS) with a downstream solution (software-based firewall). Trust me on this.
* You can also throw database servers there on the private networks this now creates on your LAN and you can place them locally to where you need them. And they don't consume a valuable public IP address.
* I buy them in bulk so that I can have a few lying around in their packages. I bought a 30A DC power supply so that I can power several of them without taking up too much valuable "power strip" space.
* I use a laptop in the datacenter to configure them via a browser interface. Very little tweaking is required from the default setup. Max install time for one with me now is less than ten minutes total.
* With VNC installed on the webserver you as admin can remote control the webserver and use its browser to open up the HTTP-based interface for the router (since you're now on the trusted side of the router). By reconfiguring the default port for VNC you can minimize VNC hacking attempts.
* You'd want to test this on a system that has an existing digital certificate applied to a secure webserver. I'm reasonably sure that the digital certificate has that original IP address bound into it. Nonetheless, the arriving SSL packet may still work out because that IP address arrived to the webserver.