Re:"You've angered the hive"
by Tautologistics on Monday February 07, 2011 @05:03PM
(#2190966)
OK, so then forget your "super secure" server. I would instead focus on compromising one of the admin computers that has the "special user" ssh key and the port knock sequence; or maybe I will hit one of the servers communicating with this "secure" computer and see if you remembered to bounds check all the data coming in; maybe even see if you network stack has any exploits in its tcp/udp implementations while I am at it...
[ Parent
| on HN ]
Re:"You've angered the hive"
by stcredzero on Monday February 07, 2011 @05:16PM
(#2191008)
OK, so then forget your "super secure" server. I would instead focus on compromising one of the admin computers that has the "special user" ssh key and the port knock sequence
Juicy! [making notes to buy a laptop for the express purpose of logging into the server]
maybe I will hit one of the servers communicating with this "secure" computer and see if you remembered to bounds check all the data coming in
All fields are fixed length.