view release on metacpan or search on metacpan
lib/App/PAIA/Agent.pm view on Meta::CPAN
my ($class, %options) = @_;
bless {
insecure => !!$options{insecure},
logger => $options{logger},
dumper => $options{dumper},
agent => HTTP::Tiny->new( verify_SSL => (!$options{insecure}) ),
}, $class;
}
sub request {
my $self = shift;
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.79.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
bin/pft-grab view on Meta::CPAN
=item B<--picture> | B<-p>
Store the files into the C<I<ROOT>/content/pics> directory and output the
Markdown code required to show it as a picture.
Note that no check is performed on the file format to verify it is actually
a picture.
=item B<--rename>=I<name> | B<-r> I<name>
Rename the file. The alternate file name supplied with this option must
view release on metacpan or search on metacpan
=head2 GitHub Attestations
This distribution now uses
L<GitHub Attestations|https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/>,
which allow you to verify that the archive file you have was made from
the official repo.
You need a GitHub account and the L<gh tool|https://github.com/larsks/ghcli>.
# download the distro file from GitHub, MetaCPAN, or a CPAN mirror
$ gh auth login
...follow instructions...
$ gh attestation verify App-PPI-Dumper-1.23.tar.gz --owner briandfoy
=head2 Getting help
Although I'm happy to hear from module users in private email,
that's the best way for me to forget to do something.
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
lib/App/PaloAlto/PolicyVerify.pm view on Meta::CPAN
"'fields' argument has $nfields comma-separated values; needs to be 5 - e.g. '2,4,7,8,9'";
}
# Set up the firewall object
my %pa_args = %arguments{qw(uri username password insecure)};
$pa_args{verify_hostname} = delete $pa_args{insecure};
$obj{vr} = $arguments{vr};
$obj{fw} = Device::Firewall::PaloAlto->new(%pa_args)->auth()
or die $obj{fw}->error;
lib/App/PaloAlto/PolicyVerify.pm view on Meta::CPAN
version 0.0.2
=head1 SYNOPSIS
This is the supporting module for the L<pa_policy_verify> application.
=head1 DESCRIPTION
This module contains the methods used by the L<pa_policy_verify> application.
It takes in information allowing it to connect to a Palo Alto firewall, and a logfile containing
flows - source/destination IP & ports, and a protocol.
It then runs each flow in the log against the security rulebase currently installed on the Palo Alto firewall
and returns a result. The result contains:
lib/App/PaloAlto/PolicyVerify.pm view on Meta::CPAN
logfile => '/home/user/logs.csv',
sepchar => ',',
fields => '0,1,2,3,4'
);
Contructs the object. Each argument maps to a command line switch in L<pa_policy_verify>. Please refer to its
documentation for information and default values.
The only argument without a default is C<logfile>.
=head2 sepchar
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
lib/App/PerlTidy/Tk.pm view on Meta::CPAN
my $url = $info{href};
#print $url, "\n";
#open_browser($url); # https://rt.cpan.org/Public/Bug/Display.html?id=133315
#print "done\n";
my $cmd = open_browser_cmd($url);
# TODO: verify that the URL is well formatted before passing it to system
if ($^O eq 'MSWin32') {
system("$cmd $url");
} else {
system("$cmd $url &");
}
view release on metacpan or search on metacpan
lib/App/PersistentSSH.pm view on Meta::CPAN
which is the control master under C<auto> all subsequently made connections
will also close. By keeping a daemonized, managed instance of C<ssh> this
problem is avoided.
Use C<ssh -v yourhost> to verify that the connection really is going through
the control master.
You can create a F<launchd> service for this using
L<http://lingon.sourceforge.net/>. I use:
view release on metacpan or search on metacpan
lib/App/Phoebe/Oddmuse.pm view on Meta::CPAN
# for a cert.
sub oddmuse_fingerprint_name {
my $stream = shift;
my $host = shift;
my $token = shift;
# This requires SSL_verify_mode => SSL_VERIFY_PEER and SSL_verify_callback =>
# \&verify_fingerprint (which must not reject self-signed certificates).
my $fingerprint = $stream->handle->get_fingerprint();
if (not $fingerprint) {
result($stream, "60", "You need a client certificate with a common name to edit this wiki");
return;
}
view release on metacpan or search on metacpan
lib/App/Photobear.pm view on Meta::CPAN
# Try anothe method: SSLeay 1.49 or higher required
eval {
require LWP::UserAgent;
my $ua = LWP::UserAgent->new;
$ua->ssl_opts(verify_hostname => 0); # Disable SSL verification (optional)
my $response = $ua->get($url);
if ($response->is_success) {
return 1;
} else {
lib/App/Photobear.pm view on Meta::CPAN
eval {
require LWP::UserAgent;
# Create a UserAgent object
my $ua = LWP::UserAgent->new;
$ua->ssl_opts(verify_hostname => 0); # Disable SSL verification (optional)
# Send the initial GET request
my $response = $ua->get($url);
# Follow redirects if any
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.50.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
lib/App/Pimpd/Validate.pm view on Meta::CPAN
print STDERR "No song on playlist position 42!\n";
}
=head1 DESCRIPTION
App::Pimpd::Validate provides functions for verifying certain conditions that's
crucial for other functions.
=head1 EXPORTS
=over
view release on metacpan or search on metacpan
warning when tmp directory is not empty
all elements in sub directories are copied
order of presentation
commands accepted
commands do as expected
verify git is installed
verify feed works with ironman feed generator
install:
#install .plog
#do not override previous .plog
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
t/cpan/Mojo2/UserAgent.pm view on Meta::CPAN
}
# TLS
if ( $options{tls} = $proto eq 'https' ) {
map { $options{"tls_$_"} = $self->$_ } qw(ca cert key);
$options{tls_options}{SSL_verify_mode} = 0x00 if $self->insecure;
}
weaken $self;
my $id;
return $id = $loop->client(
t/cpan/Mojo2/UserAgent.pm view on Meta::CPAN
=head2 ca
my $ca = $ua->ca;
$ua = $ua->ca('/etc/tls/ca.crt');
Path to TLS certificate authority file used to verify the peer certificate, defaults to the value of the
C<MOJO_CA_FILE> environment variable.
# Show certificate authorities for debugging
IO::Socket::SSL::set_defaults(SSL_verify_callback => sub { say "Authority: $_[2]" and return $_[0] });
=head2 cert
my $cert = $ua->cert;
$ua = $ua->cert('/etc/tls/client.crt');
view release on metacpan or search on metacpan
author/patch-next-version.pl view on Meta::CPAN
foreach my $fn (keys(%files))
{
die("Failed to find '$fn' in '$toplevel'\n") unless -f "$toplevel/$fn";
}
# verify we're clean
#
my @status = qx(git status --porcelain --ignored 2>&1);
@status = grep(!m#^!! tmp/$#, @status);
die("Tree not clean:\n@status") if (@status || $?);
view release on metacpan or search on metacpan
script/pureproxy.pl view on Meta::CPAN
=head2 --ssl-key-file
Specifies the path to the SSL key file. (default: none)
=head2 --ssl-verify-mode
Specifies the verification mode for the client certificate.
See L<IO::Socket::SSL/SSL_verify_mode> for details. (default: 0)
=head2 --timeout
Seconds until timeout. (default: 300)
view release on metacpan or search on metacpan
lib/App/Qmail/DMARC.pm view on Meta::CPAN
__END__
=head1 NAME
qmail-dmarc - verify using DMARC and queue a mail message for delivery
=head1 DESCRIPTION
qmail-dmarc is designed to be called by qmail-smtpd instead of qmail-queue
and will verify if incoming e-mail conforms to the DMARC policy of its
sender domain:
=over 4
=item 1.
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
lib/App/RPi/EnvUI/API.pm view on Meta::CPAN
Mandatory, String. The user name to validate the password for.
$pw
Mandatory, String. The plain text password to verify.
Return: True (C<1>) if successful, C<undef> otherwise.
=head2 aux($aux_id)
view release on metacpan or search on metacpan
lib/App/Rakubrew.pm view on Meta::CPAN
}
}
else {
my $version = shift @args;
if ($version ne '--unset') {
verify_version($version);
}
}
} elsif ($arg eq 'local') {
validate_brew_mode();
lib/App/Rakubrew.pm view on Meta::CPAN
sub test {
my ($self, $version) = @_;
$self->match_and_run($version, sub {
my $matched = shift;
verify_version($matched);
my $v_dir = catdir($versions_dir, $matched);
if (!-d $v_dir) {
say STDERR "Version $matched was not built by rakubrew.";
say STDERR "Refusing to try running spectest there.";
exit 1;
view release on metacpan or search on metacpan
lib/App/Raps2.pm view on Meta::CPAN
cost => $self->{master_cost},
salt => $self->{master_salt},
passphrase => $pass,
);
$self->pw->verify( $self->{master_hash} );
return;
}
sub create_config {
view release on metacpan or search on metacpan
src/fast-recs-collate/hash.c view on Meta::CPAN
hash->mask = mask;
hash->nchains *= 2;
hash->lowmark *= 2;
hash->highmark *= 2;
}
assert (hash_verify(hash));
}
/*
* Cut a table size in half. This is done by folding together adjacent chains
* and populating the lower half of the table with these chains. The chains are
src/fast-recs-collate/hash.c view on Meta::CPAN
hash->table = newtable;
hash->mask >>= 1; /* 9 */
hash->nchains = nchains;
hash->lowmark /= 2;
hash->highmark /= 2;
assert (hash_verify(hash));
}
/*
* Create a dynamic hash table. Both the hash table structure and the table
src/fast-recs-collate/hash.c view on Meta::CPAN
hash->freenode = hnode_free;
hash->context = NULL;
hash->mask = INIT_MASK;
hash->dynamic = 1; /* 7 */
clear_table(hash); /* 8 */
assert (hash_verify(hash));
return hash;
}
free(hash);
}
src/fast-recs-collate/hash.c view on Meta::CPAN
hash->function = hashfun ? hashfun : hash_fun_default;
hash->dynamic = 0; /* 3 */
hash->mask = compute_mask(nchains); /* 4 */
clear_table(hash); /* 5 */
assert (hash_verify(hash));
return hash;
}
/*
src/fast-recs-collate/hash.c view on Meta::CPAN
/*
* Insert a node into the hash table.
* Notes:
* 1. It's illegal to insert more than the maximum number of nodes. The client
* should verify that the hash table is not full before attempting an
* insertion.
* 2. The same key may not be inserted into a table twice.
* 3. If the table is dynamic and the load factor is already at >= 2,
* grow the table.
* 4. We take the bottom N bits of the hash value to derive the chain index,
src/fast-recs-collate/hash.c view on Meta::CPAN
node->hkey = hkey;
node->next = hash->table[chain];
hash->table[chain] = node;
hash->nodecount++;
assert (hash_verify(hash));
}
/*
* Find a node in the hash table and return a pointer to it.
* Notes:
src/fast-recs-collate/hash.c view on Meta::CPAN
assert (hptr->next == node);
hptr->next = node->next;
}
hash->nodecount--;
assert (hash_verify(hash));
node->next = NULL; /* 6 */
return node;
}
src/fast-recs-collate/hash.c view on Meta::CPAN
hptr = hptr->next;
hptr->next = node->next;
}
hash->nodecount--;
assert (hash_verify(hash));
node->next = NULL;
return node;
}
src/fast-recs-collate/hash.c view on Meta::CPAN
}
/*
* Verify whether the given object is a valid hash table. This means
* Notes:
* 1. If the hash table is dynamic, verify whether the high and
* low expansion/shrinkage thresholds are powers of two.
* 2. Count all nodes in the table, and test each hash value
* to see whether it is correct for the node's chain.
*/
int hash_verify(hash_t *hash)
{
hashcount_t count = 0;
hash_val_t chain;
hnode_t *hptr;
view release on metacpan or search on metacpan
lib/App/Regather/Config.pm view on Meta::CPAN
ciphers => 'tls_cipher_suite',
clientcert => 'tls_cert',
clientkey => 'tls_key',
keydecrypt => '',
sslversion => 'tls_protocol_min',
verify => { tls_reqcert => {
none => 'never',
allow => 'optional',
demand => 'require',
hard => 'require',
try => 'optional',
lib/App/Regather/Config.pm view on Meta::CPAN
foreach my $section ( keys %{ LDAP()} ) { # $section: bnd, opt or ssl
foreach my $item ( keys %{ LDAP->{$section} } ) { # $_: item in each of ones above
$self->add_value( 'ldap.' . $section . '.' . $item,
$section eq 'ssl' && $item eq 'verify' && $cf->is_set('tls_reqcert')
?
LDAP->{$section}->{$item}->{tls_reqcert}->{ $cf->get('tls_reqcert') }
:
$cf->get( LDAP->{$section}->{$item} ),
lib/App/Regather/Config.pm view on Meta::CPAN
clientcert = STRING
clientkey = STRING
keydecrypt = STRING
ssl = STRING
sslversion = STRING
verify = STRING
[service ANY]
all_attr = NUMBER :default 0
chmod = OCTAL :default 0640
chown = NUMBER :default 1
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.78.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
view release on metacpan or search on metacpan
lib/App/Requirement/Arch.pm view on Meta::CPAN
- The requirements can be gathered from multiple places
=head3 Consequences:
- gathering requirement is simple (except if your product manager has problems opening files with unix line ending (no this is not a joke))
- tools to verify the format of the requirements are easilly written
=head3 Positive side effects:
- requirements can be shared between projects, simply gather them from multiple projects
- the physical organisation of the file is left to user, have any directory structure you deem good
lib/App/Requirement/Arch.pm view on Meta::CPAN
Each field has a
TYPE: $SCALAR or $ARRAY
DEFAULT: a default value
ACCEPTED_VALUES: values that are used to verify the contents of the fiels
OPTIONAL: wether the field is optional or not. I prefer always having all the fields but other user may prefer not seeing them. Unecessary fields
are ugly (but the whole buisiness is rather unxxx). the disadvantages of not seing all the fields is that the user has to know what she can
write or not which, IMO, makes it more difficult
TODO: add a comment entry in each field so it can be displayed as help to the user
lib/App/Requirement/Arch.pm view on Meta::CPAN
},
}
=head3 Verification
Running the B<ra_*> application will verify the categories you have assigned to requirements. Categories that are declared in
I<master_categories.pl> will be reported.
=head3 Physical sorting of the requirements
The file system layout doesn't have to match the requirement categorization, although that is sound.
lib/App/Requirement/Arch.pm view on Meta::CPAN
sub load_master_template
{
=head2 load_master_template($master_template_file)
Load and verify the master template.
I<Arguments>
=over 2
lib/App/Requirement/Arch.pm view on Meta::CPAN
sub load_master_categories
{
=head2 load_master_categories($master_categories_file)
Load and verify the master template.
I<Arguments>
=over 2
view release on metacpan or search on metacpan
lib/App/RewriteVersion.pm view on Meta::CPAN
my $bool = $app->dry_run;
$app = $app->dry_run(1);
If true, the module will process files as normal but not actually modify them.
Useful with L</"verbose"> to verify expected functionality.
=head2 follow_symlinks
my $bool = $app->follow_symlinks;
$app = $app->follow_symlinks(1);