That page was originally being worked on for a point I was going to make
to my last employer.  I can update it with the stored procedure info,
but then I have to also go back through and see if anything else has
changed since I'd have to also list the version of MySQL that I'm
comparing.

Kevin Brown wrote:
> 
> I can reach that site from Qwest.
> 
> On your SQL Server comparison chart, MySQL now has stored procedures using
> myperl.  Saw the link to it on Slashdot a few days ago.
> 
> I think logins for MySQL are restricted based on entries in the mysql db that
> controls hosts/db/permissions.
> 
> > You got me how or why, but I can reach port 80 on my system from outside
> > the @Home service.
> > Would others outside of @Home care to test this?  (Just in case the
> > hosting service I shell to is somehow within @Home's domain.)
> > http://wokan.home.dhs.org/
> 
> > > > [...]
> > > > Have you ever seen NNTP scans from networks other than @Home's?  Or
> > > rather,
> > > > do you think they would ever think to do port scans from a network other
> > > > than their own?  I'm guessing not, so I just have my firewall block
> > > > everything with a source address of 24.0.0.0/8, and then allow in any
> > > > specific addresses in that range that I want to have access to my
> > > services.
> > > > So far that's worked for the last 2.5 years or so....
> > > That may have worked in the past, but from what I've seen, all access to
> > > ports 80 and 25 is blocked coming into their network, not just to specific
> > > hosts.  Port 80 to my system is definitely blocked, even though I definitely
> > > had nothing running there. Same on a couple of others locally. If they just
> > > shut it off at the edge(s) of their network, they don't have to bother with
> > > scanning anymore. I'm not sure if this is a Cox or an @Home initiative.
> > > - Bob