strong js 1.00
Sponsored Links
Sponsored Links
strong js 1.00
No.
Title
Category
Price
License
Expand All
WiKID is a two-factor authentication system. WiKID Strong Authentication System project consists of: a PIN, stored in the users head; a small, lightweight client that encapsulates the private/public keys; and a server that stores the public keys of the clients and the users PIN.
When the user wants to login to a service, they start the client and enter their PIN, which is encrypted and sent to the server. If the PIN is correct, the account active and the encryption valid, the user is sent a one-time passcode to use instead of a static password.
You can think of WiKID as certificates on steroids. It is more secure than certificates because the required PIN is only stored on the server, so it is not susceptible to offline passive attacks.
It is easier because user enrollment is automated and you dont have to deal with a full certiticate infrastructure. You can also compare WiKID to hardware tokens: it is much easier to implement, more extensible, yet just as secure. Stealing either the token or the PIN does you no good. You must steal both, just like a hardware token.
The WiKID Strong Authentication System consists of three parts: the WiKID server, the WiKID token client and a network client (such as a VPN, website or other service requesting authentication). The WiKID server is written in Java, as is the open source J2SE PC client. As part of this release, we are also releasing the following under the GPL:
- ASP code for end-user self validation. New users can provision their own WiKID token clients based on trusted LAN credentials, in this case, Active Directory credentials. This code can easily be modified for other types of credentials.
- The WiKID Citrix Web Interface plug-in. If you’re using Citrix Web Interface for remote access, now you can add two-factor authentication quickly and easily.
- The wAuth COM object and Java component. Network clients talk to the WiKID server using an SSL encrypted protocol - wAuth. These objects can be used to integrate WiKID into any application. The file example.jsp shows how easily this is done for Java-based web applications. The Citrix Web Interface and the ASP code for end-user validation show how simple this is for ASP applications.
- The J2SE WiKID token client. The token client is responsible for key generation, domain management and one-time password requests. It can run on your PC, a suitable PDA or on a device such as a USB token.
When the user wants to log in, they select the domain they want to log into (yes, WiKID is capable of handling multiple domains with a single client unlike hardware tokens) and enter their PIN. The PIN and a single-use AES symmetric key is encrypted by the client’s private key.
The server decrypts the OTP request. If the PIN is correct and the account active, the server generates the OTP and encrypts it with the token client’s public key and the single-use AES key. The user gets the OTP and uses it to log in. Whatever service the user is trying to log into passes the OTP and username back to the WiKID server for validation via a network client connection.
If you manage multiple accounts and boxes across multiple entities, WiKID can help you reduce your password overload. One WiKID token can work with multiple WiKID servers, so, if you want to get rid of your static passwords, deploy WiKID in as many places as you can.
WiKID is great for:
· Strong authentication for remote access via a VPN
· Strong Authentication for remote access via Citrix
· Two-factor Authentication for extranet applications
· Locking down internet-exposed intranets
· Secure Online Banking - fight phishing and other attacks
· Lock down SSH and other admin access
· Any place you might have used certificates or token, but couldnt because of cost, hassle, etc.
Here are some key features of "WiKID Strong Authentication System":
· Easy to use Web Interface
· Automated initial validation of users
· Fault tolerance via replication
· Highly scalable - each transaction is 300 bits +/-
· Simple user disablement
· Support for a number of network protocols
· No need for time synchronization - Request-response architecture
· Each client can support multiple relationships across multiple servers
· Extensible across enterprises
When the user wants to login to a service, they start the client and enter their PIN, which is encrypted and sent to the server. If the PIN is correct, the account active and the encryption valid, the user is sent a one-time passcode to use instead of a static password.
You can think of WiKID as certificates on steroids. It is more secure than certificates because the required PIN is only stored on the server, so it is not susceptible to offline passive attacks.
It is easier because user enrollment is automated and you dont have to deal with a full certiticate infrastructure. You can also compare WiKID to hardware tokens: it is much easier to implement, more extensible, yet just as secure. Stealing either the token or the PIN does you no good. You must steal both, just like a hardware token.
The WiKID Strong Authentication System consists of three parts: the WiKID server, the WiKID token client and a network client (such as a VPN, website or other service requesting authentication). The WiKID server is written in Java, as is the open source J2SE PC client. As part of this release, we are also releasing the following under the GPL:
- ASP code for end-user self validation. New users can provision their own WiKID token clients based on trusted LAN credentials, in this case, Active Directory credentials. This code can easily be modified for other types of credentials.
- The WiKID Citrix Web Interface plug-in. If you’re using Citrix Web Interface for remote access, now you can add two-factor authentication quickly and easily.
- The wAuth COM object and Java component. Network clients talk to the WiKID server using an SSL encrypted protocol - wAuth. These objects can be used to integrate WiKID into any application. The file example.jsp shows how easily this is done for Java-based web applications. The Citrix Web Interface and the ASP code for end-user validation show how simple this is for ASP applications.
- The J2SE WiKID token client. The token client is responsible for key generation, domain management and one-time password requests. It can run on your PC, a suitable PDA or on a device such as a USB token.
When the user wants to log in, they select the domain they want to log into (yes, WiKID is capable of handling multiple domains with a single client unlike hardware tokens) and enter their PIN. The PIN and a single-use AES symmetric key is encrypted by the client’s private key.
The server decrypts the OTP request. If the PIN is correct and the account active, the server generates the OTP and encrypts it with the token client’s public key and the single-use AES key. The user gets the OTP and uses it to log in. Whatever service the user is trying to log into passes the OTP and username back to the WiKID server for validation via a network client connection.
If you manage multiple accounts and boxes across multiple entities, WiKID can help you reduce your password overload. One WiKID token can work with multiple WiKID servers, so, if you want to get rid of your static passwords, deploy WiKID in as many places as you can.
WiKID is great for:
· Strong authentication for remote access via a VPN
· Strong Authentication for remote access via Citrix
· Two-factor Authentication for extranet applications
· Locking down internet-exposed intranets
· Secure Online Banking - fight phishing and other attacks
· Lock down SSH and other admin access
· Any place you might have used certificates or token, but couldnt because of cost, hassle, etc.
Here are some key features of "WiKID Strong Authentication System":
· Easy to use Web Interface
· Automated initial validation of users
· Fault tolerance via replication
· Highly scalable - each transaction is 300 bits +/-
· Simple user disablement
· Support for a number of network protocols
· No need for time synchronization - Request-response architecture
· Each client can support multiple relationships across multiple servers
· Extensible across enterprises
js-search is a javascript indexing and searching.
A client-side library for building a simple inverted index, and searching it.
You can download the source code from SVN with the following command:
svn checkout http://js-search.googlecode.com/svn/trunk/ js-search
A client-side library for building a simple inverted index, and searching it.
You can download the source code from SVN with the following command:
svn checkout http://js-search.googlecode.com/svn/trunk/ js-search
3
Miscellaneous -> Security
OtherProprietary License
Hide show
WiKID Strong Authentication System is a highly scalable, secure two-factor authentication system.
WiKID Systems, Inc., has developed a commercial open source two-factor authentication solution that increases security, reduces costs and is very convenient to end-users and administrators.
Our unique architecture combines strong asymmetric encryption with Blackberries, cell phones, Palms, PocketPCs, Windows, Linux and Apple PCs to create an one-time password system that is as strong as hardware tokens - with all the flexibility and benefits of a software tokens.
WiKIDs unique automatic initial validation system, ease of implementation, host/mutual authentication, and transaction authentication capabilities make WiKID perfect for both VPN authentication and online banking.
Whats New in This Release:
· Includes support for Firefox 2.0.x.
WiKID Systems, Inc., has developed a commercial open source two-factor authentication solution that increases security, reduces costs and is very convenient to end-users and administrators.
Our unique architecture combines strong asymmetric encryption with Blackberries, cell phones, Palms, PocketPCs, Windows, Linux and Apple PCs to create an one-time password system that is as strong as hardware tokens - with all the flexibility and benefits of a software tokens.
WiKIDs unique automatic initial validation system, ease of implementation, host/mutual authentication, and transaction authentication capabilities make WiKID perfect for both VPN authentication and online banking.
Whats New in This Release:
· Includes support for Firefox 2.0.x.
OSSP js is a stand-alone distribution of the JavaScript (JS) programming language reference implementation from Mozilla -- aka "JSRef" or "SpiderMonkey".
OSSP js provides a smart, stand-alone and portable distribution of Mozilla JavaScript through a build environment based on GNU autoconf, GNU libtool and GNU shtool, including support for easy JavaScript build-time feature set selection (ECMA-3, JS-1.5, JS-1.6), optional CLI line editing support, optional "stdio" based File object support and JS/Perl bindings.
Additionally, the C API in "libjs" contains both the JavaScript engine and the required Sun math library ("fdlibm") and with all internal symbols carefully protected under the "js" namespace. Finally, a js-config(1) utility and a pkg-config(1) specification is provided to allow applications to easily build with the JavaScript C API.
OSSP js was created because for OSSP and similar pedantic C coding projects a smart, stand-alone, portable, clean, powerful and robust scripting language engine is required. JavaScript is a great programming language and Mozilla JavaScript "SpiderMonkey" definitely is an acceptable clean, powerful and robust implementation.
Unfortunately there is just a stand-alone distribution released from time to time by Mozilla and it is far away from really being smart, stand-alone and portable. At least for OSSP it was not acceptable having to tell the community that for small and stand-alone C components like the OSSP components they either have to install the great but large Mozilla Firefox application (where Mozilla JavaScript is included) or have to fiddle around theirself with an older stand-alone JavaScript distribution and its weak build environment.
OSSP js combines the best from two worlds: the 1:1 repackaged JavaScript code base from Mozilla and the usual amount of GNU autoconf, GNU libtool and GNU shtool wrappers as always used by OSSP. Additionally, stand-alone ("stdio" instead of NSPR based) File object support was required.
Whats New in This Release:
· The build environment was upgraded to GNU autoconf 2.61 and a jspack(1) command that is a CLI adaption of Dean Edwards JavaScript "packer" was added.
OSSP js provides a smart, stand-alone and portable distribution of Mozilla JavaScript through a build environment based on GNU autoconf, GNU libtool and GNU shtool, including support for easy JavaScript build-time feature set selection (ECMA-3, JS-1.5, JS-1.6), optional CLI line editing support, optional "stdio" based File object support and JS/Perl bindings.
Additionally, the C API in "libjs" contains both the JavaScript engine and the required Sun math library ("fdlibm") and with all internal symbols carefully protected under the "js" namespace. Finally, a js-config(1) utility and a pkg-config(1) specification is provided to allow applications to easily build with the JavaScript C API.
OSSP js was created because for OSSP and similar pedantic C coding projects a smart, stand-alone, portable, clean, powerful and robust scripting language engine is required. JavaScript is a great programming language and Mozilla JavaScript "SpiderMonkey" definitely is an acceptable clean, powerful and robust implementation.
Unfortunately there is just a stand-alone distribution released from time to time by Mozilla and it is far away from really being smart, stand-alone and portable. At least for OSSP it was not acceptable having to tell the community that for small and stand-alone C components like the OSSP components they either have to install the great but large Mozilla Firefox application (where Mozilla JavaScript is included) or have to fiddle around theirself with an older stand-alone JavaScript distribution and its weak build environment.
OSSP js combines the best from two worlds: the 1:1 repackaged JavaScript code base from Mozilla and the usual amount of GNU autoconf, GNU libtool and GNU shtool wrappers as always used by OSSP. Additionally, stand-alone ("stdio" instead of NSPR based) File object support was required.
Whats New in This Release:
· The build environment was upgraded to GNU autoconf 2.61 and a jspack(1) command that is a CLI adaption of Dean Edwards JavaScript "packer" was added.
php-js application is an experimental PHP extension which embeds the Mozilla SpiderMonkey JavaScript engine into PHP.
Installation and Usage:
A simple ./configure; make; make install should do the trick. Make sure to add an extension=js.so line to your php.ini/php.d. Note: you need to install libjs first. If youre using a Redhat-esque system, you can use the SRPM provided above, else, use the TBZ.
Then, just use js_eval to evaluate your JavaScript. js_eval returns the value returned by the JavaScript interpreter to PHP.
For example:
js_eval("var a = 123;");
js_eval("var b = 456;");
$c = js_eval("[a, b];");
echo "a is ".$c[0]."n";
echo "b is ".$c[1]."n";
js_eval("var sum = function(x, y) { return x + y; }");
$d = js_eval("sum(a, b);");
echo "The sum of a and b is ".$d."n";
Would produce:
a is 123
b is 456
The sum of a and b is 579
js_eval takes an optional boolean argument, assoc, which returns objects as associative arrays instead of PHP objects.
The php-js execution environment provides two built-in JavaScript system functions:
print
gc
print outputs its argument to the php output stream.
gc forces garbage collection within the JavaScript environment.
Whats New in This Release:
· A session shutdown issue has been fixed.
· There is better handling of null objects.
Installation and Usage:
A simple ./configure; make; make install should do the trick. Make sure to add an extension=js.so line to your php.ini/php.d. Note: you need to install libjs first. If youre using a Redhat-esque system, you can use the SRPM provided above, else, use the TBZ.
Then, just use js_eval to evaluate your JavaScript. js_eval returns the value returned by the JavaScript interpreter to PHP.
For example:
js_eval("var a = 123;");
js_eval("var b = 456;");
$c = js_eval("[a, b];");
echo "a is ".$c[0]."n";
echo "b is ".$c[1]."n";
js_eval("var sum = function(x, y) { return x + y; }");
$d = js_eval("sum(a, b);");
echo "The sum of a and b is ".$d."n";
Would produce:
a is 123
b is 456
The sum of a and b is 579
js_eval takes an optional boolean argument, assoc, which returns objects as associative arrays instead of PHP objects.
The php-js execution environment provides two built-in JavaScript system functions:
gc
print outputs its argument to the php output stream.
gc forces garbage collection within the JavaScript environment.
Whats New in This Release:
· A session shutdown issue has been fixed.
· There is better handling of null objects.
6
System -> Networking
GPL GNU General Public License
Hide show
WiKID is a two-factor authentication system. WiKID Strong Authentication System project consists of: a PIN, stored in the users head; a small, lightweight client that encapsulates the private/public keys; and a server that stores the public keys of the clients and the users PIN.
When the user wants to login to a service, they start the client and enter their PIN, which is encrypted and sent to the server. If the PIN is correct, the account active and the encryption valid, the user is sent a one-time passcode to use instead of a static password.
You can think of WiKID as certificates on steroids. It is more secure than certificates because the required PIN is only stored on the server, so it is not susceptible to offline passive attacks.
It is easier because user enrollment is automated and you dont have to deal with a full certiticate infrastructure. You can also compare WiKID to hardware tokens: it is much easier to implement, more extensible, yet just as secure. Stealing either the token or the PIN does you no good. You must steal both, just like a hardware token.
The WiKID Strong Authentication System consists of three parts: the WiKID server, the WiKID token client and a network client (such as a VPN, website or other service requesting authentication). The WiKID server is written in Java, as is the open source J2SE PC client. As part of this release, we are also releasing the following under the GPL:
- ASP code for end-user self validation. New users can provision their own WiKID token clients based on trusted LAN credentials, in this case, Active Directory credentials. This code can easily be modified for other types of credentials.
- The WiKID Citrix Web Interface plug-in. If you’re using Citrix Web Interface for remote access, now you can add two-factor authentication quickly and easily.
- The wAuth COM object and Java component. Network clients talk to the WiKID server using an SSL encrypted protocol - wAuth. These objects can be used to integrate WiKID into any application. The file example.jsp shows how easily this is done for Java-based web applications. The Citrix Web Interface and the ASP code for end-user validation show how simple this is for ASP applications.
- The J2SE WiKID token client. The token client is responsible for key generation, domain management and one-time password requests. It can run on your PC, a suitable PDA or on a device such as a USB token.
When the user wants to log in, they select the domain they want to log into (yes, WiKID is capable of handling multiple domains with a single client unlike hardware tokens) and enter their PIN. The PIN and a single-use AES symmetric key is encrypted by the client’s private key.
The server decrypts the OTP request. If the PIN is correct and the account active, the server generates the OTP and encrypts it with the token client’s public key and the single-use AES key. The user gets the OTP and uses it to log in. Whatever service the user is trying to log into passes the OTP and username back to the WiKID server for validation via a network client connection.
If you manage multiple accounts and boxes across multiple entities, WiKID can help you reduce your password overload. One WiKID token can work with multiple WiKID servers, so, if you want to get rid of your static passwords, deploy WiKID in as many places as you can.
WiKID is great for:
· Strong authentication for remote access via a VPN
· Strong Authentication for remote access via Citrix
· Two-factor Authentication for extranet applications
· Locking down internet-exposed intranets
· Secure Online Banking - fight phishing and other attacks
· Lock down SSH and other admin access
· Any place you might have used certificates or token, but couldnt because of cost, hassle, etc.
Here are some key features of "WiKID Strong Authentication System":
· Easy to use Web Interface
· Automated initial validation of users
· Fault tolerance via replication
· Highly scalable - each transaction is 300 bits +/-
· Simple user disablement
· Support for a number of network protocols
· No need for time synchronization - Request-response architecture
· Each client can support multiple relationships across multiple servers
· Extensible across enterprises
Whats New in This Release:
· Minor bugfixes. The VMWare image has caught up to the ISO version.
When the user wants to login to a service, they start the client and enter their PIN, which is encrypted and sent to the server. If the PIN is correct, the account active and the encryption valid, the user is sent a one-time passcode to use instead of a static password.
You can think of WiKID as certificates on steroids. It is more secure than certificates because the required PIN is only stored on the server, so it is not susceptible to offline passive attacks.
It is easier because user enrollment is automated and you dont have to deal with a full certiticate infrastructure. You can also compare WiKID to hardware tokens: it is much easier to implement, more extensible, yet just as secure. Stealing either the token or the PIN does you no good. You must steal both, just like a hardware token.
The WiKID Strong Authentication System consists of three parts: the WiKID server, the WiKID token client and a network client (such as a VPN, website or other service requesting authentication). The WiKID server is written in Java, as is the open source J2SE PC client. As part of this release, we are also releasing the following under the GPL:
- ASP code for end-user self validation. New users can provision their own WiKID token clients based on trusted LAN credentials, in this case, Active Directory credentials. This code can easily be modified for other types of credentials.
- The WiKID Citrix Web Interface plug-in. If you’re using Citrix Web Interface for remote access, now you can add two-factor authentication quickly and easily.
- The wAuth COM object and Java component. Network clients talk to the WiKID server using an SSL encrypted protocol - wAuth. These objects can be used to integrate WiKID into any application. The file example.jsp shows how easily this is done for Java-based web applications. The Citrix Web Interface and the ASP code for end-user validation show how simple this is for ASP applications.
- The J2SE WiKID token client. The token client is responsible for key generation, domain management and one-time password requests. It can run on your PC, a suitable PDA or on a device such as a USB token.
When the user wants to log in, they select the domain they want to log into (yes, WiKID is capable of handling multiple domains with a single client unlike hardware tokens) and enter their PIN. The PIN and a single-use AES symmetric key is encrypted by the client’s private key.
The server decrypts the OTP request. If the PIN is correct and the account active, the server generates the OTP and encrypts it with the token client’s public key and the single-use AES key. The user gets the OTP and uses it to log in. Whatever service the user is trying to log into passes the OTP and username back to the WiKID server for validation via a network client connection.
If you manage multiple accounts and boxes across multiple entities, WiKID can help you reduce your password overload. One WiKID token can work with multiple WiKID servers, so, if you want to get rid of your static passwords, deploy WiKID in as many places as you can.
WiKID is great for:
· Strong authentication for remote access via a VPN
· Strong Authentication for remote access via Citrix
· Two-factor Authentication for extranet applications
· Locking down internet-exposed intranets
· Secure Online Banking - fight phishing and other attacks
· Lock down SSH and other admin access
· Any place you might have used certificates or token, but couldnt because of cost, hassle, etc.
Here are some key features of "WiKID Strong Authentication System":
· Easy to use Web Interface
· Automated initial validation of users
· Fault tolerance via replication
· Highly scalable - each transaction is 300 bits +/-
· Simple user disablement
· Support for a number of network protocols
· No need for time synchronization - Request-response architecture
· Each client can support multiple relationships across multiple servers
· Extensible across enterprises
Whats New in This Release:
· Minor bugfixes. The VMWare image has caught up to the ISO version.
KCAD (Kontrol-Alt-Delete) is a somewhat sarcastic screensaver for KDE. It is intended for those of you who are stuck with BOFH-type bosses who insist on running Windows NT.
This screensaver should assist you in appeasing their Microsoft-enhanced sensibilities. By default, KCAD looks just very KDE-ish, but with a little bit of configuration-editing, it will fool 99% of the Bosses out there.
Installation
· tar xzfv kcad-1.00.tgz
· cd kcad-1.00
· ./configure (on FreeBSD: --prefix=/usr/local --with-qt-includes=/usr/X11R6/include/qt2)
· make (on FreeBSD: gmake)
· (become root)
· [g]make install
Using
In order to make KCAD look like it does in the second screenshot above, you must create a configuration file for KCAD. Put the following text in the file $HOME/.kde/share/config/kcad.kss:
[Settings]
NtLike=1
Voila! Thats all there is to it! Consider your boss fooled!
This screensaver should assist you in appeasing their Microsoft-enhanced sensibilities. By default, KCAD looks just very KDE-ish, but with a little bit of configuration-editing, it will fool 99% of the Bosses out there.
Installation
· tar xzfv kcad-1.00.tgz
· cd kcad-1.00
· ./configure (on FreeBSD: --prefix=/usr/local --with-qt-includes=/usr/X11R6/include/qt2)
· make (on FreeBSD: gmake)
· (become root)
· [g]make install
Using
In order to make KCAD look like it does in the second screenshot above, you must create a configuration file for KCAD. Put the following text in the file $HOME/.kde/share/config/kcad.kss:
[Settings]
NtLike=1
Voila! Thats all there is to it! Consider your boss fooled!
GNU Phantom.Security is a computer-controlled security system.
Phantom is designed to be a completely customizable computer controlled security system. All source code (C++/Bourne script) is included. Phantom was designed & tested on a Linux system, but I assume the C++ portions can be easily ported to other Unix systems (even DOS/Windows, maybe?). The Phantom Security system is for use with intrusion/fire detection equipment such as motion sensors, door magnets, and smoke detectors. However, any Normally Open or Normally Closed device may work with little or no change to the code. All source code and diagrams included are free to use,for distributing, and to modify!
Phantom.Controller is to be used in a system with non-powered security devices, i.e. door magnets. Phantom.Controller2 is for systems with powered security devices, i.e. motion sensors & smoke detectors. Anyone with a basic knowledge of circuit design can mix and match from these two diagrams to mix powered & non-powered devices!
Whats New in This Release:
· To compile & install Phantom.Security 1.00:
· configure
· make
· make install
· The default installation directory is /home/Phantom/security. However, this can be modified in the top-level Makefile.am (if this is changed, you need to re-run aclocal, autoconf, & automake). However, both the bindir and datadir should point to the SAME directory, or else Phantom.Security wont function correctly, because it wont be able
· to find the Phantom.conf file.
Whats New in This Release:
· Version 1.0!!! GNU Phantom.Security is out of Beta! I have been running Phantom.Security for months straight on my machine at work and believe it is stable enough to promote it out
· of Beta!
· Created HTML & PostScript versions of documentation. Available on-line.
Phantom is designed to be a completely customizable computer controlled security system. All source code (C++/Bourne script) is included. Phantom was designed & tested on a Linux system, but I assume the C++ portions can be easily ported to other Unix systems (even DOS/Windows, maybe?). The Phantom Security system is for use with intrusion/fire detection equipment such as motion sensors, door magnets, and smoke detectors. However, any Normally Open or Normally Closed device may work with little or no change to the code. All source code and diagrams included are free to use,for distributing, and to modify!
Phantom.Controller is to be used in a system with non-powered security devices, i.e. door magnets. Phantom.Controller2 is for systems with powered security devices, i.e. motion sensors & smoke detectors. Anyone with a basic knowledge of circuit design can mix and match from these two diagrams to mix powered & non-powered devices!
Whats New in This Release:
· To compile & install Phantom.Security 1.00:
· configure
· make
· make install
· The default installation directory is /home/Phantom/security. However, this can be modified in the top-level Makefile.am (if this is changed, you need to re-run aclocal, autoconf, & automake). However, both the bindir and datadir should point to the SAME directory, or else Phantom.Security wont function correctly, because it wont be able
· to find the Phantom.conf file.
Whats New in This Release:
· Version 1.0!!! GNU Phantom.Security is out of Beta! I have been running Phantom.Security for months straight on my machine at work and believe it is stable enough to promote it out
· of Beta!
· Created HTML & PostScript versions of documentation. Available on-line.
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above strong js 1.00 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
Featured Software
Want to place your software product here?
Please contact us for consideration.
Contact WareSeeker.com
Sponsored Links
Related Information
Top Popular Software
Editor's Picks Software
