acknowledgement
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 15
TCP Knocking 0.1
TCP Knocking provides a port knocking implementation. more>>
TCP Knocking provides a port knocking implementation.
Often a secure system needs a port open so that only authorized persons can access a particular service and also the service should not exposed to attackers and worms that may use vulnerabilities that exist in the listening server. Port knocking is designed to be used as a complementary service to the existing authentication mechanism. But one of the biggest problems with port knocking is manipulating the firewall with timeouts.
When the correct knock sequence is sent, the firewall is modified for couple of seconds. Having the firewall open automatically for a time period will make any system administrator uncomfortable. TCP knocking attempts to solve the problem by incorporating the knock into the TCP handshake. Tcp knocking is similar to port knocking, but instead sending UDP packets with secret ports, the TCP handshake packets must include secrete codes. It is at least as secure as port knocking and it can be made secure with more hardening.
Modified TCP handshake:
In normal TCP handshake, the client sends the syn packet and chooses a random initial sequence number. The server responds with a packet that has both syn and ack flags set, choosing a random
The modified TCP handshake uses the empty fields in the header. The server does not respond to connection requests without a special code generated along with the syn packet. The server also encrypts the ISN in the ack packet (2) and the final packet of the three-way handshake must have the correct acknowledgment for the servers ISN. The system is further protected from brute-force attacks by closing the connection if the first attempt for the third packet does not have the expected acknowledgment sequence.
Also, rather than use conventional encryption techniques like HMAC for verification, this system uses a file with random numbers as the key. This is because of the limited unused space available in the TCP/IP header which makes HMAC very weak. By using a shared file, the length of the key can be much greater than traditional systems and even though some parts of the key can be revealed by attacks, the server can protect itself from replay attacks.
The handshake:
1) Syn
The syn packet does not use the 32 bit acknowledgment field in the TCP header as it the the first packet to initiate the connection. Further the 16 bit IPID can be used to transmit information. In the current implementation only the 32 bit acknowledgment field is used. Currently the 32 bit ack is derived from a 64 KB file which contains random numbers. The ISN and the source IP address along with the random numbers are used to generate this value.
2) Syn/Ack
The ISN is encrypted using the random numbers from the 64 KB file using the destination IP address as well as a 16 bit random number used as IPID. I do not have code for this part yet.
3) Ack
The client decrypts the syn number from the encrypted syn, the key file, the 16 bit IPID and its own IP address and sends the ack packet. The server closes all connections from the client for couple of minutes if it sends a wrong ack value. Part of the security relies on the fact that the ISN generated by Linux 2.6 is fairly random.
Implementation:
I have implemented only the first part, which is the server expecting secret code along with the first syn packet from the client. Hence it is very possible to brute-force the server. Also the system is designed with the second phase in mind, which is the encrypted Initial Sequence Number in the ack packet and closing the connection if the correct ack is not sent on the first try. I do not have an implementation for that yet. The security will be increased greatly when the second phase is incorporated. Also the ability to detect brute-force attacks can be added to this system.
But the current system can be used for protecting the server from worms and random scanning. The use-case is similar to port knocking but it does not use the ugly system of opening the firewall for a couple of seconds. Vanilla port knocking is susceptible to brute-force attacks as well. Besides, inserting a kernel module to just ssh into your server will increase your mad sysadmin points.
Enhancements:
- TCP knocking with Phase 1 of the protocol was implemented.
<<lessOften a secure system needs a port open so that only authorized persons can access a particular service and also the service should not exposed to attackers and worms that may use vulnerabilities that exist in the listening server. Port knocking is designed to be used as a complementary service to the existing authentication mechanism. But one of the biggest problems with port knocking is manipulating the firewall with timeouts.
When the correct knock sequence is sent, the firewall is modified for couple of seconds. Having the firewall open automatically for a time period will make any system administrator uncomfortable. TCP knocking attempts to solve the problem by incorporating the knock into the TCP handshake. Tcp knocking is similar to port knocking, but instead sending UDP packets with secret ports, the TCP handshake packets must include secrete codes. It is at least as secure as port knocking and it can be made secure with more hardening.
Modified TCP handshake:
In normal TCP handshake, the client sends the syn packet and chooses a random initial sequence number. The server responds with a packet that has both syn and ack flags set, choosing a random
The modified TCP handshake uses the empty fields in the header. The server does not respond to connection requests without a special code generated along with the syn packet. The server also encrypts the ISN in the ack packet (2) and the final packet of the three-way handshake must have the correct acknowledgment for the servers ISN. The system is further protected from brute-force attacks by closing the connection if the first attempt for the third packet does not have the expected acknowledgment sequence.
Also, rather than use conventional encryption techniques like HMAC for verification, this system uses a file with random numbers as the key. This is because of the limited unused space available in the TCP/IP header which makes HMAC very weak. By using a shared file, the length of the key can be much greater than traditional systems and even though some parts of the key can be revealed by attacks, the server can protect itself from replay attacks.
The handshake:
1) Syn
The syn packet does not use the 32 bit acknowledgment field in the TCP header as it the the first packet to initiate the connection. Further the 16 bit IPID can be used to transmit information. In the current implementation only the 32 bit acknowledgment field is used. Currently the 32 bit ack is derived from a 64 KB file which contains random numbers. The ISN and the source IP address along with the random numbers are used to generate this value.
2) Syn/Ack
The ISN is encrypted using the random numbers from the 64 KB file using the destination IP address as well as a 16 bit random number used as IPID. I do not have code for this part yet.
3) Ack
The client decrypts the syn number from the encrypted syn, the key file, the 16 bit IPID and its own IP address and sends the ack packet. The server closes all connections from the client for couple of minutes if it sends a wrong ack value. Part of the security relies on the fact that the ISN generated by Linux 2.6 is fairly random.
Implementation:
I have implemented only the first part, which is the server expecting secret code along with the first syn packet from the client. Hence it is very possible to brute-force the server. Also the system is designed with the second phase in mind, which is the encrypted Initial Sequence Number in the ack packet and closing the connection if the correct ack is not sent on the first try. I do not have an implementation for that yet. The security will be increased greatly when the second phase is incorporated. Also the ability to detect brute-force attacks can be added to this system.
But the current system can be used for protecting the server from worms and random scanning. The use-case is similar to port knocking but it does not use the ugly system of opening the firewall for a couple of seconds. Vanilla port knocking is susceptible to brute-force attacks as well. Besides, inserting a kernel module to just ssh into your server will increase your mad sysadmin points.
Enhancements:
- TCP knocking with Phase 1 of the protocol was implemented.
Download (0.005MB)
Added: 2006-12-06 License: GPL (GNU General Public License) Price:
1054 downloads
NetPacket::TCP 0.04
NetPacket::TCP is a Perl module to assemble and disassemble TCP (Transmission Control Protocol) packets. more>>
NetPacket::TCP is a Perl module to assemble and disassemble TCP (Transmission Control Protocol) packets.
SYNOPSIS
use NetPacket::TCP;
$tcp_obj = NetPacket::TCP->decode($raw_pkt);
$tcp_pkt = NetPacket::TCP->encode($ip_pkt);
$tcp_data = NetPacket::TCP::strip($raw_pkt);
NetPacket::TCP provides a set of routines for assembling and disassembling packets using TCP (Transmission Control Protocol).
Methods
NetPacket::TCP->decode([RAW PACKET])
Decode the raw packet data given and return an object containing instance data. This method will quite happily decode garbage input. It is the responsibility of the programmer to ensure valid packet data is passed to this method.
NetPacket::TCP->encode($ip_obj)
Return a TCP packet encoded with the instance data specified. Needs parts of the ip header contained in $ip_obj in order to calculate the TCP checksum.
Functions
NetPacket::TCP::strip([RAW PACKET])
Return the encapsulated data (or payload) contained in the TCP packet. This data is suitable to be used as input for other NetPacket::* modules.
This function is equivalent to creating an object using the decode() constructor and returning the data field of that object.
Instance data
The instance data for the NetPacket::TCP object consists of the following fields.
src_port
The source TCP port for the packet.
dest_port
The destination TCP port for the packet.
seqnum
The TCP sequence number for this packet.
acknum
The TCP acknowledgement number for this packet.
hlen
The header length for this packet.
reserved
The 6-bit "reserved" space in the TCP header.
flags
Contains the urg, ack, psh, rst, syn, fin, ece and cwr flags for this packet.
winsize
The TCP window size for this packet.
cksum
The TCP checksum.
urg
The TCP urgent pointer.
options
Any TCP options for this packet in binary form.
data
The encapsulated data (payload) for this packet.
<<lessSYNOPSIS
use NetPacket::TCP;
$tcp_obj = NetPacket::TCP->decode($raw_pkt);
$tcp_pkt = NetPacket::TCP->encode($ip_pkt);
$tcp_data = NetPacket::TCP::strip($raw_pkt);
NetPacket::TCP provides a set of routines for assembling and disassembling packets using TCP (Transmission Control Protocol).
Methods
NetPacket::TCP->decode([RAW PACKET])
Decode the raw packet data given and return an object containing instance data. This method will quite happily decode garbage input. It is the responsibility of the programmer to ensure valid packet data is passed to this method.
NetPacket::TCP->encode($ip_obj)
Return a TCP packet encoded with the instance data specified. Needs parts of the ip header contained in $ip_obj in order to calculate the TCP checksum.
Functions
NetPacket::TCP::strip([RAW PACKET])
Return the encapsulated data (or payload) contained in the TCP packet. This data is suitable to be used as input for other NetPacket::* modules.
This function is equivalent to creating an object using the decode() constructor and returning the data field of that object.
Instance data
The instance data for the NetPacket::TCP object consists of the following fields.
src_port
The source TCP port for the packet.
dest_port
The destination TCP port for the packet.
seqnum
The TCP sequence number for this packet.
acknum
The TCP acknowledgement number for this packet.
hlen
The header length for this packet.
reserved
The 6-bit "reserved" space in the TCP header.
flags
Contains the urg, ack, psh, rst, syn, fin, ece and cwr flags for this packet.
winsize
The TCP window size for this packet.
cksum
The TCP checksum.
urg
The TCP urgent pointer.
options
Any TCP options for this packet in binary form.
data
The encapsulated data (payload) for this packet.
Download (0.011MB)
Added: 2007-02-28 License: Perl Artistic License Price:
971 downloads
EDIReader 4.1
EDIReader is a Java package for parsing business documents structured according to Electronic Data Interchange (EDI) standards. more>>
EDIReader is a Java package for parsing business documents structured according to EDI (Electronic Data Interchange) standards.
It supports the SAX and JAXP interfaces defined for XML, making it suitable for use in any XML-based system that allows the configuration of a custom SAX parser.
EDIReader parses EDI analogous to the way a conventional SAX parser parses XML, calling an arbitrary JAXP ContentHandler with elements and attributes as if it were parsing XML. Therefore, XSLT transformations and DOM-based tools can be applied directly to EDI input.
In many cases, EDIReader and an XSLT stylesheet provide a lightweight and open source alternative to conventional EDI mapper/translators.
Capturing an XML expression of the parsed EDI data is simple with EDIReader, and an EDItoXML utility is included as a demonstration program.
EDIReader is not a conventional EDI mapper/translator, nor by itself a replacement for one. Its purpose is to allow EDI input into a wide variety of XML-based systems so that tools used to transform and otherwise process XML-structured data can be applied to EDI as well. It requires no more configuration than any SAX parser, which is virtually none.
A design goal is to build in as much EDI awareness as is necessary to do its job and no more. Therefore, it handles all of the issues of EDI syntax so that XML tools such as XSLT can be applied to the issues of EDI structure and semantics. Since it does not need to perform full EDI compliance checking, it requires no tables of code values and the like to be installed and updated for particular EDI standards and versions.
Main features:
- Dynamic standard recognition - the parser differentiates between ANSI X.12 and EDIFACT EDI standards by inspection and uses a factory pattern to construct an appropriate parser subclass.
- Extensible - additional EDI standards can be supported by developing new subclasses.
- Checks for well-formed EDI syntax - EDIReader checks the basic syntactic correctness of the EDI structures according to the rules defined by ANSI X.12 or EDIFACT. This includes proper enveloping, embedded counts of segments and groups, and control number correspondence.
- Easily embedded - the parser can be embedded within your Java application in the same way as you would an XML parser, avoiding the file-based and proprietary interfaces often used with conventional EDI translators.
- Efficient - a single-pass algorithm is used to quickly and efficiently parse the EDI structures.
- Flexible segment terminator handling - EDIReader dynamically identifies the segment terminator character used with each individual EDI interchange. Special characters such as CR and LF may be used as segment terminators, and they may optionally appear after each segment following the formal segment terminator. With EDIReader it is not necessary to configure the terminator before the EDI data is parsed.
- Generation of Functional Acknowledgments - EDIReader can generate EDI function acknowledgments for the function groups within an ANSI X12 interchange as a by-product of parsing.
EDIReader can be enhanced with document-specific plugins that correspond to specific transaction sets (using ANSI terminology) or messages (using EDIFACT terminology). Plugins are optional and allow the parser to recognize segment groups and the way in which these groups are nested and repeated.
The XML generated by EDIReader reflects the segment grouping when a plugin is available, which is particularly useful when mapping EDI documents using XSLT.
Plugins for specific document types are available from BerryWorks Software, and several popular ones are included in the GPL version:
- ANSI 824 - Application Advice
- ANSI 835 - Health Care Claim Payment/Advice
- ANSI 837 - Health Care Claim
- EDIFACT MSCONS - Metered Services Consumption Report
- EDIFACT UTILMD - Utilities Master Data
<<lessIt supports the SAX and JAXP interfaces defined for XML, making it suitable for use in any XML-based system that allows the configuration of a custom SAX parser.
EDIReader parses EDI analogous to the way a conventional SAX parser parses XML, calling an arbitrary JAXP ContentHandler with elements and attributes as if it were parsing XML. Therefore, XSLT transformations and DOM-based tools can be applied directly to EDI input.
In many cases, EDIReader and an XSLT stylesheet provide a lightweight and open source alternative to conventional EDI mapper/translators.
Capturing an XML expression of the parsed EDI data is simple with EDIReader, and an EDItoXML utility is included as a demonstration program.
EDIReader is not a conventional EDI mapper/translator, nor by itself a replacement for one. Its purpose is to allow EDI input into a wide variety of XML-based systems so that tools used to transform and otherwise process XML-structured data can be applied to EDI as well. It requires no more configuration than any SAX parser, which is virtually none.
A design goal is to build in as much EDI awareness as is necessary to do its job and no more. Therefore, it handles all of the issues of EDI syntax so that XML tools such as XSLT can be applied to the issues of EDI structure and semantics. Since it does not need to perform full EDI compliance checking, it requires no tables of code values and the like to be installed and updated for particular EDI standards and versions.
Main features:
- Dynamic standard recognition - the parser differentiates between ANSI X.12 and EDIFACT EDI standards by inspection and uses a factory pattern to construct an appropriate parser subclass.
- Extensible - additional EDI standards can be supported by developing new subclasses.
- Checks for well-formed EDI syntax - EDIReader checks the basic syntactic correctness of the EDI structures according to the rules defined by ANSI X.12 or EDIFACT. This includes proper enveloping, embedded counts of segments and groups, and control number correspondence.
- Easily embedded - the parser can be embedded within your Java application in the same way as you would an XML parser, avoiding the file-based and proprietary interfaces often used with conventional EDI translators.
- Efficient - a single-pass algorithm is used to quickly and efficiently parse the EDI structures.
- Flexible segment terminator handling - EDIReader dynamically identifies the segment terminator character used with each individual EDI interchange. Special characters such as CR and LF may be used as segment terminators, and they may optionally appear after each segment following the formal segment terminator. With EDIReader it is not necessary to configure the terminator before the EDI data is parsed.
- Generation of Functional Acknowledgments - EDIReader can generate EDI function acknowledgments for the function groups within an ANSI X12 interchange as a by-product of parsing.
EDIReader can be enhanced with document-specific plugins that correspond to specific transaction sets (using ANSI terminology) or messages (using EDIFACT terminology). Plugins are optional and allow the parser to recognize segment groups and the way in which these groups are nested and repeated.
The XML generated by EDIReader reflects the segment grouping when a plugin is available, which is particularly useful when mapping EDI documents using XSLT.
Plugins for specific document types are available from BerryWorks Software, and several popular ones are included in the GPL version:
- ANSI 824 - Application Advice
- ANSI 835 - Health Care Claim Payment/Advice
- ANSI 837 - Health Care Claim
- EDIFACT MSCONS - Metered Services Consumption Report
- EDIFACT UTILMD - Utilities Master Data
Download (0.66MB)
Added: 2007-03-17 License: GPL (GNU General Public License) Price:
959 downloads
Webswell Connect 2.1.0
Webswell Connect is an e-business integration framework based on the ebXML standard. more>>
Webswell Connect is an e-business integration framework based on the ebXML standard. Webswell Connect allows easy, interactive and user-friendly installation.
It consists of an ebXML registry/repository server and client, a messaging system for secure and reliable messaging and user interface similar to popular email clients for sending/handling ebXML messages.
It supports HTTP, HTTPS, and email communication while keeping it safe and reliable by implementing digital signatures, encryption, acknowledgment mechanisms, duplication elimination, etc.
Enhancements:
- This version can be used as an SOA, ebxml, and AS2 integration tool.
- It includes HSQLDB as a default database system.
- It includes an interactive installer with supporting software.
- It includes Webswell Dispatcher 1.1.22, with improved handling of AS2 and ebxml Registry Repository messages.
- It is able to load Ebxml collaboration profiles agreements with hundreds of partnerships.
<<lessIt consists of an ebXML registry/repository server and client, a messaging system for secure and reliable messaging and user interface similar to popular email clients for sending/handling ebXML messages.
It supports HTTP, HTTPS, and email communication while keeping it safe and reliable by implementing digital signatures, encryption, acknowledgment mechanisms, duplication elimination, etc.
Enhancements:
- This version can be used as an SOA, ebxml, and AS2 integration tool.
- It includes HSQLDB as a default database system.
- It includes an interactive installer with supporting software.
- It includes Webswell Dispatcher 1.1.22, with improved handling of AS2 and ebxml Registry Repository messages.
- It is able to load Ebxml collaboration profiles agreements with hundreds of partnerships.
Download (153.9MB)
Added: 2007-08-16 License: Academic Free License (AFL) Price:
799 downloads
System.FilePath 0.11
System.FilePath is a Haskell library from Yhc originally, now with added tweaks. more>>
System.FilePath is a Haskell library from Yhc originally, now with added tweaks. Pure Haskell 98 (with Hierarchical libraries), no preprocessor. It has a nice interface for doing file manipulations, and works portably between Windows and Unix. [Not the same as http://darcs.haskell.org/~lemmih/FilePath/]
The interface is still changing, for that reason please use System.FilePath.Version_0_10 or System.FilePath.Version_0_11 which will be guaranteed to work unmodified in future releases.
I have written a System.FilePath module in part based on the one in
Yhc, and in part based on the one in Cabal (thanks to Lemmih). The aim
is to try and get this module into the base package, as FilePaths are
something many programs use, but its all too easy to hack up a little
function that gets it right most of the time on most platforms, and
there lies a source of bugs.
This module is Posix (Linux) and Windows capable - just import
System.FilePath and it will pick the right one. Of course, if you
demand Windows paths on all OSs, then System.FilePath.Windows will
give you that (same with Posix). Written in Haskell 98 + Heirarchical
Modules.
Haddock:
http://www-users.cs.york.ac.uk/~ndm/projects/filepath/System-FilePath.html
Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/filepath
Source: http://www.cs.york.ac.uk/fp/darcs/filepath/System/FilePath.hs
Homepage: http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php
If you go to the haddock page there are a few little examples at the
top of the file.
Acknowledgements
Thanks to Marc Webber, shapr, David House, Lemmih, others...
Competitors
System.FilePath from Cabal, by Lemmih
FilePath.hs and NameManip.hs from MissingH
The one from Cabal and FilePath.hs in MissingH are both very similar, I
stole lots of good ideas from those two.
NameManip seems to be more unix specific, but all functions in that module
have equivalents in this new System.FilePath module.
Hopefully this new module can be used without noticing any lost functions,
and certainly adds new features/functions to the table.
Should FilePath by an abstract data type?
The answer for this library is no. This is a deliberate design decision.
In Haskell 98 the definition is type FilePath = String, and all functions
operating on FilePaths, i.e. readFile/writeFile etc take FilePaths. The
only way to introduce an abstract type is to provide wrappers for these
functions or casts between Strings and FilePathAbstracts.
There are also additional questions as to what constitutes a FilePath, and
what is just a pure String. For example, "/path/file.ext" is a FilePath. Is
"/" ? "/path" ? "path" ? "file.ext" ? ".ext" ? "file" ?
With that being accepted, it should be trivial to write
System.FilePath.ByteString which has the same interface as System.FilePath
yet operates on ByteStrings.
<<lessThe interface is still changing, for that reason please use System.FilePath.Version_0_10 or System.FilePath.Version_0_11 which will be guaranteed to work unmodified in future releases.
I have written a System.FilePath module in part based on the one in
Yhc, and in part based on the one in Cabal (thanks to Lemmih). The aim
is to try and get this module into the base package, as FilePaths are
something many programs use, but its all too easy to hack up a little
function that gets it right most of the time on most platforms, and
there lies a source of bugs.
This module is Posix (Linux) and Windows capable - just import
System.FilePath and it will pick the right one. Of course, if you
demand Windows paths on all OSs, then System.FilePath.Windows will
give you that (same with Posix). Written in Haskell 98 + Heirarchical
Modules.
Haddock:
http://www-users.cs.york.ac.uk/~ndm/projects/filepath/System-FilePath.html
Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/filepath
Source: http://www.cs.york.ac.uk/fp/darcs/filepath/System/FilePath.hs
Homepage: http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php
If you go to the haddock page there are a few little examples at the
top of the file.
Acknowledgements
Thanks to Marc Webber, shapr, David House, Lemmih, others...
Competitors
System.FilePath from Cabal, by Lemmih
FilePath.hs and NameManip.hs from MissingH
The one from Cabal and FilePath.hs in MissingH are both very similar, I
stole lots of good ideas from those two.
NameManip seems to be more unix specific, but all functions in that module
have equivalents in this new System.FilePath module.
Hopefully this new module can be used without noticing any lost functions,
and certainly adds new features/functions to the table.
Should FilePath by an abstract data type?
The answer for this library is no. This is a deliberate design decision.
In Haskell 98 the definition is type FilePath = String, and all functions
operating on FilePaths, i.e. readFile/writeFile etc take FilePaths. The
only way to introduce an abstract type is to provide wrappers for these
functions or casts between Strings and FilePathAbstracts.
There are also additional questions as to what constitutes a FilePath, and
what is just a pure String. For example, "/path/file.ext" is a FilePath. Is
"/" ? "/path" ? "path" ? "file.ext" ? ".ext" ? "file" ?
With that being accepted, it should be trivial to write
System.FilePath.ByteString which has the same interface as System.FilePath
yet operates on ByteStrings.
Download (0.014MB)
Added: 2007-03-09 License: GPL (GNU General Public License) Price:
959 downloads
Module::Install::Philosophy 0.67
Module::Install::Philosophy Perl module contains the concepts behind Module::Install. more>>
Module::Install::Philosophy Perl module contains the concepts behind Module::Install.
SYNOPSIS
This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.
The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.
This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?
As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.
One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.
These are the current problems that I see with CPAN and the core modules:
New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.
I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.
One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.
CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.
<<lessSYNOPSIS
This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.
The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.
This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?
As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.
One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.
These are the current problems that I see with CPAN and the core modules:
New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.
I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.
One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.
CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.
Download (0.080MB)
Added: 2007-06-25 License: Perl Artistic License Price:
851 downloads
NRL NORM 1.3b9
NRL NORM is an implementation of NACK-Oriented Reliable Multicast. more>>
NRL NORM is an implementation of NACK-Oriented Reliable Multicast.
The NORM protocol is currently under development within the Internet Engineering Task Force (IETF) Reliable Multicast Transport (RMT) working group. The NORM protocol is designed to provide end-to-end reliable transport of bulk data objects or streams over generic IP multicast routing and forwarding services. NORM uses a selective, negative acknowledgement (NACK) mechanism for transport reliability and offers additional protocol mechanisms to conduct reliable multicast sessions with limited "a priori" coordination among senders and receivers.
A congestion control scheme is specified to allow the NORM protocol fairly share available network bandwidth with other transport protocols such as Transmission Control Protocol (TCP). It is capable of operating with both reciprocal multicast routing among senders and receivers and with asymmetric connectivity (possibly a unicast return path) from the senders to receivers.
The protocol offers a number of features to allow different types of applications or possibly other higher level transport protocols to utilize its service in different ways. The protocol leverages the use of FEC-based repair and other IETF reliable multicast transport (RMT) building blocks in its design.
Enhancements:
- This release fixes several moderate to major bugs, including divide-by-zero, assertion failures, and incorrect pointer dereferencing.
- It fixes numerous minor bugs.
<<lessThe NORM protocol is currently under development within the Internet Engineering Task Force (IETF) Reliable Multicast Transport (RMT) working group. The NORM protocol is designed to provide end-to-end reliable transport of bulk data objects or streams over generic IP multicast routing and forwarding services. NORM uses a selective, negative acknowledgement (NACK) mechanism for transport reliability and offers additional protocol mechanisms to conduct reliable multicast sessions with limited "a priori" coordination among senders and receivers.
A congestion control scheme is specified to allow the NORM protocol fairly share available network bandwidth with other transport protocols such as Transmission Control Protocol (TCP). It is capable of operating with both reciprocal multicast routing among senders and receivers and with asymmetric connectivity (possibly a unicast return path) from the senders to receivers.
The protocol offers a number of features to allow different types of applications or possibly other higher level transport protocols to utilize its service in different ways. The protocol leverages the use of FEC-based repair and other IETF reliable multicast transport (RMT) building blocks in its design.
Enhancements:
- This release fixes several moderate to major bugs, including divide-by-zero, assertion failures, and incorrect pointer dereferencing.
- It fixes numerous minor bugs.
Download (1.4MB)
Added: 2006-08-16 License: GPL (GNU General Public License) Price:
1169 downloads
BoboMail 0.6pre1
BoboMail is a so called webmail application, which provides mail access through a web interface. more>>
BoboMail is a so called webmail application, which provides mail access through a web interface.
It is distributed under the GNU GPL. See COPYING in the package or go to http://www.gnu.org for details.
The first version of BoboMail was used for about a year and a half in the intranet of the Computer Club Ostfriesland (one of Germanys largest computer clubs, see http://www.cco-ev.de if you understand German). I wrote my own webmailer, because at that time only some Perl scripts were available, which were not easy to customize (e.g. German interface).
The name of BoboMail comes from former name of ZPublisher, a cgi framework used by the developer.
I hope you will find BoboMail usefull. Please send complaints (e.g. spelling mistakes), criticism, security advices, suggestions, praises and everything else to ich@henning-schroeder.de or visit me (Henning) on my personal webpage at http://www.henning-schroeder.de/en Important acknowledgement: This product includes software developed by Digital Creations for use in the Z Object Publishing Environment (htt://www.zope.org).
The BoboMail distribution contains Zopes ZPublisher and ZTemplates. These compoments underly the Zope Public License (ZPL). They are packages with BoboMail for easier installation. BoboMail is hosted at Sourceforge (http://sourceforge.net). If you are interested in BoboMail development please visit the its webpage at http://bobomail.sourceforge.net Besides I want to make BoboMail even more modular so that my stuff can be used for a mailinglist archiver or a web-forum. Attention: I really would like to know where you will use BoboMail. Please tell me your success stories
Main features:
- read, write, reply, forward, delete and bounce messages
- send and receive attachments
- decodes quoted-printable, base64 and uuencoded
- handles HTML-mails properly (with inline images!)
- does not need Javascript
- direct support for the following MIME types: message/rfc822, message/delivery-status, multipart/alternative, multipart/mixed, multipart/report, multipart/related, multipart/digest, text/plain, text/html, text/x-vcard, image/jpeg, text/rfc822-headers, image/png, image/x-xpixmap, image/gif
- works with POP3-servers and partially IMAP4 (spool-files under development)
- easy to modify and customize through HTML-templates
- modular design provides easy interface for other authentication methods and mail protocols
- provides optionally its own fast multithreading webserver (BoboMailHTTPD)
- multi-lingual support (i18n) - currently English, Brazilian Portuguese, Finish, Spanish and German
- and its 100% Python
Enhancements:
- with the help from Ken Causey the annoying first-login-bug is fixed now :-)
- IMAP support for uw-imapd, expects additional folders in $HOME/Mail
- now runs with Python 2.x without problems
- new look, using nicer template inspired by zope.org
- and some other small bug fixes (see cvs if you like)
<<lessIt is distributed under the GNU GPL. See COPYING in the package or go to http://www.gnu.org for details.
The first version of BoboMail was used for about a year and a half in the intranet of the Computer Club Ostfriesland (one of Germanys largest computer clubs, see http://www.cco-ev.de if you understand German). I wrote my own webmailer, because at that time only some Perl scripts were available, which were not easy to customize (e.g. German interface).
The name of BoboMail comes from former name of ZPublisher, a cgi framework used by the developer.
I hope you will find BoboMail usefull. Please send complaints (e.g. spelling mistakes), criticism, security advices, suggestions, praises and everything else to ich@henning-schroeder.de or visit me (Henning) on my personal webpage at http://www.henning-schroeder.de/en Important acknowledgement: This product includes software developed by Digital Creations for use in the Z Object Publishing Environment (htt://www.zope.org).
The BoboMail distribution contains Zopes ZPublisher and ZTemplates. These compoments underly the Zope Public License (ZPL). They are packages with BoboMail for easier installation. BoboMail is hosted at Sourceforge (http://sourceforge.net). If you are interested in BoboMail development please visit the its webpage at http://bobomail.sourceforge.net Besides I want to make BoboMail even more modular so that my stuff can be used for a mailinglist archiver or a web-forum. Attention: I really would like to know where you will use BoboMail. Please tell me your success stories
Main features:
- read, write, reply, forward, delete and bounce messages
- send and receive attachments
- decodes quoted-printable, base64 and uuencoded
- handles HTML-mails properly (with inline images!)
- does not need Javascript
- direct support for the following MIME types: message/rfc822, message/delivery-status, multipart/alternative, multipart/mixed, multipart/report, multipart/related, multipart/digest, text/plain, text/html, text/x-vcard, image/jpeg, text/rfc822-headers, image/png, image/x-xpixmap, image/gif
- works with POP3-servers and partially IMAP4 (spool-files under development)
- easy to modify and customize through HTML-templates
- modular design provides easy interface for other authentication methods and mail protocols
- provides optionally its own fast multithreading webserver (BoboMailHTTPD)
- multi-lingual support (i18n) - currently English, Brazilian Portuguese, Finish, Spanish and German
- and its 100% Python
Enhancements:
- with the help from Ken Causey the annoying first-login-bug is fixed now :-)
- IMAP support for uw-imapd, expects additional folders in $HOME/Mail
- now runs with Python 2.x without problems
- new look, using nicer template inspired by zope.org
- and some other small bug fixes (see cvs if you like)
Download (0.29MB)
Added: 2006-06-10 License: GPL (GNU General Public License) Price:
1232 downloads
NIST 2.2.2
The NIST Implementation of the Ad-Hoc On Demand Distance Vector protocol is a kernel-level driver for Linux . more>>
The NIST Implementation of the Ad-Hoc On Demand Distance Vector protocol is a kernel-level driver for Linux . AODV is a routing protocol for ad hoc networks designed with mobile wireless devices in mind. For a quick overview on AODVs basics, check out our Quick Guide to AODV page. If you are interested in running a simulation of AODV, NIST has developed a simulation in OPNET.
Kernel AODV is a loadable kernel module for Linux. It implements AODV routing between computers equipped with WLAN interfaces.
This software was developed at the National Institute of Standards and Technology by employees of the Federal Government in the course of their official duties. Pursuant to title 17 Section 105 of the United States Code this software is not subject to copyright protection and is in the public domain. Kernel AODV is an experimental system. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic. We would appreciate acknowledgement if the software is used.
This software can be redistributed and/or modified freely provided that any derivative works bear some notice that they are derived from it, and any modified versions bear some notice that they have been modified.
Enhancements:
- Corrected LINK_LIMIT #ifdefs (Fix from Peter Barron)
- aodv_neigh.c
- hello.c
- module.c
- Add Packet Queuing back in (Fix from Peter Barron)
- Send queued messages when recieving a route, aodv_route.c
- Drop packet from queue if RREQ fails, rreq.c
- Added packet_queue.c back in, packet_queue.c
- Added init and cleanup of packet_queue, module.c
- Added additional check to packet_out.c to determine if packet is going to external subnet on a gateway.
- Shouldnt be neccesary since a route should be created for the external destination anyhow. Have to look into this. (Fix from Peter Barron)
- Removed annoying message printed when signal strength can not be read. Instead only prints when can not be set. signal.c
- Fixed the undefined symbol STRCHR problem for real this time. The problem is doing strstr() with a singlecharecter results in it being converted to strchr(), but for some reason it is not properly imported. The solution it to simply use stchr() instead. module.c
- Changed it so that find_aodv_route() will return valid routes that have expired. When it didnt return expired routes two routes would sometimes be created. Also, now kernel routes are only removed when an expired route is removed. find_aodv_route() will also invalidate expired valid routes.
- Had some trouble with duplicate kernel routes. Now we are always deleting before inserting a new route. Should fix it, fingers are crossed.
- Changed delete_neighbor() so that we send out an RERR even if the route is no longer valid. Also change gen_rerr() so that is will send out a RERR even if the route is not valid. It has to be better to send out a few extra rather than not enough. Just cause you have timed a route out doesnt mean others have.
- Compared the Metrics wrong in update_route() if the seq numbers were equal.
<<lessKernel AODV is a loadable kernel module for Linux. It implements AODV routing between computers equipped with WLAN interfaces.
This software was developed at the National Institute of Standards and Technology by employees of the Federal Government in the course of their official duties. Pursuant to title 17 Section 105 of the United States Code this software is not subject to copyright protection and is in the public domain. Kernel AODV is an experimental system. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic. We would appreciate acknowledgement if the software is used.
This software can be redistributed and/or modified freely provided that any derivative works bear some notice that they are derived from it, and any modified versions bear some notice that they have been modified.
Enhancements:
- Corrected LINK_LIMIT #ifdefs (Fix from Peter Barron)
- aodv_neigh.c
- hello.c
- module.c
- Add Packet Queuing back in (Fix from Peter Barron)
- Send queued messages when recieving a route, aodv_route.c
- Drop packet from queue if RREQ fails, rreq.c
- Added packet_queue.c back in, packet_queue.c
- Added init and cleanup of packet_queue, module.c
- Added additional check to packet_out.c to determine if packet is going to external subnet on a gateway.
- Shouldnt be neccesary since a route should be created for the external destination anyhow. Have to look into this. (Fix from Peter Barron)
- Removed annoying message printed when signal strength can not be read. Instead only prints when can not be set. signal.c
- Fixed the undefined symbol STRCHR problem for real this time. The problem is doing strstr() with a singlecharecter results in it being converted to strchr(), but for some reason it is not properly imported. The solution it to simply use stchr() instead. module.c
- Changed it so that find_aodv_route() will return valid routes that have expired. When it didnt return expired routes two routes would sometimes be created. Also, now kernel routes are only removed when an expired route is removed. find_aodv_route() will also invalidate expired valid routes.
- Had some trouble with duplicate kernel routes. Now we are always deleting before inserting a new route. Should fix it, fingers are crossed.
- Changed delete_neighbor() so that we send out an RERR even if the route is no longer valid. Also change gen_rerr() so that is will send out a RERR even if the route is not valid. It has to be better to send out a few extra rather than not enough. Just cause you have timed a route out doesnt mean others have.
- Compared the Metrics wrong in update_route() if the seq numbers were equal.
Download (0.037MB)
Added: 2006-07-06 License: GPL (GNU General Public License) Price:
1213 downloads
Limb3 2007.3
Limb is an OpenSource PHP framework aimed for rapid web application development. more>>
Limb is an OpenSource PHP framework aimed for rapid web application development.
We are committed proponents of beautiful and easy-to-maintain code that simply works. That is why we develop and constantly refactor Limb code in a test driven manner using the best agile development practices.
The latest version of framework is Limb3 which consists of many reusable components distributed as packages on Limb3 PEAR channel.
The previous version Limb2 is a PHP4 compatible framework for building web sites with rich and easy-to-update content. In acknowledgement of the original approach in 2004 Limb2 got the 3d place in Zend Contest. However nowadays Limb2 development is almost frozen since the core dev. team is mostly focused on Limb3. Someday Limb2 will be a simply package of the more general Limb3 framework.
Main features:
- PHP-5.2 compatibility
- lmbActiveRecord better inheritance and value objects support
- DATASOURCE package cruft cleanup and unification
- merge of DATASOURCE and CLASSKIT packages into CORE package
- new FS package(merging FILE_SCHEMA and UTIL packages)
- new LOG package(extracted from ERROR package)
- TREE package code overhaul and new features(nested sets driver is available again)
- more friendly error subsystem
- form errors better implementation
- TESTS_RUNNER improved CLI and phpSpikesCoverage support
- LIMB_VAR_DIR dependency removal from base classes
- reimplementation of CALENDAR package using better JavaScript alternative
- DATETIME package cleanup and misc improvements
- initial TinyMC support in WYSIWYG package
- FCKEditor updated to 2.4.2
- WACT better expressions support
- SQLite DB driver
- DBAL package refactoring and cleanup, lmbDBAL is a central facade for accessing mis. tools in a package
- JS package cleanup, moving to jQuery instead of Prototype
- more isolated packages tests
Enhancements:
- PHP 5.2 compatibility was added.
- Better inheritance and value objects support was implemented for lmbActiveRecord.
- A new FS package was added, which merges the FILE_SCHEMA and UTIL packages.
- A new LOG package was extracted from the ERROR package.
- The TREE package code was overhauled and new features were added.
- The error subsystem was made more friendly.
- The CLI and phpSpikesCoverage support of TESTS_RUNNER were improved.
- The CALENDAR package was reimplemented using a better JavaScript alternative.
- Initial TinyMC support was added in the WYSIWYG package.
- FCKEditor was updated to 2.4.2.
- An SQLite DB driver was added.
<<lessWe are committed proponents of beautiful and easy-to-maintain code that simply works. That is why we develop and constantly refactor Limb code in a test driven manner using the best agile development practices.
The latest version of framework is Limb3 which consists of many reusable components distributed as packages on Limb3 PEAR channel.
The previous version Limb2 is a PHP4 compatible framework for building web sites with rich and easy-to-update content. In acknowledgement of the original approach in 2004 Limb2 got the 3d place in Zend Contest. However nowadays Limb2 development is almost frozen since the core dev. team is mostly focused on Limb3. Someday Limb2 will be a simply package of the more general Limb3 framework.
Main features:
- PHP-5.2 compatibility
- lmbActiveRecord better inheritance and value objects support
- DATASOURCE package cruft cleanup and unification
- merge of DATASOURCE and CLASSKIT packages into CORE package
- new FS package(merging FILE_SCHEMA and UTIL packages)
- new LOG package(extracted from ERROR package)
- TREE package code overhaul and new features(nested sets driver is available again)
- more friendly error subsystem
- form errors better implementation
- TESTS_RUNNER improved CLI and phpSpikesCoverage support
- LIMB_VAR_DIR dependency removal from base classes
- reimplementation of CALENDAR package using better JavaScript alternative
- DATETIME package cleanup and misc improvements
- initial TinyMC support in WYSIWYG package
- FCKEditor updated to 2.4.2
- WACT better expressions support
- SQLite DB driver
- DBAL package refactoring and cleanup, lmbDBAL is a central facade for accessing mis. tools in a package
- JS package cleanup, moving to jQuery instead of Prototype
- more isolated packages tests
Enhancements:
- PHP 5.2 compatibility was added.
- Better inheritance and value objects support was implemented for lmbActiveRecord.
- A new FS package was added, which merges the FILE_SCHEMA and UTIL packages.
- A new LOG package was extracted from the ERROR package.
- The TREE package code was overhauled and new features were added.
- The error subsystem was made more friendly.
- The CLI and phpSpikesCoverage support of TESTS_RUNNER were improved.
- The CALENDAR package was reimplemented using a better JavaScript alternative.
- Initial TinyMC support was added in the WYSIWYG package.
- FCKEditor was updated to 2.4.2.
- An SQLite DB driver was added.
Download (2.1MB)
Added: 2007-07-16 License: LGPL (GNU Lesser General Public License) Price:
831 downloads
Sunrise 0.42j
Sunrise project converts websites and newsfeeds for offline reading on your handheld. more>>
Sunrise project converts websites and newsfeeds for offline reading on your handheld.
Offline browser for handhelds (like AvantGO).
Sunrise is open-source software released under the BSD license.
Getting Started
Sunrise requires Java 1.5. (Earlier Java versions will not work correctly due to issues with the java.nio library.)
Start Sunrise Desktop with the script "sunrise-desktop.sh".
Some documentation can be found in the "web" subdirectory.
Acknowledgements
This product includes software developed by Andy Clark.
This product includes software developed by the Apache Software Foundation.
Toolbar icons and banner images taken from the Eclipse project.
<<lessOffline browser for handhelds (like AvantGO).
Sunrise is open-source software released under the BSD license.
Getting Started
Sunrise requires Java 1.5. (Earlier Java versions will not work correctly due to issues with the java.nio library.)
Start Sunrise Desktop with the script "sunrise-desktop.sh".
Some documentation can be found in the "web" subdirectory.
Acknowledgements
This product includes software developed by Andy Clark.
This product includes software developed by the Apache Software Foundation.
Toolbar icons and banner images taken from the Eclipse project.
Download (2.8MB)
Added: 2007-01-17 License: BSD License Price:
1016 downloads
mod_auth_cookie_dbm 1.0.2
mod_auth_cookie_dbm is a session authentication/expiration using (cryptographically strong) cookies. more>>
mod_auth_cookie_dbm is a session authentication/expiration using (cryptographically strong) cookies. Cookie-to-username mapping with DBM database.
It was devised as a better replacement for the "Basic" authentication components that ship with Apache.
Classic "Basic" authentication has some downsides:
- Username and password are shipped across the net with every request.
- There is no concept of a "session" (nor encores, such as timeouts and automatic logout)
This module
1. checks requests for a cookie, named in the CookieDBMAuthCookieName configuration directive.
2. If found, the cookie value is looked up in a DBM database, named in the CookieDBMAuthFile directive.
If the lookup fails, a redirect is made to a page specified in the CookieDBMAuthFailureURL directive.
3. The DBM entry is expected to contain a username and optionally an expiry time. Fields are colon-separated, the expiry time is a spelled-out integer (the field gets passed to strtol()) representing the time_t
If valid, the username is taped onto the request, thus "emulating" Basic authentication.
If expired, redirect to the CookieDBMAuthFailureURL.
The CookieDBMAuthFailureURL typically points at a "login page" CGI script. This program, after checking the users credentials, should make up a cookie value (preferably a long, cryptographically strong random string), enter it in the dbm file, and pass it to the browser. It might also update an AuthUserFile or AuthDBMUserFile database on the fly.
Acknowledgements:
This module was written from scratch, with some inspiration from the mod_auth_cookie_mysql and mod_auth_cookie_pgsql2 modules.
<<lessIt was devised as a better replacement for the "Basic" authentication components that ship with Apache.
Classic "Basic" authentication has some downsides:
- Username and password are shipped across the net with every request.
- There is no concept of a "session" (nor encores, such as timeouts and automatic logout)
This module
1. checks requests for a cookie, named in the CookieDBMAuthCookieName configuration directive.
2. If found, the cookie value is looked up in a DBM database, named in the CookieDBMAuthFile directive.
If the lookup fails, a redirect is made to a page specified in the CookieDBMAuthFailureURL directive.
3. The DBM entry is expected to contain a username and optionally an expiry time. Fields are colon-separated, the expiry time is a spelled-out integer (the field gets passed to strtol()) representing the time_t
If valid, the username is taped onto the request, thus "emulating" Basic authentication.
If expired, redirect to the CookieDBMAuthFailureURL.
The CookieDBMAuthFailureURL typically points at a "login page" CGI script. This program, after checking the users credentials, should make up a cookie value (preferably a long, cryptographically strong random string), enter it in the dbm file, and pass it to the browser. It might also update an AuthUserFile or AuthDBMUserFile database on the fly.
Acknowledgements:
This module was written from scratch, with some inspiration from the mod_auth_cookie_mysql and mod_auth_cookie_pgsql2 modules.
Download (0.008MB)
Added: 2006-05-25 License: BSD License Price:
1247 downloads
Got Word Database Maker 1.3
Bible trivia game that is a cross between the TV game show Who Wants to be a Millionaire? more>>
Hello! Thank you for donating your knowledge and time to our cause. Pariahware, Inc. is currently working on a Bible trivia game that is a cross between the TV game show "Who Wants to be a Millionaire?" and the electronic game series "You Dont Know Jack!" As one might imagine, this can be a daunting task.
That is why we are asking for your help in coming up with some GREAT Bible questions in order to make this game even more fun than we could do by ourselves! When you are finished submitting all of your questions, please e-mail the "qanda.rsd" file back to submissions@pariahware.com. By submitting the questions that you come up with, you agree to the following:
The Legal:
1. You expect no royalty fees or other payment for Pariahware, Inc. using your questions in the game.
2. Any parts of the questions you submit may be altered at will by the members of Pariahware, Inc.
3. Even though you submit a question for the game, that does not necessarily mean it will appear in the game.
4. If your name is included in your e-mail, Pariahware, Inc. has the right to add it as an acknowledgement, unless otherwise noted. You will not be paid as a result of having your name listed.
The How To:
1. Make sure that the Got Word DB Maker application and the "qanda.rsd" file are in the same folder or the program will not work.
2. Double-click the Got Word DB Maker application icon.
3. Select the radio button in the lower-left-hand corner that says "Add new question".
4. There are five text fields. The large one on the top is for the question. The other four are for potential answers. All of these need to be filled.
5. The correct answer needs to be selected by the "drop down" in the upper-right-hand corner.
6. The book of the Bible, in which the question is referencing, needs to be selected in the upper-left-hand corner.
7. Below the book selection is value (points) for the question. This needs to be selected as well.
8. When all of this has been done, the "Save New Question" button will activate. Click it to save your question.
Word of Caution:
To make changes to question that you have already entered, click the "edit existing questions" radio button.
Enhancements:
- Bug Fixes.
<<lessThat is why we are asking for your help in coming up with some GREAT Bible questions in order to make this game even more fun than we could do by ourselves! When you are finished submitting all of your questions, please e-mail the "qanda.rsd" file back to submissions@pariahware.com. By submitting the questions that you come up with, you agree to the following:
The Legal:
1. You expect no royalty fees or other payment for Pariahware, Inc. using your questions in the game.
2. Any parts of the questions you submit may be altered at will by the members of Pariahware, Inc.
3. Even though you submit a question for the game, that does not necessarily mean it will appear in the game.
4. If your name is included in your e-mail, Pariahware, Inc. has the right to add it as an acknowledgement, unless otherwise noted. You will not be paid as a result of having your name listed.
The How To:
1. Make sure that the Got Word DB Maker application and the "qanda.rsd" file are in the same folder or the program will not work.
2. Double-click the Got Word DB Maker application icon.
3. Select the radio button in the lower-left-hand corner that says "Add new question".
4. There are five text fields. The large one on the top is for the question. The other four are for potential answers. All of these need to be filled.
5. The correct answer needs to be selected by the "drop down" in the upper-right-hand corner.
6. The book of the Bible, in which the question is referencing, needs to be selected in the upper-left-hand corner.
7. Below the book selection is value (points) for the question. This needs to be selected as well.
8. When all of this has been done, the "Save New Question" button will activate. Click it to save your question.
Word of Caution:
To make changes to question that you have already entered, click the "edit existing questions" radio button.
Enhancements:
- Bug Fixes.
Download (1.3MB)
Added: 2006-04-21 License: Freeware Price:
1283 downloads
Gspoof 3.2.
Gspoof is a GTK+ program which makes easier and accurate the building and the sending of TCP packet with a data-payload or not. more>>
Gspoof is a GTK+ program which makes easier and accurate the building and the sending of TCP packet with a data-payload or not. Its possible to modify TCP/IP fields also Ethernet header working to Link Level.
The program works in two different mode:
The 1st (the standard mode) allow "only" adjustment of IP and TCP headers.
Exactly:
source IP address (if possible is autodetect from available interface) destination IP address TTL time to live (default value is 64) ID (a 16 byte random generate value) TOS type of service (automagically calculated from ECN parameters)
source port
destination port
control flags (you can specify more flags toghether)
sequence number (a 32 byte random generate value)
acknowledgement number (a 32 byte random generate value)
window size (default vale is 32767)
urgent pointer (a 16 byte random generate value)
Enhancements:
- Added Explicit Congestion Notification support (thanks to )
- Fixed a bug in ltostr()
- Cleaned code in console.c
- Fixed some tips
<<lessThe program works in two different mode:
The 1st (the standard mode) allow "only" adjustment of IP and TCP headers.
Exactly:
source IP address (if possible is autodetect from available interface) destination IP address TTL time to live (default value is 64) ID (a 16 byte random generate value) TOS type of service (automagically calculated from ECN parameters)
source port
destination port
control flags (you can specify more flags toghether)
sequence number (a 32 byte random generate value)
acknowledgement number (a 32 byte random generate value)
window size (default vale is 32767)
urgent pointer (a 16 byte random generate value)
Enhancements:
- Added Explicit Congestion Notification support (thanks to )
- Fixed a bug in ltostr()
- Cleaned code in console.c
- Fixed some tips
Download (0.067MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1207 downloads
PDL::FAQ 2.4.3
PDL::FAQ is a Perl module for frequently asked questions about PDL. more>>
PDL::FAQ is a Perl module for frequently asked questions about PDL.
This is a considerably reworked version of the PDL FAQ. As such many errors might have crept in and many updates might not have made it in. You are explicitly encouraged to let us know about questions which you think should be answered in this document but currently arent.
Similarly, if you think parts of this document are unclear, please tell the FAQ maintainer about it. Where a specific answer is taken in full from someones posting the authorship should be indicated, let the FAQ maintainer know if it isnt. For more general information explicit acknowledgement is not made in the text, but rather there is an incomplete list of contributors at the end of this docuement. Please contact the FAQ maintainer if you feel hard done by.
<<lessThis is a considerably reworked version of the PDL FAQ. As such many errors might have crept in and many updates might not have made it in. You are explicitly encouraged to let us know about questions which you think should be answered in this document but currently arent.
Similarly, if you think parts of this document are unclear, please tell the FAQ maintainer about it. Where a specific answer is taken in full from someones posting the authorship should be indicated, let the FAQ maintainer know if it isnt. For more general information explicit acknowledgement is not made in the text, but rather there is an incomplete list of contributors at the end of this docuement. Please contact the FAQ maintainer if you feel hard done by.
Download (2.1MB)
Added: 2006-09-19 License: Perl Artistic License Price:
1130 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 acknowledgement 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
