- nuXleus Web Application & Messaging ....
- Version 0.2.3.4
- nuXleus Web Application & Messaging ....
- Version 0.2.3.4
- nuXleus Web Application & Messaging ....
- Version 0.2.3.4
- mono:source
- 105700-0.1 (12-Jun-2008)
- ejabberd:source
- 2.0.1_2-0.1 (11-Jun-2008)
- erlang:source
- R12B_3-0.4 (11-Jun-2008)
- erlang:source
- R12B_3-0.3 (11-Jun-2008)
- erlang:source
- R12B_3-0.2 (11-Jun-2008)
- erlang:source
- R12B_3-0.1 (11-Jun-2008)
- xsp:source
- 101751-0.1 (03-Jun-2008)
- mono:source
- 104738-0.1 (03-Jun-2008)
- Saxon.NET:source
- 9.0.0.6-0.2 (02-Jun-2008)
- Saxon.NET:source
- 9.0.0.6-0.1 (02-Jun-2008)
Don't have an account?
Set one up.
nuXleus Web Application & Messaging Appliance
Product Home Page
Description
The nuXleus Project has the specific intent to become a User-Centric/Specific Application and XML messaging virtualization-based appliance in which a primary, user-specific/centric host machine can use as a secured proxy for all web-based communications.
PLEASE NOTE: Please keep in mind this project is not intended nor designed as a stand alone solution. Instead we have the specific intent to develop integrated solutions to work with existing operating system installs, acting as a virtual and secure gateway to the web in which our host OS can then use as a proxy, and in doing so minimizing the exposure to the outside world.
Our goal, in fact, is to reduce this exposure to ZERO, using nuXleus as the primary and only point of contact to the outside web, while acting as our personal, online presence hosting provider. Using this synopsis, nuXleus can then provide a safe and secured environment to provide extended web-based services built around the overall vision of the Semantic Web*, ensuring that our personal host OS never has the need to risk that which could lead to any type of malware, virus, worm, or other form of threat from the outside world by limiting ALL communications to first pass through the nuXleus interface, to then be examined for potential threats, checked for proper security credentials, passing the result to the host system if, and only if, ALL security processes in place have given each specific message the green light to be passed through a single secured port on the host machine.
110% secure**, 100% of the time.
** - This is meant to invoke the idea of taking the security side of this project to a level just above that which is felt to be secured such that we can always keep the focus on staying one step ahead of the blackhat hacker community, but avoiding taking things too far into the extreme as to cripple the functionality and/or usability and therefore overall benefit to the individual who utilize the services of this project. In other words, if we lock down the system in such a way that the security can be compared to unplugging the machine from the power outlet, this project has ultimately failed.