plaintext
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 62
Pod::PlainText 1.34
Pod::PlainText is a Perl module that can convert POD data to formatted ASCII text. more>>
Pod::PlainText is a Perl module that can convert POD data to formatted ASCII text.
SYNOPSIS
use Pod::PlainText;
my $parser = Pod::PlainText->new (sentence => 0, width => 78);
# Read POD from STDIN and write to STDOUT.
$parser->parse_from_filehandle;
# Read POD from file.pod and write to file.txt.
$parser->parse_from_file (file.pod, file.txt);
Pod::PlainText is a module that can convert documentation in the POD format (the preferred language for documenting Perl) into formatted ASCII. It uses no special formatting controls or codes whatsoever, and its output is therefore suitable for nearly any device.
As a derived class from Pod::Parser, Pod::PlainText supports the same methods and interfaces. See Pod::Parser for all the details; briefly, one creates a new parser with Pod::PlainText->new() and then calls either parse_from_filehandle() or parse_from_file().
<<lessSYNOPSIS
use Pod::PlainText;
my $parser = Pod::PlainText->new (sentence => 0, width => 78);
# Read POD from STDIN and write to STDOUT.
$parser->parse_from_filehandle;
# Read POD from file.pod and write to file.txt.
$parser->parse_from_file (file.pod, file.txt);
Pod::PlainText is a module that can convert documentation in the POD format (the preferred language for documenting Perl) into formatted ASCII. It uses no special formatting controls or codes whatsoever, and its output is therefore suitable for nearly any device.
As a derived class from Pod::Parser, Pod::PlainText supports the same methods and interfaces. See Pod::Parser for all the details; briefly, one creates a new parser with Pod::PlainText->new() and then calls either parse_from_filehandle() or parse_from_file().
Download (0.094MB)
Added: 2006-08-15 License: Perl Artistic License Price:
1165 downloads
Crypt::OpenPGP::Plaintext 1.03
Crypt::OpenPGP::Plaintext is a plaintext, literal-data packet. more>>
Crypt::OpenPGP::Plaintext is a plaintext, literal-data packet.
SYNOPSIS
use Crypt::OpenPGP::Plaintext;
my $pt = Crypt::OpenPGP::Plaintext->new(
Data => $data,
Filename => $file,
);
my $serialized = $pt->save;
my $pt = Crypt::OpenPGP::Plaintext->parse($buffer);
Crypt::OpenPGP::Plaintext implements plaintext literal-data packets, and is essentially just a container for a string of octets, along with some meta-data about the plaintext.
USAGE
Crypt::OpenPGP::Plaintext->new( %arg )
Creates a new plaintext data packet object and returns that object. If there are no arguments in %arg, the object is created with an empty data container; this is used, for example, in parse (below), to create an empty packet which is then filled from the data in the buffer.
If you wish to initialize a non-empty object, %arg can contain:
Data
A block of octets that make up the plaintext data.
This argument is required (for a non-empty object).
Filename
The name of the file that this data came from, or the name of a file where it should be saved upon extraction from the packet (after decryption, for example, if this packet is going to be encrypted).
Mode
The mode in which the data is formatted. Valid values are t and b, meaning "text" and "binary", respectively.
This argument is optional; Mode defaults to b.
$pt->save
Returns the serialized form of the plaintext object, which is the plaintext data, preceded by some meta-data describing the data.
Crypt::OpenPGP::Plaintext->parse($buffer)
Given $buffer, a Crypt::OpenPGP::Buffer object holding (or with offset pointing to) a plaintext data packet, returns a new Crypt::OpenPGP::Ciphertext object, initialized with the data in the buffer.
$pt->data
Returns the plaintext data.
$pt->mode
Returns the mode of the packet (either t or b).
<<lessSYNOPSIS
use Crypt::OpenPGP::Plaintext;
my $pt = Crypt::OpenPGP::Plaintext->new(
Data => $data,
Filename => $file,
);
my $serialized = $pt->save;
my $pt = Crypt::OpenPGP::Plaintext->parse($buffer);
Crypt::OpenPGP::Plaintext implements plaintext literal-data packets, and is essentially just a container for a string of octets, along with some meta-data about the plaintext.
USAGE
Crypt::OpenPGP::Plaintext->new( %arg )
Creates a new plaintext data packet object and returns that object. If there are no arguments in %arg, the object is created with an empty data container; this is used, for example, in parse (below), to create an empty packet which is then filled from the data in the buffer.
If you wish to initialize a non-empty object, %arg can contain:
Data
A block of octets that make up the plaintext data.
This argument is required (for a non-empty object).
Filename
The name of the file that this data came from, or the name of a file where it should be saved upon extraction from the packet (after decryption, for example, if this packet is going to be encrypted).
Mode
The mode in which the data is formatted. Valid values are t and b, meaning "text" and "binary", respectively.
This argument is optional; Mode defaults to b.
$pt->save
Returns the serialized form of the plaintext object, which is the plaintext data, preceded by some meta-data describing the data.
Crypt::OpenPGP::Plaintext->parse($buffer)
Given $buffer, a Crypt::OpenPGP::Buffer object holding (or with offset pointing to) a plaintext data packet, returns a new Crypt::OpenPGP::Ciphertext object, initialized with the data in the buffer.
$pt->data
Returns the plaintext data.
$pt->mode
Returns the mode of the packet (either t or b).
Download (0.095MB)
Added: 2007-08-17 License: Perl Artistic License Price:
799 downloads
MS Word to plaintext converter 0.1
MS Word to plaintext converter is a service menue easily converts MS Word documents to plain text files. more>>
MS Word to plaintext converter is a service menue easily converts MS Word documents to plain text files. The generated text file is named *.doc.txt.
I hope it is as useful for you as it is for me.
<<lessI hope it is as useful for you as it is for me.
Download (MB)
Added: 2006-04-26 License: GPL (GNU General Public License) Price:
1283 downloads
App::SimpleScan::Plugin::Plaintext 1.02
App::SimpleScan::Plugin::Plaintext is a Perl module that can check a pages text without markup. more>>
App::SimpleScan::Plugin::Plaintext is a Perl module that can check a pages text without markup.
SYNOPSIS
# Normal test specs use the entire HTML text
http://perl.org/ /books n | / Y Sites list HTML
# If we want to match just the text, not the HTML:
%%plaintext on
http://perl.org/ /|books | dev | history | jobs/ Y Literal list
# And we can turn this back off again:
%%plaintext off
This plugin adds the %%plaintext pragma. This allows you to write test specs that match the visible text on a page, as opposed to the HTML text. This is useful if you want to make sure (for instance) if specific text is on the page, but you dont care how its marked up.
INTERFACE
pragmas
Exports the %%plaintext pragma handler to App::SimpleScan.
plaintext_pragma
Actually handles the pragma statement. Calls the exported plaintext method to record the current state (on or off).
filters
Standard App::SimpleScan callback; returns the code filters.
filter
If the plaintext method returns true, we alter the tests to use text_like and text_unlike instead of page_like and page_unlike. In eitehr case, we return the code to the caller (standard interface).
<<lessSYNOPSIS
# Normal test specs use the entire HTML text
http://perl.org/ /books n | / Y Sites list HTML
# If we want to match just the text, not the HTML:
%%plaintext on
http://perl.org/ /|books | dev | history | jobs/ Y Literal list
# And we can turn this back off again:
%%plaintext off
This plugin adds the %%plaintext pragma. This allows you to write test specs that match the visible text on a page, as opposed to the HTML text. This is useful if you want to make sure (for instance) if specific text is on the page, but you dont care how its marked up.
INTERFACE
pragmas
Exports the %%plaintext pragma handler to App::SimpleScan.
plaintext_pragma
Actually handles the pragma statement. Calls the exported plaintext method to record the current state (on or off).
filters
Standard App::SimpleScan callback; returns the code filters.
filter
If the plaintext method returns true, we alter the tests to use text_like and text_unlike instead of page_like and page_unlike. In eitehr case, we return the code to the caller (standard interface).
Download (0.005MB)
Added: 2006-12-19 License: Perl Artistic License Price:
1039 downloads
Template::Plugin::HtmlToText 0.02
Template::Plugin::HtmlToText is a plugin interface to HTML::FormatText. more>>
Template::Plugin::HtmlToText is a plugin interface to HTML::FormatText.
SYNOPSIS
Quick summary of what the module does.
Perhaps a little code snippet.
[% USE HtmlToText %]
# use html2text FILTER to var myhtml or myhtmltext
[% myhtml FILTER html2text(leftmargin => 0, rightmargin => 50) %]
[% myhtmltext | html2text %]
# not to a var, but to html code
[% FILTER html2text %]
heavy
[% END %]
[%# output is "heavy", no %]
This plugin provides an interface to the HTML::FormatText module which format HTML as plaintext.
<<lessSYNOPSIS
Quick summary of what the module does.
Perhaps a little code snippet.
[% USE HtmlToText %]
# use html2text FILTER to var myhtml or myhtmltext
[% myhtml FILTER html2text(leftmargin => 0, rightmargin => 50) %]
[% myhtmltext | html2text %]
# not to a var, but to html code
[% FILTER html2text %]
heavy
[% END %]
[%# output is "heavy", no %]
This plugin provides an interface to the HTML::FormatText module which format HTML as plaintext.
Download (0.003MB)
Added: 2007-08-02 License: Perl Artistic License Price:
813 downloads
GnuPG::Interface 0.33
GnuPG::Interface is a Perl interface to GnuPG. more>>
GnuPG::Interface is a Perl interface to GnuPG.
SYNOPSIS
# A simple example
use IO::Handle;
use GnuPG::Interface;
# settting up the situation
my $gnupg = GnuPG::Interface->new();
$gnupg->options->hash_init( armor => 1,
homedir => /home/foobar );
# Note you can set the recipients even if you arent encrypting!
$gnupg->options->push_recipients( ftobin@cpan.org );
$gnupg->options->meta_interactive( 0 );
# how we create some handles to interact with GnuPG
my $input = IO::Handle->new();
my $output = IO::Handle->new();
my $handles = GnuPG::Handles->new( stdin => $input,
stdout => $output );
# Now well go about encrypting with the options already set
my @plaintext = ( foobar );
my $pid = $gnupg->encrypt( handles => $handles );
# Now we write to the input of GnuPG
print $input @plaintext;
close $input;
# now we read the output
my @ciphertext = ;
close $output;
waitpid $pid, 0;
GnuPG::Interface and its associated modules are designed to provide an object-oriented method for interacting with GnuPG, being able to perform functions such as but not limited to encrypting, signing, decryption, verification, and key-listing parsing.
How Data Member Accessor Methods are Created
Each module in the GnuPG::Interface bundle relies on Class::MethodMaker to generate the get/set methods used to set the objects data members. This is very important to realize. This means that any data member which is a list has special methods assigned to it for pushing, popping, and clearing the list.
Understanding Bidirectional Communication
It is also imperative to realize that this package uses interprocess communication methods similar to those used in IPC::Open3 and "Bidirectional Communication with Another Process" in perlipc, and that users of this package need to understand how to use this method because this package does not abstract these methods for the user greatly. This package is not designed to abstract this away entirely (partly for security purposes), but rather to simply help create proper, clean calls to GnuPG, and to implement key-listing parsing. Please see "Bidirectional Communication with Another Process" in perlipc to learn how to deal with these methods.
Using this package to do message processing generally invovlves creating a GnuPG::Interface object, creating a GnuPG::Handles object, setting some options in its options data member, and then calling a method which invokes GnuPG, such as clearsign. One then interacts with with the handles appropriately, as described in "Bidirectional Communication with Another Process" in perlipc.
<<lessSYNOPSIS
# A simple example
use IO::Handle;
use GnuPG::Interface;
# settting up the situation
my $gnupg = GnuPG::Interface->new();
$gnupg->options->hash_init( armor => 1,
homedir => /home/foobar );
# Note you can set the recipients even if you arent encrypting!
$gnupg->options->push_recipients( ftobin@cpan.org );
$gnupg->options->meta_interactive( 0 );
# how we create some handles to interact with GnuPG
my $input = IO::Handle->new();
my $output = IO::Handle->new();
my $handles = GnuPG::Handles->new( stdin => $input,
stdout => $output );
# Now well go about encrypting with the options already set
my @plaintext = ( foobar );
my $pid = $gnupg->encrypt( handles => $handles );
# Now we write to the input of GnuPG
print $input @plaintext;
close $input;
# now we read the output
my @ciphertext = ;
close $output;
waitpid $pid, 0;
GnuPG::Interface and its associated modules are designed to provide an object-oriented method for interacting with GnuPG, being able to perform functions such as but not limited to encrypting, signing, decryption, verification, and key-listing parsing.
How Data Member Accessor Methods are Created
Each module in the GnuPG::Interface bundle relies on Class::MethodMaker to generate the get/set methods used to set the objects data members. This is very important to realize. This means that any data member which is a list has special methods assigned to it for pushing, popping, and clearing the list.
Understanding Bidirectional Communication
It is also imperative to realize that this package uses interprocess communication methods similar to those used in IPC::Open3 and "Bidirectional Communication with Another Process" in perlipc, and that users of this package need to understand how to use this method because this package does not abstract these methods for the user greatly. This package is not designed to abstract this away entirely (partly for security purposes), but rather to simply help create proper, clean calls to GnuPG, and to implement key-listing parsing. Please see "Bidirectional Communication with Another Process" in perlipc to learn how to deal with these methods.
Using this package to do message processing generally invovlves creating a GnuPG::Interface object, creating a GnuPG::Handles object, setting some options in its options data member, and then calling a method which invokes GnuPG, such as clearsign. One then interacts with with the handles appropriately, as described in "Bidirectional Communication with Another Process" in perlipc.
Download (0.037MB)
Added: 2006-08-04 License: Perl Artistic License Price:
1176 downloads
pacgen 1.0
PacGen is an Ethernet IP TCP/UDP packet generating tool for Linux. more>>
PacGen is an Ethernet IP TCP/UDP packet generating tool for Linux. Experimental ARP generation is included. Experimental ARP generation is included. This tool enables custom packets with configurable Ethernet, IP, TCP, and UDP layers as well as custom payloads. As an added feature there are configurations for packet count and a programmable time interval between packet sends. Plaintext config files control all the functions and represent all layers used to build packets. Included in the archive is the source code and a recompiled binary along with example configs.
Since I didnt write a smart interface routine, pacgen will only work with eth0. If you need to use a different interface the source code is pretty obvious on where this would be changed.
<<lessSince I didnt write a smart interface routine, pacgen will only work with eth0. If you need to use a different interface the source code is pretty obvious on where this would be changed.
Download (0.023MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1211 downloads
Noteedit 2.8.1-rc
Noteedit is an editor for music notation that supports an unlimited number of staffs and up to 9 voices per staff. more>>
Noteedit is an editor for music notation that supports an unlimited number of staffs and up to 9 voices per staff.
You can use it to create sheets of notes. With Noteedit you can import and export into many formats like midi, musicxml and lilypond.
Main features:
- Insertion/deletion/modification of notes, rests (and multirests), ties/slurs, stem/beam control, instrument changes, repeats, clef/time/key/volume/tempo and all other classical music notation signatures.
- Chords markings (based on KGuitar project)
- Dynamic expression markings ((de)crescendo, octaviation, arpeggio, fermata, trills, grace notes etc.).
- Fixed expression markings (staccato, sforzato, portato, strong pizzicato, sforzando etc.).
- Multiple voices per staff (polyphony).
- Drum notes (including drum and bass drum clef).
- Flexible UI based on Qt/KDE. Supports zoom, multiple windows, many keyboard shortcuts, Konqueror embedding and other candies.
- Playback and other MIDI operations (reading and recording from MIDI keyboard) are done using TSE3 library. Each staff can have its own channel, own intsrument and own MIDI settings (reverbation, chorus). Currently played element is highlighted!
- Support for lyrics.
- Basic score layout operations (setting brackets, braces, score title, composer, copyright etc.).
- Many useful tools like automatic placment of bars, automatic placement of beams, transposition, copying&pasting of elements, optimization and resetting of accidentals, MIDI importing (or recording from MIDI keyboard) filters etc.
- Exports MIDI (using TSE3 library), MusicXML, ABC Music, PMX, MusiXTeX and LilyPond.
- Imports MIDI and MusicXML.
- The NoteEdit fileformat is similar to the format of the music publication program (MUP). Its a plaintext format, with a simple syntax for describing the music, so computer geeks can edit it by hand if they want to:).
- NoteEdit is translated into the following languages: German, Spanish, French, Hungarian, Italian, Russian, Slovak, Slovene and Swedish. It supports UTF-8 encodings for lyrics, score title, composer, copyright and other document strings.
Enhancements:
Release Candidate of NoteEdit 2.8.1.
The beta version can no longer be downloaded.
Many bugfixes and improvements to the beta version (see ChangeLog for details).
<<lessYou can use it to create sheets of notes. With Noteedit you can import and export into many formats like midi, musicxml and lilypond.
Main features:
- Insertion/deletion/modification of notes, rests (and multirests), ties/slurs, stem/beam control, instrument changes, repeats, clef/time/key/volume/tempo and all other classical music notation signatures.
- Chords markings (based on KGuitar project)
- Dynamic expression markings ((de)crescendo, octaviation, arpeggio, fermata, trills, grace notes etc.).
- Fixed expression markings (staccato, sforzato, portato, strong pizzicato, sforzando etc.).
- Multiple voices per staff (polyphony).
- Drum notes (including drum and bass drum clef).
- Flexible UI based on Qt/KDE. Supports zoom, multiple windows, many keyboard shortcuts, Konqueror embedding and other candies.
- Playback and other MIDI operations (reading and recording from MIDI keyboard) are done using TSE3 library. Each staff can have its own channel, own intsrument and own MIDI settings (reverbation, chorus). Currently played element is highlighted!
- Support for lyrics.
- Basic score layout operations (setting brackets, braces, score title, composer, copyright etc.).
- Many useful tools like automatic placment of bars, automatic placement of beams, transposition, copying&pasting of elements, optimization and resetting of accidentals, MIDI importing (or recording from MIDI keyboard) filters etc.
- Exports MIDI (using TSE3 library), MusicXML, ABC Music, PMX, MusiXTeX and LilyPond.
- Imports MIDI and MusicXML.
- The NoteEdit fileformat is similar to the format of the music publication program (MUP). Its a plaintext format, with a simple syntax for describing the music, so computer geeks can edit it by hand if they want to:).
- NoteEdit is translated into the following languages: German, Spanish, French, Hungarian, Italian, Russian, Slovak, Slovene and Swedish. It supports UTF-8 encodings for lyrics, score title, composer, copyright and other document strings.
Enhancements:
Release Candidate of NoteEdit 2.8.1.
The beta version can no longer be downloaded.
Many bugfixes and improvements to the beta version (see ChangeLog for details).
Download (2.5MB)
Added: 2006-05-28 License: GPL (GNU General Public License) Price:
720 downloads
ClikMenu 0.9
ClikMenu is a library of functions for creating drop-down and popup menus with JavaScript. more>>
ClikMenu project is a library of functions for creating drop-down and popup menus with JavaScript.
Support for multi-level (i.e. cascading or hierarchical) menus is standard, and entries can be URI links, "onmousedown"-type function calls, plaintext labels, or submenus.
ClikMenu is compatible with Firefox, Internet Explorer 6, and other recent browsers. There are no server-side requirements.
<<lessSupport for multi-level (i.e. cascading or hierarchical) menus is standard, and entries can be URI links, "onmousedown"-type function calls, plaintext labels, or submenus.
ClikMenu is compatible with Firefox, Internet Explorer 6, and other recent browsers. There are no server-side requirements.
Download (0.031MB)
Added: 2006-08-15 License: LGPL (GNU Lesser General Public License) Price:
1166 downloads
plconfig 0.2
plconfig is a tool for configuring HomePlug powerline bridges. more>>
plconfig is a tool for configuring HomePlug powerline bridges. HomePlug specification based powerline bridges are becoming increasingly popular. Ive got myself two of them; the brand name is "ZEUS"; a strange brand that only seems to exist in Switzerland, and some people say its actually ZyXEL (have a look at the guts). Whatever, according to the HomePlug alliance homepage (www.homeplug.org), there are only two manufacturers of powerline ICs at the moment: Intellon and Cogency Semiconductor. My bridges have the Intellon chipset (INT5130 integrated powerline MAC-PHY transceiver and INT1000 analog conversion IC). Intellon calls their implementation "PowerPacket".
Now, about the only thing that has to be configured with these is the encryption password, so your neighbor wont be able to sniff your data. A Windows program is provided for that purpose - you hook up the bridge directly to your PC, enter a 2-24 character password, and the password is saved into the bridges EEPROM.
This is a bit of an inconvenience to non-Windows users, and even if you keep Windows boxes around, at least to me the software looks ugly. It keeps running strange daemons (WinPlcMan.exe, BridgeDeCor.exe, etc.) that use up to 100% CPU at times, and sometimes its not possible to set the password without power cycling the bridge first (although that seems to be the fault of the bridge).
So I made an attempt at writing a program to set up the encryption key. I found some inofficial information on the web, and it agreed with what I learned from sniffing the communication between the PowerPacket setup software and the bridge.
Im making the program available here for you to try; its status is currently somewhere in between an ugly hack and a simple use-once-and-throw-away tool. I have no idea if it works with other powerline bridges; although it should work with all Intellon-based ones. If youve had success with a particular product, please let me know!
Besides setting the encryption key, it can also capture and display powerline bridge management-related packets and request statistics from the bridge(s).
Enhancements:
- plaintext passwords are now hashed correctly as per the HomePlug specification (no longer homebrew MD5); as such passwords should now be compatible with the Windows setup software supplied by Intellon (note that -s does no longer set up the same key as in 0.1! Of course -s 0x behaves as before...)
<<lessNow, about the only thing that has to be configured with these is the encryption password, so your neighbor wont be able to sniff your data. A Windows program is provided for that purpose - you hook up the bridge directly to your PC, enter a 2-24 character password, and the password is saved into the bridges EEPROM.
This is a bit of an inconvenience to non-Windows users, and even if you keep Windows boxes around, at least to me the software looks ugly. It keeps running strange daemons (WinPlcMan.exe, BridgeDeCor.exe, etc.) that use up to 100% CPU at times, and sometimes its not possible to set the password without power cycling the bridge first (although that seems to be the fault of the bridge).
So I made an attempt at writing a program to set up the encryption key. I found some inofficial information on the web, and it agreed with what I learned from sniffing the communication between the PowerPacket setup software and the bridge.
Im making the program available here for you to try; its status is currently somewhere in between an ugly hack and a simple use-once-and-throw-away tool. I have no idea if it works with other powerline bridges; although it should work with all Intellon-based ones. If youve had success with a particular product, please let me know!
Besides setting the encryption key, it can also capture and display powerline bridge management-related packets and request statistics from the bridge(s).
Enhancements:
- plaintext passwords are now hashed correctly as per the HomePlug specification (no longer homebrew MD5); as such passwords should now be compatible with the Windows setup software supplied by Intellon (note that -s does no longer set up the same key as in 0.1! Of course -s 0x behaves as before...)
Download (0.008MB)
Added: 2006-07-03 License: GPL (GNU General Public License) Price:
699 downloads
blinkperl 2003-03-02
blinkperl provides a telnet server which plays a blinkenlights movie. more>>
blinkperl provides a telnet server which plays a blinkenlights movie.
blinkperl is a telnet server (written in Perl) which plays a random (ASCII-Art) Blinkenlights-Movie if a telnet client connects.
In a properly configured system, you do not need a usual telnet server (because of the plaintext password transmission, ssh is better and uses another port), so why not play ASCII-Art Movies on the telnet port?
<<lessblinkperl is a telnet server (written in Perl) which plays a random (ASCII-Art) Blinkenlights-Movie if a telnet client connects.
In a properly configured system, you do not need a usual telnet server (because of the plaintext password transmission, ssh is better and uses another port), so why not play ASCII-Art Movies on the telnet port?
Download (0.066MB)
Added: 2007-03-27 License: Academic Free License (AFL) Price:
944 downloads
Crypt::UnixCrypt 1.0
Crypt::UnixCrypt is a perl-only implementation of the crypt function. more>>
Crypt::UnixCrypt is a perl-only implementation of the crypt function.
SYNOPSIS
use Crypt::UnixCrypt;
$hashed = crypt($plaintext,$salt);
# always use this modules crypt
BEGIN { $Crypt::UnixCrpyt::OVERRIDE_BUILTIN = 1 }
use Crypt::UnixCrypt;
This module is for all those poor souls whose perl port answers to the use of crypt() with the message `The crypt() function is unimplemented due to excessive paranoia..
This module wont overload a built-in crypt() unless forced by a true value of the variable $Crypt::UnixCrypt::OVERRIDE_BUILTIN.
If you use this module, you probably neither have a built-in crypt() function nor a crypt(3) manpage; so Ill supply the appropriate portions of its description (from my Linux system) here:
crypt is the password encryption function. It is based on the Data Encryption Standard algorithm with variations intended (among other things) to discourage use of hardware implementations of a key search.
$plaintext is a users typed password.
$salt is a two-character string chosen from the set [a-zA-Z0-9./]. This string is used to perturb the algorithm in one of 4096 different ways.
By taking the lowest 7 bit of each character of $plaintext (filling it up to 8 characters with zeros, if needed), a 56-bit key is obtained. This 56-bit key is used to encrypt repeatedly a constant string (usually a string consisting of all zeros). The returned value points to the encrypted password, a series of 13 printable ASCII characters (the first two characters represent the salt itself).
Warning: The key space consists of 2**56 equal 7.2e16 possible values. Exhaustive searches of this key space are possible using massively parallel computers. Software, such as crack(1), is available which will search the portion of this key space that is generally used by humans for passwords. Hence, password selection should, at minimum, avoid common words and names. The use of a passwd(1) program that checks for crackable passwords during the selection process is recommended.
The DES algorithm itself has a few quirks which make the use of the crypt(3) interface a very poor choice for anything other than password authentication. If you are planning on using the crypt(3) interface for a cryptography project, dont do it: get a good book on encryption and one of the widely available DES libraries.
<<lessSYNOPSIS
use Crypt::UnixCrypt;
$hashed = crypt($plaintext,$salt);
# always use this modules crypt
BEGIN { $Crypt::UnixCrpyt::OVERRIDE_BUILTIN = 1 }
use Crypt::UnixCrypt;
This module is for all those poor souls whose perl port answers to the use of crypt() with the message `The crypt() function is unimplemented due to excessive paranoia..
This module wont overload a built-in crypt() unless forced by a true value of the variable $Crypt::UnixCrypt::OVERRIDE_BUILTIN.
If you use this module, you probably neither have a built-in crypt() function nor a crypt(3) manpage; so Ill supply the appropriate portions of its description (from my Linux system) here:
crypt is the password encryption function. It is based on the Data Encryption Standard algorithm with variations intended (among other things) to discourage use of hardware implementations of a key search.
$plaintext is a users typed password.
$salt is a two-character string chosen from the set [a-zA-Z0-9./]. This string is used to perturb the algorithm in one of 4096 different ways.
By taking the lowest 7 bit of each character of $plaintext (filling it up to 8 characters with zeros, if needed), a 56-bit key is obtained. This 56-bit key is used to encrypt repeatedly a constant string (usually a string consisting of all zeros). The returned value points to the encrypted password, a series of 13 printable ASCII characters (the first two characters represent the salt itself).
Warning: The key space consists of 2**56 equal 7.2e16 possible values. Exhaustive searches of this key space are possible using massively parallel computers. Software, such as crack(1), is available which will search the portion of this key space that is generally used by humans for passwords. Hence, password selection should, at minimum, avoid common words and names. The use of a passwd(1) program that checks for crackable passwords during the selection process is recommended.
The DES algorithm itself has a few quirks which make the use of the crypt(3) interface a very poor choice for anything other than password authentication. If you are planning on using the crypt(3) interface for a cryptography project, dont do it: get a good book on encryption and one of the widely available DES libraries.
Download (0.008MB)
Added: 2007-06-19 License: Perl Artistic License Price:
857 downloads
Data::Encrypted 0.07
Data::Encrypted is a Perl module to transparently store encrypted data via RSA. more>>
Data::Encrypted is a Perl module to transparently store encrypted data via RSA.
SYNOPSIS
# functional interface:
use Data::Encrypted file => "./.$0-encrypted-data", qw(encrypted);
# note: login and password are not *really* the login and
# password values, only the desired prompt!
my $login = encrypted(login);
my $password = encrypted(password);
# script continues, connecting to some secure resource (database,
# website, etc).
__END__
# alternative, OO interface:
use Data::Encrypted;
my $enc = new Data::Encrypted file => "./.$0-encrypted-data";
my $login = $enc->encrypted(login);
my $password = $enc->encrypted(password);
$enc->finished(); # close and release lock on storage file
# script continues, connecting to some secure resource (database,
# website, etc).
__END__
[ then, back at the command line: ]
% myscript.pl
Data::Encrypted value for login not found, please enter: *****
Data::Encrypted value for password not found, please enter: ********
[ script merrily continues ... ]
% myscript.pl
[ script merrily continues, no prompting this time ... ]
Often when dealing with external resources (database engines, ftp, telnet, websites, etc), your Perl script must supply a password, or other sensitive data, to the other system. This requires you to either continually prompt the user for the data, or to store the information (in plaintext) within your script. Youd rather not have to remember the connection details to all your different resources, so youd like to store the data somewhere. And if you share your script with anyone (as any good open-source developer would), youd rather not have your password or other sensitive information floating around.
Data::Encrypted attempts to fill this small void with a simple, yet functional solution to this common predicament. It works by prompting you (via Term::ReadPassword) once for each required value, but only does so the first time you run your script; thereafter, the data is stored encrypted in a secondary file. Subsequent executions of your script use the encrypted data directly, if possible; otherwise it again prompts for the data. Currently, Data::Encrypted achieves encryption via an RSA public-key cryptosystem implemented by Crypt::RSA, using (by default) your own SSH1 public and private keys.
<<lessSYNOPSIS
# functional interface:
use Data::Encrypted file => "./.$0-encrypted-data", qw(encrypted);
# note: login and password are not *really* the login and
# password values, only the desired prompt!
my $login = encrypted(login);
my $password = encrypted(password);
# script continues, connecting to some secure resource (database,
# website, etc).
__END__
# alternative, OO interface:
use Data::Encrypted;
my $enc = new Data::Encrypted file => "./.$0-encrypted-data";
my $login = $enc->encrypted(login);
my $password = $enc->encrypted(password);
$enc->finished(); # close and release lock on storage file
# script continues, connecting to some secure resource (database,
# website, etc).
__END__
[ then, back at the command line: ]
% myscript.pl
Data::Encrypted value for login not found, please enter: *****
Data::Encrypted value for password not found, please enter: ********
[ script merrily continues ... ]
% myscript.pl
[ script merrily continues, no prompting this time ... ]
Often when dealing with external resources (database engines, ftp, telnet, websites, etc), your Perl script must supply a password, or other sensitive data, to the other system. This requires you to either continually prompt the user for the data, or to store the information (in plaintext) within your script. Youd rather not have to remember the connection details to all your different resources, so youd like to store the data somewhere. And if you share your script with anyone (as any good open-source developer would), youd rather not have your password or other sensitive information floating around.
Data::Encrypted attempts to fill this small void with a simple, yet functional solution to this common predicament. It works by prompting you (via Term::ReadPassword) once for each required value, but only does so the first time you run your script; thereafter, the data is stored encrypted in a secondary file. Subsequent executions of your script use the encrypted data directly, if possible; otherwise it again prompts for the data. Currently, Data::Encrypted achieves encryption via an RSA public-key cryptosystem implemented by Crypt::RSA, using (by default) your own SSH1 public and private keys.
Download (0.007MB)
Added: 2006-10-04 License: Perl Artistic License Price:
1117 downloads
localscan 2.1
localscan is a frontend to nmap. more>>
localscan is a frontend to nmap. The purpose of localscan is to make the lives of administrators easier. At its heart, localscan is simply a list of "ignore this host/port combo" rules designed to reduce the amount of useless information returned by nmap scans of a given subnet.
I administer a largish lab at a largish higher educational institution (which shall remain unnamed!), and about three months ago I found it necessary to start running a portscanner against my subnet every so often. Now, while it was relatively easy to cobble something together that would do this and mail the results of the scan to me, I found that my inbox was being filled with inanity. Lots of valid services were present, and the few invalid services were hard to pick out. So I put together a quick-and-dirty filter and released it internally as local_scan 1.0a. Not surprisingly, no one used it. This is because I was (am!) still learning Perl.
After the initial disappointment, I sat down and started rewriting, with the end result being what you just downloaded. :) Localscan 2.0 is much easier for the non-Perl person (yes, there are a few of them out there) to use. All the "interesting" user-configurable parameters are now contained in a plaintext external datafile called localscan.conf.
You should have received four files in this tarball.
This readme file
A "quickstart" guide
Localscan.pl, the actual script
Make_conf.pl, a script to generate the localscan.conf file
<<lessI administer a largish lab at a largish higher educational institution (which shall remain unnamed!), and about three months ago I found it necessary to start running a portscanner against my subnet every so often. Now, while it was relatively easy to cobble something together that would do this and mail the results of the scan to me, I found that my inbox was being filled with inanity. Lots of valid services were present, and the few invalid services were hard to pick out. So I put together a quick-and-dirty filter and released it internally as local_scan 1.0a. Not surprisingly, no one used it. This is because I was (am!) still learning Perl.
After the initial disappointment, I sat down and started rewriting, with the end result being what you just downloaded. :) Localscan 2.0 is much easier for the non-Perl person (yes, there are a few of them out there) to use. All the "interesting" user-configurable parameters are now contained in a plaintext external datafile called localscan.conf.
You should have received four files in this tarball.
This readme file
A "quickstart" guide
Localscan.pl, the actual script
Make_conf.pl, a script to generate the localscan.conf file
Download (0.009MB)
Added: 2006-07-13 License: GPL (GNU General Public License) Price:
1204 downloads
XML::TMX::Writer 0.16
XML::TMX::Writer is a Perl extension for writing TMX files. more>>
XML::TMX::Writer is a Perl extension for writing TMX files.
SYNOPSIS
use XML::TMX::Writer;
my $tmx = new XML::TMX::Writer();
$tmx->start_tmx(ID => paulojjs);
$tmx->add_tu(SRCLANG => en, en => some text, pt => algum texto);
$tmx->add_tu(SRCLANG => en,
en => some text,
pt => algum texto,
-note => [32, 34 ],
-prop => { q => 23,
aut => "jj"}
);
$tmx->end_tmx();
This module provides a simple way for writing TMX files.
METHODS
The following methods are available:
new
$tmx = new XML::TMX::Writer();
Creates a new XML::TMX::Writer object
start_tmx
$tmx->start_tmx(OUTPUT => some_file.tmx);
Begins a TMX file. Several options are available:
OUTPUT
Output of the TMX, if none is defined stdout is used by default.
TOOL
Tool used to create the TMX. Defaults to XML::TMX::Writer
TOOLVERSION
Some version identification of the tool used to create the TMX. Defaults to the current module version
SEGTYPE
Segment type used in the < tu > elements. Possible values are block, paragraph, sentence and phrase. Defaults to sentence.
SRCTMF
Specifies the format of the translation memory file from which the TMX document or segment thereof have been generated.
ADMINLANG
Specifies the default language for the administrative and informative elements < note > and < prop >.
SRCLANG
Specifies the language of the source text. If a element does not have a srclang attribute specified, it uses the one defined in the element. Defaults to *all*.
DATATYPE
Specifies the type of data contained in the element. Depending on that type, you may apply different processes to the data.
The recommended values for the datatype attribute are as follow (this list is not exhaustive):
unknown
undefined
alptext
WinJoust data
cdf
Channel Definition Format
cmx
Corel CMX Format
cpp
C and C++ style text
hptag
HP-Tag
html
HTML, DHTML, etc
interleaf
Interleaf documents
ipf
IPF/BookMaster
java
Java, source and property files
javascript
JavaScript, ECMAScript scripts
lisp
Lisp
mif
Framemaker MIF, MML, etc
opentag
OpenTag data
pascal
Pascal, Delphi style text
plaintext
Plain text (default)
pm
PageMaker
rtf
Rich Text Format =item sgml
SGML
stf-f
S-Tagger for FrameMaker
stf-i
S-Tagger for Interleaf
transit
Transit data
vbscript
Visual Basic scripts
winres
Windows resources from RC, DLL, EXE
xml
XML
xptag
Quark XPressTag
SRCENCODING
All TMX documents are in Unicode. However, it is sometimes useful to know what code set was used to encode text that was converted to Unicode for purposes of interchange. This option specifies the original or preferred code set of the data of the element in case it is to be re-encoded in a non-Unicode code set. Defaults to none.
ID
Specifies the identifier of the user who created the element. Defaults to none.
<<lessSYNOPSIS
use XML::TMX::Writer;
my $tmx = new XML::TMX::Writer();
$tmx->start_tmx(ID => paulojjs);
$tmx->add_tu(SRCLANG => en, en => some text, pt => algum texto);
$tmx->add_tu(SRCLANG => en,
en => some text,
pt => algum texto,
-note => [32, 34 ],
-prop => { q => 23,
aut => "jj"}
);
$tmx->end_tmx();
This module provides a simple way for writing TMX files.
METHODS
The following methods are available:
new
$tmx = new XML::TMX::Writer();
Creates a new XML::TMX::Writer object
start_tmx
$tmx->start_tmx(OUTPUT => some_file.tmx);
Begins a TMX file. Several options are available:
OUTPUT
Output of the TMX, if none is defined stdout is used by default.
TOOL
Tool used to create the TMX. Defaults to XML::TMX::Writer
TOOLVERSION
Some version identification of the tool used to create the TMX. Defaults to the current module version
SEGTYPE
Segment type used in the < tu > elements. Possible values are block, paragraph, sentence and phrase. Defaults to sentence.
SRCTMF
Specifies the format of the translation memory file from which the TMX document or segment thereof have been generated.
ADMINLANG
Specifies the default language for the administrative and informative elements < note > and < prop >.
SRCLANG
Specifies the language of the source text. If a element does not have a srclang attribute specified, it uses the one defined in the element. Defaults to *all*.
DATATYPE
Specifies the type of data contained in the element. Depending on that type, you may apply different processes to the data.
The recommended values for the datatype attribute are as follow (this list is not exhaustive):
unknown
undefined
alptext
WinJoust data
cdf
Channel Definition Format
cmx
Corel CMX Format
cpp
C and C++ style text
hptag
HP-Tag
html
HTML, DHTML, etc
interleaf
Interleaf documents
ipf
IPF/BookMaster
java
Java, source and property files
javascript
JavaScript, ECMAScript scripts
lisp
Lisp
mif
Framemaker MIF, MML, etc
opentag
OpenTag data
pascal
Pascal, Delphi style text
plaintext
Plain text (default)
pm
PageMaker
rtf
Rich Text Format =item sgml
SGML
stf-f
S-Tagger for FrameMaker
stf-i
S-Tagger for Interleaf
transit
Transit data
vbscript
Visual Basic scripts
winres
Windows resources from RC, DLL, EXE
xml
XML
xptag
Quark XPressTag
SRCENCODING
All TMX documents are in Unicode. However, it is sometimes useful to know what code set was used to encode text that was converted to Unicode for purposes of interchange. This option specifies the original or preferred code set of the data of the element in case it is to be re-encoded in a non-Unicode code set. Defaults to none.
ID
Specifies the identifier of the user who created the element. Defaults to none.
Download (0.015MB)
Added: 2007-05-31 License: Perl Artistic License Price:
878 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above plaintext 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
