On 10 September 2012 17:58, Tim Schaub <tsch...@opengeo.org> wrote:
> I wanted to add a quick note to say that admins should be able to
> disable this feature. The security concern is minor, but it's a real
> hole that may raise red flags in some audits. Here's the (obviously
> contrived) situation where this allows "secure" data to leak to an
> evil hacker.
>
> Agent Geo is a staffer at a facility with data they hope to keep
> secure. Agent Geo runs a GeoServer that is available at
> http://localhost:8080/geoserver/, and has recently been browsing his
> top:secret feature type; having been prompted by GeoServer to enter
> his credentials, he did so. While on a lunch break, Agent Geo visits
> http://evilhacker.com/ a site maintained by Evil Hacker. Evil Hacker
> has been waiting for someone with a GeoServer on localhost and a
> feature type named top:secret to stumble upon his site.
Wouldn't that be topp:secret?
Sorry couldn't resist :-)
Ian
--
Ian Turton
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
