Net::ParseWhois

2001-03-31 Thread Abraham Ingersoll


Hello,

I've created (and finally uploaded) Net::ParseWhois. It's a logical update
of Net::Whois that adds support for whois referrals. For background,
please see any of the following:

http://perlmonks.org/index.pl?node_id=44070&lastnode_id=44898
http://perlmonks.org/index.pl?node_id=44898&lastnode_id=864
http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-11/msg00179.html

Please add Net::ParseWhois to the official module list, or let me know
what remains to be done before that can happen.

Thanks!
Abe





File::Canon.pm

2001-03-31 Thread Jerry Eubanks

I have a perl file that is trying to use File::Canon.pm.

I have not been able to find this file anywhere in perl/CPAN.

use File::Canon; # Dirname manipulation


Can you help me on this?


This what I have in the script.

# Standard modules
use Getopt::Long (); # "Long" command line option parsing
routines
use File::Basename;  # Basename of file(s)
use FindBin qw($RealBin);# Find real location of the script

# Custom modules
use lib "$RealBin/../lib/perl";  # Custom modules location
 $RealBin is in FindBin.pm
use Devel::Debug;# Integrated debug routines
use Devel::Usage;# Program usage logging
use Net::FTP;# File Transfer Protocol support
use File::Canon; # Dirname manipulation


Thank you,

Jerry Eubanks

[EMAIL PROTECTED]




[RFC2410] Crypt::NULL

2001-03-31 Thread Abhijit Menon-Sen

I'd like to upload Crypt::NULL (README appended), a module implementing
NULL encryption as described in RFC 2410, to the CPAN. Please suggest an
alternative name is Crypt::NULL is unsuitable.

  modid:   Crypt::NULL
  DSLI:RdpO
  description: NULL Encryption Algorithm
  userid:  AMS (Abhijit Menon-Sen)
  chapterid:   14 (Security_and_Encryption)

- ams

NAME
Crypt::NULL - NULL Encryption Algorithm

SYNOPSIS
use Crypt::NULL;

$null = Crypt::NULL->new($key);

$ciphertext = $null->encrypt($plaintext);

$plaintext = $null->decrypt($ciphertext);

DESCRIPTION
The NULL Encryption Algorithm is a symmetric block cipher described
in RFC 2410 by Rob Glenn and Stephen Kent.

This module implements NULL encryption. It supports the Crypt::CBC
interface, with the following functions.

  Functions

blocksize
Returns the size (in bytes) of the block (16, in this case).

keysize
Returns the size (in bytes) of the key (16, in this case).

new($key, $rounds)
This creates a new Crypt::NULL object with the specified key.

encrypt($data)
Encrypts blocksize() bytes of $data and returns the
corresponding ciphertext.

decrypt($data)
Decrypts blocksize() bytes of $data and returns the
corresponding plaintext.

SEE ALSO
Crypt::CBC, Crypt::TEA, Crypt::Blowfish

AUTHOR
Abhijit Menon-Sen <[EMAIL PROTECTED]>

Copyright 2001 Abhijit Menon-Sen. All rights reserved.

This is free software; you may redistribute and/or modify it
under the same terms as Perl itself.



Set::Crontab

2001-03-31 Thread Abhijit Menon-Sen

The Set::Crontab module is on the CPAN, but is not in the module list.
Could somebody please add it?

  modid:   Set::Crontab
  DSLI:bdph
  description: Expand crontab(5)-style integer lists
  userid:  AMS (Abhijit Menon-Sen)

- ams



new module: ExtUtils::FakeConfig

2001-03-31 Thread Mattia Barbon

  This module is meant to be used at Makefile.PL time
( so I think it belongs to ExtUtils ); it makes easy to
override values in %Config; basically you
create a module like this:

package Foo;

use ExtUtils::FakeConfig
  cc => 'my_cc', cflags => 'funny flags';

1;

and do
perl -MFoo Makefile.PL

  I use it to compile ActivePerl modules with MinGW,
but it has many other uses, especially if you want to
compile modules with a different cc your Perl was compiled
with.
  I don't plan to put it in CPAN ( yet ), just want comments
about the name.

Regards
Mattia



Renaming Net::SNMP::Interfaces

2001-03-31 Thread Jonathan Stowe

Hi,
I'd like to kick off a discussion of what the above module should be
renamed to :) In my earlier discussion with David we had decided that it
probably should be something like SNMP::NetSNMP::ifTable which naturally
suggested itself because it used Net::SNMP and it was felt that leaving it
under Net::SNMP interfered somewhat with David's ability to add new things
in that namespace.

Now however I have concluded that the next release of the module will have
the capability of using either Net::SNMP or SNMP at the users request (or
whichever one is available ) and that has somewhat complicated the naming
in my mind as SNMP::NetSNMP would imply something that would no longer be
true.

Of course I could shift the proposed name up to be SNMP::IfTable but that
might interfere with someone elses plans and none of the existing
sub-namespaces seem to fit the bill.

Any suggestions gratefully received :)

/J\