OSA::net project main goal is to create an extensible, scalable framework for management of security related devices in middle-sized and large computer networks.
Be the first to post a text review of OSA::net. Rate and review a project by clicking thumbs up or thumbs down in the right column.
OSA::net is cross platfrom, multi vendor security management framework. On Monday, 12 January 2004 OSA::net OSA::net released it's first binaries including security policy editor, database and basic enforcement mechanism. Although still at the alpha stage, our architecture is now defined clearly. Release 0.0.1 being OSA::net technology preview unveils powerful three tiered architecture composed of: 1. OSA::Control, an universal GUI editor capable of creating security policy for various target devices 2. OSA::HQ, a database keeping policies accessible to administrators 3. OSA::Tower, a thin, yet universal policy translation and enforcement mechanism Release is mainly targeted at developers at this time. More details on http://osa-net.sourceforge.net
--- Mon, 17 Nov 2003 --- release 0.1.1 --- STATUS: Initial release. OSA::HQ, OSA::Tower and GUI implementation of OSA::Control ready. No authentication between these modules implemented yet. BUGS: Lots of ; ) Truly this should be treated as preview and has not undergone real testing. Significant problems exist with polymorphic deserialization server side (they will be resolved in next release). This bug prevents user from successfully editing action parameter in policy table. It leaves editor and is properly marshalled, byt the server side is unable to understand it's serialized form. TODO: Authentication Other modules described by the architecture Better caching for PolicyRegistry Documentation gathering and reedition
--- Mon, 17 Nov 2003 --- release 0.1.1 --- STATUS: Initial release. OSA::HQ, OSA::Tower and GUI implementation of OSA::Control ready. No authentication between these modules implemented yet. BUGS: Lots of ; ) Truly this should be treated as preview and has not undergone real testing. Significant problems exist with polymorphic deserialization server side (they will be resolved in next release). This bug prevents user from successfully editing action parameter in policy table. It leaves editor and is properly marshalled, byt the server side is unable to understand it's serialized form. TODO: Authentication Other modules described by the architecture Better caching for PolicyRegistry Documentation gathering and reedition
--- Mon, 17 Nov 2003 --- release 0.1.1 --- STATUS: Initial release. OSA::HQ, OSA::Tower and GUI implementation of OSA::Control ready. No authentication between these modules implemented yet. BUGS: Lots of ; ) Truly this should be treated as preview and has not undergone real testing. Significant problems exist with polymorphic deserialization server side (they will be resolved in next release). This bug prevents user from successfully editing action parameter in policy table. It leaves editor and is properly marshalled, byt the server side is unable to understand it's serialized form. TODO: Authentication Other modules described by the architecture Better caching for PolicyRegistry Documentation gathering and reedition
--- Mon, 17 Nov 2003 --- release 0.1.1 --- STATUS: Initial release. OSA::HQ, OSA::Tower and GUI implementation of OSA::Control ready. No authentication between these modules implemented yet. BUGS: Lots of ; ) Truly this should be treated as preview and has not undergone real testing. Significant problems exist with polymorphic deserialization server side (they will be resolved in next release). This bug prevents user from successfully editing action parameter in policy table. It leaves editor and is properly marshalled, byt the server side is unable to understand it's serialized form. TODO: Authentication Other modules described by the architecture Better caching for PolicyRegistry Documentation gathering and reedition
--- Mon, 17 Nov 2003 --- release 0.1.1 --- STATUS: Initial release. OSA::HQ, OSA::Tower and GUI implementation of OSA::Control ready. No authentication between these modules implemented yet. BUGS: Lots of ; ) Truly this should be treated as preview and has not undergone real testing. Significant problems exist with polymorphic deserialization server side (they will be resolved in next release). This bug prevents user from successfully editing action parameter in policy table. It leaves editor and is properly marshalled, byt the server side is unable to understand it's serialized form. TODO: Authentication Other modules described by the architecture Better caching for PolicyRegistry Documentation gathering and reedition
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?