pluto
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7
Apache Pluto 1.0.1
Pluto is the reference implementation of the Java Portlet Specification (JSR-168). more>>
Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is JSR 168.
Portlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)
<<lessPortlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)
Download (11.6MB)
Added: 2005-10-20 License: The Apache License 2.0 Price:
1471 downloads
Pluto Request Action Library 2.0.0.36
Pluto Request Action Library is a library that makes it easy to create a client/server application. more>>
Pluto Request Action Library allows you to create a client/server application, where client sends requests, server replies with responses and optional actions. Very object oriented, and takes only minutes to get going. Same library used for both server & client side.
How does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
<<lessHow does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
Download (0.37MB)
Added: 2006-02-09 License: GPL (GNU General Public License) Price:
1354 downloads
Pluto Bi-Directional Comm library 2.0.0.38
Pluto Bi-Directional Comm library automates bi-directional communication over bluetooth or sockets. more>>
Pluto Bi-Directional Comm library automates bi-directional communication over bluetooth or sockets. Very object oriented and easy to use. Allows 2 devices to send each other commands.
The framework handles all the handshaking & protocols, and provides a template for commands.
How does it work?
This library allows 2 devices to communicate with each other over sockets or a Bluetooth connection. BD handles the handshaking, communication protocol, and provides a very simple way to send and implement commands.
Both sides are truly peers, and either side send the other a command by creating an instance of the command. Each side creates an instance of BDCommandProcessor, and then either side can create an instance of a command, add it to BDCommandProcessor, and the other side will implement the command. Each command is really just a simple class derived from BDCommand.
You only add whatever member variables your command, and implement a pure virtual "ProcessAction" member function. When one side wants to send that command to the other, it just creates an instance of it, sets member variables, and passes it to the "SendCommand" function in BDCommandProcessor.
The framework will automatically serialize the member variables in the class, and send the data to the other side. On the other side, the framework will recreate the class with the member variables set, and call the "ProcessAction" function which you implement to do whatever the command is supposed to do.
Your software doesnt need to worry about any of the data serialization, or the handshaking, or the sending of the commands. The framework handles all that--you just implement the "ProcessAction" function.
<<lessThe framework handles all the handshaking & protocols, and provides a template for commands.
How does it work?
This library allows 2 devices to communicate with each other over sockets or a Bluetooth connection. BD handles the handshaking, communication protocol, and provides a very simple way to send and implement commands.
Both sides are truly peers, and either side send the other a command by creating an instance of the command. Each side creates an instance of BDCommandProcessor, and then either side can create an instance of a command, add it to BDCommandProcessor, and the other side will implement the command. Each command is really just a simple class derived from BDCommand.
You only add whatever member variables your command, and implement a pure virtual "ProcessAction" member function. When one side wants to send that command to the other, it just creates an instance of it, sets member variables, and passes it to the "SendCommand" function in BDCommandProcessor.
The framework will automatically serialize the member variables in the class, and send the data to the other side. On the other side, the framework will recreate the class with the member variables set, and call the "ProcessAction" function which you implement to do whatever the command is supposed to do.
Your software doesnt need to worry about any of the data serialization, or the handshaking, or the sending of the commands. The framework handles all that--you just implement the "ProcessAction" function.
Download (0.20MB)
Added: 2006-02-24 License: GPL (GNU General Public License) Price:
1338 downloads
LinuxMCE 1.1 Beta 2
LinuxMCE is a free, open source add-on to Ubuntu including a 10 UI, complete whole-house media solution with pvr + media. more>>
LinuxMCE is a free, open source add-on to Ubuntu including a 10 UI, complete whole-house media solution with pvr + distributed media, and the most advanced smarthome solution available. The project is stable, easy to use, and requires no knowledge of Linux and only basic computer skills.
Enhancements:
- LinuxMCE Version 1.1 for Kubuntu Feisty represents a significant change over 1.0. The code in LinuxMCE 1.0 was already quite stable, however, many users reported installation issues, too many scripts inherited from Pluto that took over the conf files, a kludgey integration with Ubuntu, and incomplete integration with MythTV. All these are addressed in the new 1.1.
<<lessEnhancements:
- LinuxMCE Version 1.1 for Kubuntu Feisty represents a significant change over 1.0. The code in LinuxMCE 1.0 was already quite stable, however, many users reported installation issues, too many scripts inherited from Pluto that took over the conf files, a kludgey integration with Ubuntu, and incomplete integration with MythTV. All these are addressed in the new 1.1.
Download (MB)
Added: 2007-06-11 License: GPL (GNU General Public License) Price:
870 downloads
strongSwan 2.8.3
strongSwan is an OpenSource IPsec implementation for the Linux operating system. more>>
strongSwan is an OpenSource IPsec implementation for the Linux operating system. strongSwan is based on the discontinued FreeS/WAN project and the X.509 patch which we developped over the last three years.
In order to have a stable IPsec platform to base our future extensions of the X.509 capability on, we decided to lauch the strongSwan project.
Main features:
- runs both on Linux 2.4 (KLIPS) and Linux 2.6 (native IPsec) kernels
- strong 3DES, AES, Serpent, Twofish, or Blowfish encryption
- Authentication based on X.509 certificates or preshared keys
- Powerful IPsec policies based on wildcards or intermediate CAs
- Retrieval and local caching of Certificate Revocation Lists via HTTP or LDAP
- Full support of the Online Certificate Status Protocol (OCSP, RCF 2560).
- Optional storage of RSA private keys on smartcards or USB crypto tokens
- Smartcard access via standardized PKCS #11 interface
- PKCS #11 proxy function offering RSA decryption services via whack
- NAT-Traversal (RFC 3947) and support of Virtual IPs and IKE Mode Config
- CA management (OCSP and CRL URIs, default LDAP server)
- Dead Peer Detection (DPD, RFC 3706)
- Group policies based on X.509 attribute certificates ( RFC 3281)
- Generation of default self-signed certificates during strongSwan setup
Whats New in 2.8.0 Stable Release:
- The implementation of the IKE Mode Config push mode allows interoperability with Cisco VPN gateways.
- By setting "modeconfig=push", strongSwan will wait for the peer to push down a virtual IP address that can be used within an IPsec tunnel.
- The default value of the new keyword is "modeconfig=pull".
- The command "ipsec statusall" now shows "DPD active" for all ISAKMP Security Associations that are under active Dead Peer Detection control.
Whats New in 4.0.7 Development Release:
- Extended authentication (XAUTH) in conjunction with IKE Main Mode authentication (RSA and PSK) is now possible with most VPN clients and gateways (e.g. Cisco, NCP, Shrew, etc.).
Whats New in 2.8.3 Stable Release:
- A bug in the computation of the SHA-512-HMAC function was fixed.
- The SHA-384 hash and HMAC functions were implemented.
- SHA-2 signatures are now supported in X.509 certificates.
- Automatic test vector-based self-tests of all hash functions (MD5, SHA-1, SHA-2) during pluto startup was introduced to increase the reliability of the software.
<<lessIn order to have a stable IPsec platform to base our future extensions of the X.509 capability on, we decided to lauch the strongSwan project.
Main features:
- runs both on Linux 2.4 (KLIPS) and Linux 2.6 (native IPsec) kernels
- strong 3DES, AES, Serpent, Twofish, or Blowfish encryption
- Authentication based on X.509 certificates or preshared keys
- Powerful IPsec policies based on wildcards or intermediate CAs
- Retrieval and local caching of Certificate Revocation Lists via HTTP or LDAP
- Full support of the Online Certificate Status Protocol (OCSP, RCF 2560).
- Optional storage of RSA private keys on smartcards or USB crypto tokens
- Smartcard access via standardized PKCS #11 interface
- PKCS #11 proxy function offering RSA decryption services via whack
- NAT-Traversal (RFC 3947) and support of Virtual IPs and IKE Mode Config
- CA management (OCSP and CRL URIs, default LDAP server)
- Dead Peer Detection (DPD, RFC 3706)
- Group policies based on X.509 attribute certificates ( RFC 3281)
- Generation of default self-signed certificates during strongSwan setup
Whats New in 2.8.0 Stable Release:
- The implementation of the IKE Mode Config push mode allows interoperability with Cisco VPN gateways.
- By setting "modeconfig=push", strongSwan will wait for the peer to push down a virtual IP address that can be used within an IPsec tunnel.
- The default value of the new keyword is "modeconfig=pull".
- The command "ipsec statusall" now shows "DPD active" for all ISAKMP Security Associations that are under active Dead Peer Detection control.
Whats New in 4.0.7 Development Release:
- Extended authentication (XAUTH) in conjunction with IKE Main Mode authentication (RSA and PSK) is now possible with most VPN clients and gateways (e.g. Cisco, NCP, Shrew, etc.).
Whats New in 2.8.3 Stable Release:
- A bug in the computation of the SHA-512-HMAC function was fixed.
- The SHA-384 hash and HMAC functions were implemented.
- SHA-2 signatures are now supported in X.509 certificates.
- Automatic test vector-based self-tests of all hash functions (MD5, SHA-1, SHA-2) during pluto startup was introduced to increase the reliability of the software.
Download (2.3MB)
Added: 2007-02-23 License: GPL (GNU General Public License) Price:
973 downloads
coords 0.5.2
coords is a planetarium program. more>>
coords is a planetarium program. The project is still under construction, but it does a good job of showing the sky with stars and planets at the correct positions.
This version shows celestial objects from the Yale BSC and NGC2000 catalogs, planets from Mercury to Pluto, the Sun and the Moon.
All GUI parts have been written with GLib 2.12, GTK 2.8, Pango 1.14, and Cairo 1.4 (Debian Lenny libraries).
How to use it:
The GUI program:
- If you click in the sky map, you can move it with the arrow keys. Its a stereographic projection of the sky sphere, the up and down keys change the pitch and the left and right keys allow you to roll around the zenith. There are spin buttons too. Finally, the sky can also be moved by dragging the mouse on it.
- A spin button adjusts the zoom factor (Scale).
- A menu allows you to toggle the visibility of various things (equator, frames or grids, star names, ...)
- other stuff, i hope its intuitive
coordserver takes no argument. Currently, it can serve data in two modes. The first is a Right Ascent,Declination pair, given as two floating point numbers separated by a comma (option -c of coordclient). This is meant for machine
processing. The second mode is text.
coordclient can take up to 3 arguments. The first is the -c option (see above).
The next argument is the star name, which can be :
- a name
- an HR (Harvard Revised Catalog) number with 0 padding before the number if less than 4 digits
- a Bayer name (Alp Boo, Alp 1 Cen, Gam Per...)
- a Flamsteed name ( 1 Peg, with two blank spaces before the "1" because the number field is 3 characters long).
The next argument can be date in YYYY-MM-DD.DDDD format. If absent, the machine current date will be used.
<<lessThis version shows celestial objects from the Yale BSC and NGC2000 catalogs, planets from Mercury to Pluto, the Sun and the Moon.
All GUI parts have been written with GLib 2.12, GTK 2.8, Pango 1.14, and Cairo 1.4 (Debian Lenny libraries).
How to use it:
The GUI program:
- If you click in the sky map, you can move it with the arrow keys. Its a stereographic projection of the sky sphere, the up and down keys change the pitch and the left and right keys allow you to roll around the zenith. There are spin buttons too. Finally, the sky can also be moved by dragging the mouse on it.
- A spin button adjusts the zoom factor (Scale).
- A menu allows you to toggle the visibility of various things (equator, frames or grids, star names, ...)
- other stuff, i hope its intuitive
coordserver takes no argument. Currently, it can serve data in two modes. The first is a Right Ascent,Declination pair, given as two floating point numbers separated by a comma (option -c of coordclient). This is meant for machine
processing. The second mode is text.
coordclient can take up to 3 arguments. The first is the -c option (see above).
The next argument is the star name, which can be :
- a name
- an HR (Harvard Revised Catalog) number with 0 padding before the number if less than 4 digits
- a Bayer name (Alp Boo, Alp 1 Cen, Gam Per...)
- a Flamsteed name ( 1 Peg, with two blank spaces before the "1" because the number field is 3 characters long).
The next argument can be date in YYYY-MM-DD.DDDD format. If absent, the machine current date will be used.
Download (2.9MB)
Added: 2007-08-12 License: GPL (GNU General Public License) Price:
807 downloads
FreeS/WAN 2.06
FreeS/WAN is an implementation of IPSEC & IKE for Linux. more>>
FreeS/WAN is an implementation of IPSEC & IKE for Linux. IPSEC is Internet Protocol SECurity. It uses strong cryptography to provide both authentication and encryption services. Authentication ensures that packets are from the right sender and have not been altered in transit. Encryption prevents unauthorised reading of packet contents. These services allow you to build secure tunnels through untrusted networks.
Two protocols are used
ESP (Encapsulating Security Payload) provides encryption plus authentication
IKE (Internet Key Exchange) negotiates connection parameters, including keys, for ESP
Freeswan implementation has three main parts:
KLIPS (kernel IPsec) implements ESP, and packet handling within the kernel
Pluto (an IKE daemon) implements IKE, negotiating connections with other systems
various scripts provide an adminstrators interface to the machinery.
Because IPsec operates at the network layer, it is remarkably flexible and can be used to secure nearly any type of Internet traffic. Two applications, however, are extremely widespread:
a Virtual Private Network, or VPN, allows multiple sites to communicate securely over an insecure Internet by encrypting all communication between the sites.
"Road Warriors" connect to the office from home, or perhaps from a hotel somewhere
There is enough opportunity in these applications that vendors are flocking to them. IPsec is being built into routers, into firewall products, and into major operating systems, primarily to support these applications. See our list of implementations for details.
We support both of those applications, and various less common IPsec applications as well, but we also add one of our own:
opportunistic encryption, the ability to set up FreeS/WAN gateways so that any two of them can encrypt to each other, and will do so whenever packets pass between them.
This is an extension we are adding to the protocols. FreeS/WAN is the first prototype implementation, though we hope other IPsec implementations will adopt the technique once we demonstrate it. See project goals below for why we think this is important.
A somewhat more detailed description of each of these applications is below. Our quickstart section will show you how to build each of them.
<<lessTwo protocols are used
ESP (Encapsulating Security Payload) provides encryption plus authentication
IKE (Internet Key Exchange) negotiates connection parameters, including keys, for ESP
Freeswan implementation has three main parts:
KLIPS (kernel IPsec) implements ESP, and packet handling within the kernel
Pluto (an IKE daemon) implements IKE, negotiating connections with other systems
various scripts provide an adminstrators interface to the machinery.
Because IPsec operates at the network layer, it is remarkably flexible and can be used to secure nearly any type of Internet traffic. Two applications, however, are extremely widespread:
a Virtual Private Network, or VPN, allows multiple sites to communicate securely over an insecure Internet by encrypting all communication between the sites.
"Road Warriors" connect to the office from home, or perhaps from a hotel somewhere
There is enough opportunity in these applications that vendors are flocking to them. IPsec is being built into routers, into firewall products, and into major operating systems, primarily to support these applications. See our list of implementations for details.
We support both of those applications, and various less common IPsec applications as well, but we also add one of our own:
opportunistic encryption, the ability to set up FreeS/WAN gateways so that any two of them can encrypt to each other, and will do so whenever packets pass between them.
This is an extension we are adding to the protocols. FreeS/WAN is the first prototype implementation, though we hope other IPsec implementations will adopt the technique once we demonstrate it. See project goals below for why we think this is important.
A somewhat more detailed description of each of these applications is below. Our quickstart section will show you how to build each of them.
Download (1.5MB)
Added: 2006-07-11 License: GPL (GNU General Public License) Price:
1210 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above pluto search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
