Why not adopt me?

This distribution is up for adoption! If you're interested then please contact the PAUSE module admins via email.

NAME

POE::Component::IRC::Plugin::Data::SimplePassword - plugin for generating passwords on IRC

SYNOPSIS

use strict;
use warnings;

use POE qw(Component::IRC  Component::IRC::Plugin::Data::SimplePassword);

my $irc = POE::Component::IRC->spawn(
    nick        => 'PassBot',
    server      => 'irc.freenode.net',
    port        => 6667,
    ircname     => 'PassBot',
);

POE::Session->create(
    package_states => [
        main => [ qw(_start irc_001) ],
    ],
);

$poe_kernel->run;

sub _start {
    $irc->yield( register => 'all' );

    $irc->plugin_add(
        'PassBot' =>
            POE::Component::IRC::Plugin::Data::SimplePassword->new
    );

    $irc->yield( connect => {} );
}

sub irc_001 {
    $_[KERNEL]->post( $_[SENDER] => join => '#zofbot' );
}


<Zoffix> PassBot, pass
<PassBot> Zoffix, %FNZc5t{Sb

<Zoffix> PassBot, pass 100
<PassBot> Zoffix, qxopdfN&&U}FG/s."5]1)]M,M(0vGEzD1_Cx8IB*.tC(F'OGcRxaHCZ5wp\
                    1*m+PGR(HcZG"'NKoEKCAbnd+'/N^/+5G{gIf9|g^

DESCRIPTION

This module is a POE::Component::IRC plugin which uses POE::Component::IRC::Plugin for its base. It provides interface to to generate random passwords on IRC. It accepts input from public channel events, /notice messages as well as /msg (private messages); although that can be configured at will.

IRC USAGE

Providing the plugin run with all of its defaults, you have two modes:

<Zoffix> PassBot, pass
<PassBot> Zoffix, %FNZc5t{Sb

<Zoffix> PassBot, pass 100
<PassBot> Zoffix, qxopdfN&&U}FG/s."5]1)]M,M(0vGEzD1_Cx8IB*.tC(F'OGcRxaHCZ5wp\
                    1*m+PGR(HcZG"'NKoEKCAbnd+'/N^/+5G{gIf9|g^

That is, any digits that are left after stripping the trigger will be regarded as the length of the password to make. See trigger and default_length constructor arguments for details.

CONSTRUCTOR

`new`

# plain and simple
$irc->plugin_add(
    'PassGen' => POE::Component::IRC::Plugin::Data::SimplePassword->new
);

# juicy flavor
$irc->plugin_add(
    'PassGen' =>
        POE::Component::IRC::Plugin::Data::SimplePassword->new(
            auto             => 1,
            chars            => [ grep /[[:graph:]]/, map chr, 0..127 ],
            default_length   => 10,
            response_event   => 'irc_data_pass',
            banned           => [ qr/aol\.com$/i ],
            addressed        => 1,
            root             => [ qr/mah.net$/i ],
            trigger          => qr/^pass\s*/i,
            triggers         => {
                public  => qr/^pass\s*/i,
                notice  => qr/^pass\s*/i,
                privmsg => qr/^pass\s*/i,
            },
            listen_for_input => [ qw(public notice privmsg) ],
            eat              => 1,
            debug            => 0,
        )
);

The new() method constructs and returns a new POE::Component::IRC::Plugin::Data::SimplePassword object suitable to be fed to POE::Component::IRC's plugin_add method. The constructor takes a few arguments, but all of them are optional. The possible arguments/values are as follows:

`auto`

->new( auto => 0 );

Optional. Takes either true or false values, specifies whether or not the plugin should auto respond to requests. When the auto argument is set to a true value plugin will respond to the requesting person with the results automatically. When the auto argument is set to a false value plugin will not respond and you will have to listen to the events emited by the plugin to retrieve the results (see EMITED EVENTS section and response_event argument for details). Defaults to: 1.

`chars`

->new( chars => [ grep /[[:graph:]]/, map chr, 0..127 ], )

Optional. Takes an arrayref of characters to be used for generating passwords. Defaults to: [ grep /[[:graph:]]/, map chr, 0..127 ]

`default_length`

->new( default_length => 10, )

Optional. The plugin can be triggered from IRC without the length argument (see IRC USAGE section above). If that's the case than the length of the password to generate will be taken from default_length argument. Defaults to: 10

`response_event`

->new( response_event => 'event_name_to_recieve_results' );

Optional. Takes a scalar string specifying the name of the event to emit when the results of the request are ready. See EMITED EVENTS section for more information. Defaults to: irc_data_pass

`banned`

->new( banned => [ qr/aol\.com$/i ] );

Optional. Takes an arrayref of regexes as a value. If the usermask of the person (or thing) making the request matches any of the regexes listed in the banned arrayref, plugin will ignore the request. Defaults to: [] (no bans are set).

`root`

->new( root => [ qr/\Qjust.me.and.my.friend.net\E$/i ] );

Optional. As opposed to banned argument, the root argument allows access only to people whose usermasks match any of the regexen you specify in the arrayref the argument takes as a value. By default: it is not specified. Note: as opposed to banned specifying an empty arrayref to root argument will restrict access to everyone.

`trigger`

->new( trigger => qr/^pass\s*/i );

Optional. Takes a regex as an argument. Messages matching this regex, irrelevant of the type of the message, will be considered as requests. See also addressed option below which is enabled by default as well as trigggers option which is more specific. Note: the trigger will be removed from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. Defaults to: qr/^pass\s*/i

`triggers`

->new( triggers => {
        public  => qr/^pass\s*/i,
        notice  => qr/^pass\s*/i,
        privmsg => qr/^pass\s*/i,
    }
);

Optional. Takes a hashref as an argument which may contain either one or all of keys public, notice and privmsg which indicates the type of messages: channel messages, notices and private messages respectively. The values of those keys are regexes of the same format and meaning as for the trigger argument (see above). Messages matching this regex will be considered as requests. The difference is that only messages of type corresponding to the key of triggers hashref are checked for the trigger. Note: the trigger will be matched irrelevant of the setting in triggers, thus you can have one global and specific "local" triggers. See also addressed option below which is enabled by default as well as trigggers option which is more specific. Note: the trigger will be removed from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. Defaults to: qr/^pass\s*/i

`addressed`

->new( addressed => 1 );

Optional. Takes either true or false values. When set to a true value all the public messages must be addressed to the bot. In other words, if your bot's nickname is Nick and your trigger is qr/^trig\s+/ you would make the request by saying Nick, trig EXAMPLE. When addressed mode is turned on, the bot's nickname, including any whitespace and common punctuation character will be removed before matching the trigger (see above). When addressed argument it set to a false value, public messages will only have to match trigger regex in order to make a request. Note: this argument has no effect on /notice and /msg requests. Defaults to: 1

`listen_for_input`

->new( listen_for_input => [ qw(public  notice  privmsg) ] );

Optional. Takes an arrayref as a value which can contain any of the three elements, namely public, notice and privmsg which indicate which kind of input plugin should respond to. When the arrayref contains public element, plugin will respond to requests sent from messages in public channels (see addressed argument above for specifics). When the arrayref contains notice element plugin will respond to requests sent to it via /notice messages. When the arrayref contains privmsg element, the plugin will respond to requests sent to it via /msg (private messages). You can specify any of these. In other words, setting ( listen_for_input = [ qr(notice privmsg) ] )> will enable functionality only via /notice and /msg messages. Defaults to: [ qw(public notice privmsg) ]

`eat`

->new( eat => 0 );

Optional. If set to a false value plugin will return a PCI_EAT_NONE after responding. If eat is set to a true value, plugin will return a PCI_EAT_ALL after responding. See POE::Component::IRC::Plugin documentation for more information if you are interested. Defaults to: 1

`debug`

->new( debug => 1 );

Optional. Takes either a true or false value. When debug argument is set to a true value some debugging information will be printed out. When debug argument is set to a false value no debug info will be printed. Defaults to: 0.

EMITED EVENTS

`response_event`

$VAR1 = {
    'out' => 'Y`cP#i-XO].7KIL_V{@Q;~OcHkA0D7-RxIQOSb=ah:,fmr^BW!Z@Gq;kzIug*ko?~2u5<1[A=&f]*^.]-{J/d?i#j$_lanynMNq_',
    'pass' => 'Zoffix, Y`cP#i-XO].7KIL_V{@Q;~OcHkA0D7-RxIQOSb=ah:,fmr^BW!Z@Gq;kzIug*ko?~2u5<1[A=&f]*^.]-{J/d?i#j$_lanynMNq_',
    'length' => '100',
    'chars' => [ '!', '"', '#', .... ] # shortened for brevity
    '_channel' => '#zofbot',
    '_type' => 'public',
    '_who' => 'Zoffix!n=Zoffix@unaffiliated/zoffix',
    '_message' => 'PassBot, pass 100',
};

The event handler set up to handle the event, name of which you've specified in the response_event argument to the constructor (it defaults to irc_data_pass) will recieve input every time request is completed. The input will come in $_[ARG0] on a form of a hashref. The possible keys/values of that hashrefs are as follows:

`out`

{ 'out' => 'Y`cP#i-XO].7KIL_V{@Q;~OcHkA0D7-RxIQOSb=ah:,fmr^BW!Z@Gq;kzIug*ko?~2u5<1[A=&f]*^.]-{J/d?i#j$_lanynMNq_', }

The out key will contain the password that was generated.

`pass`

{ 'pass' => 'Zoffix, Y`cP#i-XO].7KIL_V{@Q;~OcHkA0D7-RxIQOSb=ah:,fmr^BW!Z@Gq;kzIug*ko?~2u5<1[A=&f]*^.]-{J/d?i#j$_lanynMNq_', }

The pass key will contain whatever would be spoken to IRC when auto argument (see CONSTRUCTOR) is set to a true value; generally this will me the same as out unless the plugin was triggered in a public channel.

`length`

{ 'length' => '100', }

The length key will contain the length of the generated password.

`chars`

{ 'chars' => [ '!', '"', '#', .... ], } # shortened for brevity

The chars key will contain an arrayref of characters that were used to generate the password.

`_who`

{ '_who' => 'Zoffix!n=Zoffix@unaffiliated/zoffix', }

The _who key will contain the user mask of the user who sent the request.

`_message`

{ '_message' => 'PassBot, pass 100', }

The _message key will contain the actual message which the user sent; that is before the trigger is stripped.

`_type`

{ '_type' => 'public', }

The _type key will contain the "type" of the message the user have sent. This will be either public, privmsg or notice.

`_channel`

{ '_channel' => '#zofbot', }

The _channel key will contain the name of the channel where the message originated. This will only make sense if _type key contains public.

AUTHOR

'Zoffix, <'zoffix at cpan.org'> (http://zoffix.com/, http://haslayout.net/, http://zofdesign.com/)

BUGS

Please report any bugs or feature requests to bug-poe-component-irc-plugin-data-simplepassword at rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=POE-Component-IRC-Plugin-Data-SimplePassword. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.

SUPPORT

You can find documentation for this module with the perldoc command.

perldoc POE::Component::IRC::Plugin::Data::SimplePassword

You can also look for information at:

RT: CPAN's request tracker

http://rt.cpan.org/NoAuth/Bugs.html?Dist=POE-Component-IRC-Plugin-Data-SimplePassword
AnnoCPAN: Annotated CPAN documentation

http://annocpan.org/dist/POE-Component-IRC-Plugin-Data-SimplePassword
CPAN Ratings

http://cpanratings.perl.org/d/POE-Component-IRC-Plugin-Data-SimplePassword
Search CPAN

http://search.cpan.org/dist/POE-Component-IRC-Plugin-Data-SimplePassword

COPYRIGHT & LICENSE

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

To install POE::Component::IRC::Plugin::Data::SimplePassword, copy and paste the appropriate command in to your terminal.

cpanm

cpanm POE::Component::IRC::Plugin::Data::SimplePassword

CPAN shell

perl -MCPAN -e shell
install POE::Component::IRC::Plugin::Data::SimplePassword

For more information on module installation, please visit the detailed CPAN module installation guide.

	Global
`s`	Focus search bar
`?`	Bring up this help dialog

	GitHub
`g` `p`	Go to pull requests
`g` `i`	go to github issues (only if github is preferred repository)

	POD
`g` `a`	Go to author
`g` `c`	Go to changes
`g` `i`	Go to issues
`g` `d`	Go to dist
`g` `r`	Go to repository/SCM
`g` `s`	Go to source
`g` `b`	Go to file browse

	Search terms
module: (e.g. module:Plugin)
distribution: (e.g. distribution:Dancer auth)
author: (e.g. author:SONGMU Redis)
version: (e.g. version:1.00)

Why not adopt me?

NAME

SYNOPSIS

DESCRIPTION

IRC USAGE

CONSTRUCTOR

new

auto

chars

default_length

response_event

banned

root

trigger

triggers

addressed

listen_for_input

eat

debug

EMITED EVENTS

response_event

out

pass

length

chars

_who

_message

_type

_channel

AUTHOR

BUGS

SUPPORT

COPYRIGHT & LICENSE

Module Install Instructions

`new`

`auto`

`chars`

`default_length`

`response_event`

`banned`

`root`

`trigger`

`triggers`

`addressed`

`listen_for_input`

`eat`

`debug`

`response_event`

`out`

`pass`

`length`

`chars`

`_who`

`_message`

`_type`

`_channel`