I am seeing some posts saying that a blog posting may not be considered sufficient in court for proving prior art. However, I'm curious to know how an actual working implementation of an unpatented idea would be seen. For example, once an idea becomes part of a software product documented version history would that be seen as prior art?
While FTP is insecure in that username/password credentials are sent unprotected over the wire, I would argue that very few FTP servers are actually compromised in this way (sniffing the wire). Most FTP servers are compromised by automated brute force username/password attacks and weak user passwords. Even if you are using a secure protocols (SFTP, SCP) these protocols are still subject to these attacks unless you have measures in place to prevent it. Take a look at your server logs and I'm sure you will find several failed authentication attempts against port 22. One of the simplest things that admins can do to reduce hacks is to automatically ban an IP after too many failed logins. For SSH a tool like DenyHosts is really simple to install.
Slashdot Mirror
I am seeing some posts saying that a blog posting may not be considered sufficient in court for proving prior art. However, I'm curious to know how an actual working implementation of an unpatented idea would be seen. For example, once an idea becomes part of a software product documented version history would that be seen as prior art?
While FTP is insecure in that username/password credentials are sent unprotected over the wire, I would argue that very few FTP servers are actually compromised in this way (sniffing the wire). Most FTP servers are compromised by automated brute force username/password attacks and weak user passwords. Even if you are using a secure protocols (SFTP, SCP) these protocols are still subject to these attacks unless you have measures in place to prevent it. Take a look at your server logs and I'm sure you will find several failed authentication attempts against port 22. One of the simplest things that admins can do to reduce hacks is to automatically ban an IP after too many failed logins. For SSH a tool like DenyHosts is really simple to install.