Result:
found more than 505 distributions - search limited to the first 2001 files matching your query
( run in 1.001 )
App-GitGerrit
view release on metacpan or search on metacpan
lib/App/GitGerrit.pm view on Meta::CPAN
return (undef, undef);
}
}
sub credential_description_file {
my ($baseurl, $password) = @_;
my %credential = (
protocol => $baseurl->scheme,
host => $baseurl->host,
path => $baseurl->path,
password => $password,
);
# Try to get the username from the baseurl
my ($username) = url_userinfo($baseurl);
$credential{username} = $username if $username;
lib/App/GitGerrit.pm view on Meta::CPAN
# means that we're using a pre-1.8 Git, which doesn't
# support git-credential yet.
$git_credential_supported = 0;
}
my ($username, $password) = @credentials{qw/username password/};
unless (defined $username && defined $password) {
debug "Get credentials from git-gerrit.baseurl";
($username, $password) = url_userinfo(config('baseurl'));
}
unless (defined $username && defined $password) {
debug "Get credentials from a .netrc file";
if (eval {require Net::Netrc}) {
if (my $mach = Net::Netrc->lookup(URI->new(config('baseurl'))->host, $username)) {
($username, $password) = ($mach->login, $mach->password);
}
} else {
debug "Failed to require Net::Netrc";
}
}
unless (defined $username && defined $password) {
debug "Prompt the user for the credentials";
if (eval {require Term::Prompt}) {
$username = Term::Prompt::prompt('x', 'Gerrit username: ', '', $ENV{USER});
$password = Term::Prompt::prompt('p', 'Gerrit password: ', '');
print "\n";
} else {
debug "Failed to require Term::Prompt";
}
}
defined $username or error "Couldn't get credential's username";
defined $password or error "Couldn't get credential's password";
return ($username, $password);
}
sub set_credentials {
my ($username, $password, $what) = @_;
return 1 unless $git_credential_supported;
$what =~ /^(?:approve|reject)$/
or error "set_credentials \$what argument ($what) must be either 'approve' or 'reject'";
my $baseurl = URI->new(config('baseurl'));
my ($fh, $credfile) = credential_description_file($baseurl, $password);
return system("git credential $what <$credfile") == 0;
}
# The get_message routine returns the message argument to the
lib/App/GitGerrit.pm view on Meta::CPAN
sub gerrit {
my $method = shift;
state $gerrit;
unless ($gerrit) {
my ($username, $password) = get_credentials;
require Gerrit::REST;
$gerrit = Gerrit::REST->new(config('baseurl'), $username, $password);
eval { $gerrit->GET("/projects/" . uri_escape_utf8(config('project'))) };
if (my $error = $@) {
set_credentials($username, $password, 'reject') if $error->{code} == 401;
die $error;
} else {
set_credentials($username, $password, 'approve');
}
}
if ($Options{debug}) {
my ($endpoint, @args) = @_;
App-GitGot
view release on metacpan or search on metacpan
lib/App/GitGot/Command/fork.pm view on Meta::CPAN
}
elsif ( defined $config{pass} and defined $config{user} ) {
return ( login => $config{user} , pass => $config{pass} )
}
else {
say STDERR "Couldn't parse password or access_token info from ~/.github-identity"
and exit(1);
}
}
sub _parse_github_url {
App-GitHooks-Plugin-PgBouncerAuthSyntax
view release on metacpan or search on metacpan
lib/App/GitHooks/Plugin/PgBouncerAuthSyntax.pm view on Meta::CPAN
}
);
next;
}
# Skip lines with the correct username/password specification.
next
if $line =~ /
^
"[^"]*" # Username.
\ # Space.
App-GitHooks-Plugin-PreventTrailingWhitespace
view release on metacpan or search on metacpan
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
App-GitHooks-Plugin-RubyCompile
view release on metacpan or search on metacpan
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
App-GitHub
view release on metacpan or search on metacpan
lib/App/GitHub.pm view on Meta::CPAN
sub set_login {
my ( $self, $login ) = @_;
( $login, my $pass ) = split( /\s+/, $login, 2 );
unless ( $login and $pass ) {
$self->print("Wrong login args ($login $pass), eg fayland password");
return;
}
$self->_do_login( $login, $pass );
}
App-GitHubPullRequest
view release on metacpan or search on metacpan
lib/App/GitHubPullRequest.pm view on Meta::CPAN
list [<state>] Show all pull requests (state: open/closed)
show <number> Show details for the specified pull request
patch <number> Fetch a properly formatted patch for specified pull request
checkout <number> Create tracking branch for specified pull request
login [<user>] [<password>] [<two-factor-auth-token>]
Login to GitHub and receive an access token (deprecated)
authorize Create a GitHub OAuth personal access token
comment <number> [<text>] Create a comment on the specified pull request
close <number> Close the specified pull request
open <number> Reopen the specified pull request
lib/App/GitHubPullRequest.pm view on Meta::CPAN
return 0;
}
sub login {
my ($self, $user, $password, $two_factor_token) = @_;
# Add deprecation message
say "\nThis authorization method is deprecated and will be removed on November 13, 2020.";
say "Please use the 'authorize' command to authenticate with GitHub.\n";
# Try to fetch user/password from git config (or prompt)
$user ||= _qx('git', "config github.user") || _prompt('GitHub username');
$password ||= _qx('git', "config github.password") || _prompt('GitHub password', 'hidden');
die("Please specify a user name.\n") unless $user;
die("Please specify a password.\n") unless $password;
# Prompt for two-factor auth token
$two_factor_token ||= _prompt('GitHub two-factor authentication token (if any)');
# Perform authentication
my $auth = _api_create(
lib/App/GitHubPullRequest.pm view on Meta::CPAN
"scopes" => [qw( public_repo repo )],
"note" => __PACKAGE__,
"note_url" => 'https://metacpan/module/' . __PACKAGE__,
},
$user,
$password,
$two_factor_token,
);
die("Unable to authenticate with GitHub.\n")
unless defined $auth;
my $token = $auth->{'token'};
lib/App/GitHubPullRequest.pm view on Meta::CPAN
die("No valid GitHub repo found. List of remotes exhausted.\n");
}
# Ask the user for some information
# Disable local echo if $hide_echo is true (for passwords)
sub _prompt {
my ($label, $hide_echo) = @_;
_echo('off') if $hide_echo;
print "$label: " if defined $label;
my $input = scalar <STDIN>;
lib/App/GitHubPullRequest.pm view on Meta::CPAN
return $content;
}
# Perform HTTP POST
sub _post_url {
my ($url, $mimetype, $data, $user, $password, $two_factor_token) = @_;
croak("Please specify a URL") unless $url;
croak("Please specify a mimetype") unless $mimetype;
croak("Please specify some data") unless $data;
# See if we should use credentials
my @credentials;
if ( _is_api_url($url) ) {
my $token = _qx('git', 'config github.pr-token');
die("You must login before you can modify information.\n")
unless $token or ( $user and $password );
if ( $user and $password ) {
@credentials = ( '-u', "$user:$password" );
push @credentials, '-H', "X-GitHub-OTP: $two_factor_token"
if $two_factor_token;
}
else {
@credentials = ( '-H', "Authorization: token $token" ) if $token;
lib/App/GitHubPullRequest.pm view on Meta::CPAN
external program. This is usually a symlink set up by your operating system
to the most recently installed text editor.
The text must be encoded using UTF-8.
=head2 login [<user>] [<password>] [<2fa-token>]
DEPRECATED: Logs you in to GitHub and creates a new access token used
instead of your password and two-factor authentication token. If you don't
specify either of the options, they are looked up in your git config github
section. If none of those are found, you'll be prompted for them.
=head2 authorize [<access-token>]
App-GitUtils
view release on metacpan or search on metacpan
[profile=production]
username=bar
pass=honey
When you specify C<--config-profile=dev>, C<username> will be set to C<foo> and
C<password> to C<beaver>. When you specify C<--config-profile=production>,
C<username> will be set to C<bar> and C<password> to C<honey>.
=item B<--format>=I<s>
Choose output format, e.g. json, text.
App-Gitc
view release on metacpan or search on metacpan
lib/App/Gitc/Its/Jira.pm view on Meta::CPAN
sub label_service { return 'JIRA'; }
sub label_issue { return 'Issue'; }
our $default_jira_user = 'someuser';
our $default_jira_password = 'somepassword';
our $jira_conf;
sub lookup_jira_user {
my $self = shift;
if (not $jira_conf and -e "$ENV{HOME}/.gitc/jira.conf") {
$jira_conf = YAML::LoadFile("$ENV{HOME}/.gitc/jira.conf");
} else {
$jira_conf = {};
}
my $jira_user = $jira_conf->{user} || $default_jira_user;
my $jira_password = $jira_conf->{password} || $default_jira_password;
return ($jira_user, $jira_password);
}
sub lookup_status_strings
{
my $self = shift;
lib/App/Gitc/Its/Jira.pm view on Meta::CPAN
# build and return the Issue object
our %jira;
my $jira = $jira{$uri};
if ( not $jira ) {
my ($jira_user, $jira_password) = $self->lookup_jira_user;
$jira{$uri} = $jira
= JIRA::Client->new( $uri, $jira_user, $jira_password );
die "Unable to connect to JIRA SOAP API" unless $jira;
}
return $jira;
}
lib/App/Gitc/Its/Jira.pm view on Meta::CPAN
# build and return the Issue object
our %jira_rest;
my $jira = $jira_rest{$uri};
if ( not $jira ) {
my ($jira_user, $jira_password) = $self->lookup_jira_user;
$jira_rest{$uri} = $jira = JIRA::Client::REST->new(
username => $jira_user,
password => $jira_password,
url => $uri,
);
die "Unable to connect to JIRA REST API" unless $jira;
}
App-Glacier
view release on metacpan or search on metacpan
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
App-GnuCash-MembershipUtils
view release on metacpan or search on metacpan
lib/App/GnuCash/MembershipUtils.pm view on Meta::CPAN
return ("filename '$filename' does not exist", undef) unless -f $filename;
my $schema = GnuCash::Schema->connect(
"dbi:SQLite:$filename", # dsn
undef, # user
undef, # password
{ # dbi params
sqlite_open_flags => DBD::SQLite::OPEN_READONLY,
}
);
App-Gnuget
view release on metacpan or search on metacpan
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
App-GoogleSearchUtils
view release on metacpan or search on metacpan
script/google-search view on Meta::CPAN
[profile=production]
username=bar
pass=honey
When you specify C<--config-profile=dev>, C<username> will be set to C<foo> and
C<password> to C<beaver>. When you specify C<--config-profile=production>,
C<username> will be set to C<bar> and C<password> to C<honey>.
=item B<--no-config>, B<-C>
Do not use any configuration file.
App-Greple-subst
view release on metacpan or search on metacpan
share/jtca-katakana-guide-3.pl view on Meta::CPAN
ãƒãƒ«ãƒ– valve ３
ãƒãƒ¼ bar １ï¼ï¼‘
ãƒãƒ¼ã‚¸ãƒ§ãƒ³ version １ï¼ï¼”ã€ï¼“
ãƒãƒ¼ã‚¸ãƒ³ virgin ３
ãƒãƒ¼ãƒ†ã‚£ã‚«ãƒ« vertical １ï¼ï¼‘ã€ï¼‘ï¼ï¼”ã€ï¼“ã€ï¼”ï¼ï¼‘例外
パスワード password １ï¼ï¼”
パピルス papyrus １ï¼ï¼’例外
パフォーマンス performance １ï¼ï¼”ã€ï¼’ï¼ï¼”
パラメーター parameter １ï¼ï¼‘ã€ï¼‘ï¼ï¼”
パース perth １ï¼ï¼”
パースペクティブ perspective １ï¼ï¼”ã€ï¼“ã€ï¼”ï¼ï¼‘例外
App-GroupSecret
view release on metacpan or search on metacpan
DESCRIPTION
groupsecret is a program that makes it easy for groups to share a
secret between themselves without exposing the secret to anyone else.
It could be used, for example, by a team to share an ansible-vault(1)
password; see "ansible-vault" for more about this particular use case.
The goal of this program is to be easy to use and have few dependencies
(or only have dependencies users are likely to already have installed).
groupsecret works by encrypting a secret with a symmetric cipher
ansible-vault
Ansible Vault <http://docs.ansible.com/ansible/latest/vault.html> is a
great way to securely store secret configuration variables for use in
your playbooks. Vaults are secured using a password, which is okay if
you're the only one who will need to unlock the Vault, but as soon as
you add team members who also need to access the Vault you are then
faced with how to manage knowledge of the password. When a team member
leaves, you'll also need to change the Vault password which means
you'll need a way to communicate the change to other team members who
also have access. This becomes a burden to manage.
You can use groupsecret to manage this very easily by storing the Vault
password in a groupsecret keyfile. That way, you can add or remove keys
and change the secret (the Vault password) at any time without
affecting the team members that still have access. Team members always
use their own SSH2 RSA keys to unlock the Vault, so no new password
ever needs to be communicated out.
To set this up, first create a keyfile with the public keys of everyone
on your team:
groupsecret -f vault-password.yml add-keys keys/*_rsa.pub
Then set the secret in the keyfile to a long random number:
groupsecret -f vault-password.yml set-secret rand:48
This will be the Ansible Vault password. You can see it if you want
using the "print-secret" command, but you don't need to.
Then we'll take advantage of the fact that an Ansible Vault password
file can be an executable program that prints the Vault password to
STDOUT. Create a file named vault-password with the following script,
and make it executable (chmod +x vault-password):
#!/bin/sh
# Use groupsecret <https://github.com/chazmcgarvey/groupsecret> to access the Vault password
exec ${GROUPSECRET:-groupsecret} -f vault-password.yml print-secret
Commit both vault-password and vault-password.yml to your repository.
Now use ansible-vault(1) to add files to the Vault:
ansible-vault --vault-id=vault-password encrypt foo.yml bar.yml baz.yml
These examples show the Ansible 2.4+ syntax, but it can be adapted for
earlier versions. The significant part of this command is
--vault-id=vault-password which refers to the executable script we
created earlier. You can use that argument with other ansible-vault
commands to view or edit the encrypted files.
You can also pass that same argument to ansible-playbook(1) in order to
use the Vault in playbooks that refer to the encrypted variables:
ansible-playbook -i myinventory --vault-id=vault-password site.yml
What this does is execute vault-password which executes groupsecret to
print the secret contained in the vault-password.yml file (which is
actually the Vault password) to STDOUT. In order to do this,
groupsecret will decrypt the keyfile passphrase using any one of the
private keys that have associated public keys added to the keyfile.
That's it! Pretty easy.
If and when you need to change the Vault password (such as when a team
member leaves), you can follow this procedure which is probably mostly
self-explanatory:
groupsecret -f vault-password.yml delete-key keys/revoked/jdoe_rsa.pub
groupsecret -f vault-password.yml print-secret >old-vault-password.txt
groupsecret -f vault-password.yml set-secret rand:48
echo "New Vault password: $(groupsecret -f vault-password.yml)"
ansible-vault --vault-id=old-vault-password.txt rekey foo.yml bar.yml baz.yml
# You will be prompted for the new Vault password which you can copy from the output above.
rm -f old-vault-password.txt
This removes access to the keyfile secret and to the Ansible Vault.
Don't forget that you may also want to change the variables being
protected by the Vault. After all, those secrets are the actual things
we're protecting by doing all of this, and an exiting team member may
App-I18N
view release on metacpan or search on metacpan
share/static/jquery-1.4.2.js view on Meta::CPAN
});
jQuery.event.add(this, "keypress.specialSubmit", function( e ) {
var elem = e.target, type = elem.type;
if ( (type === "text" || type === "password") && jQuery( elem ).closest("form").length && e.keyCode === 13 ) {
return trigger( "submit", this, arguments );
}
});
} else {
share/static/jquery-1.4.2.js view on Meta::CPAN
return "checkbox" === elem.type;
},
file: function(elem){
return "file" === elem.type;
},
password: function(elem){
return "password" === elem.type;
},
submit: function(elem){
return "submit" === elem.type;
},
image: function(elem){
share/static/jquery-1.4.2.js view on Meta::CPAN
};
}
var jsc = now(),
rscript = /<script(.|\s)*?\/script>/gi,
rselectTextarea = /select|textarea/i,
rinput = /color|date|datetime|email|hidden|month|number|password|range|search|tel|text|time|url|week/i,
jsre = /=\?(&|$)/,
rquery = /\?/,
rts = /(\?|&)_=.*?(&|$)/,
rurl = /^(\w+:)?\/\/([^\/?#]+)/,
r20 = /%20/g,
share/static/jquery-1.4.2.js view on Meta::CPAN
async: true,
/*
timeout: 0,
data: null,
username: null,
password: null,
traditional: false,
*/
// Create the request object; Microsoft failed to properly
// implement the XMLHttpRequest in IE7 (can't request local files),
// so we use the ActiveXObject when it is available
share/static/jquery-1.4.2.js view on Meta::CPAN
}
// Open the socket
// Passing null username, generates a login popup on Opera (#2865)
if ( s.username ) {
xhr.open(type, s.url, s.async, s.username, s.password);
} else {
xhr.open(type, s.url, s.async);
}
// Need an extra try/catch for cross domain requests in Firefox 3
App-Icli
view release on metacpan or search on metacpan
t/in/objects.cache view on Meta::CPAN
command_name check_ssh_4
command_line /usr/lib/nagios/plugins/check_ssh -4 '$HOSTADDRESS$'
}
define command {
command_name check_ssh_no_password_login
command_line /usr/local/lib/nagios/plugins/check_ssh_no_password_login -H '$HOSTADDRESS$'
}
define command {
command_name check_ssh_port
command_line /usr/lib/nagios/plugins/check_ssh -p '$ARG1$' '$HOSTADDRESS$'
t/in/objects.cache view on Meta::CPAN
retain_nonstatus_information 1
}
define service {
host_name aneurysm
service_description SSH password login disabled
check_period 24x7
check_command check_ssh_no_password_login
contact_groups admins
notification_period 24x7
initial_state o
check_interval 15.000000
retry_interval 1.000000
t/in/objects.cache view on Meta::CPAN
retain_nonstatus_information 1
}
define service {
host_name steel.derf0.net
service_description SSH password login disabled
check_period 24x7
check_command check_ssh_no_password_login
contact_groups admins
notification_period 24x7
initial_state o
check_interval 15.000000
retry_interval 1.000000
App-Ikachan
view release on metacpan or search on metacpan
lib/App/Ikachan.pm view on Meta::CPAN
irc server port.
=item -K, --Keyword
irc server password
=item -N, --Nickname
irc nickname
App-ImageMagickUtils
view release on metacpan or search on metacpan
script/downsize-image view on Meta::CPAN
[profile=production]
username=bar
pass=honey
When you specify C<--config-profile=dev>, C<username> will be set to C<foo> and
C<password> to C<beaver>. When you specify C<--config-profile=production>,
C<username> will be set to C<bar> and C<password> to C<honey>.
=item B<--no-config>, B<-C>
Do not use any configuration file.
App-IniDiff-IniFile
view release on metacpan or search on metacpan
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
App-JC-Client
view release on metacpan or search on metacpan
lib/App/JC/Client.pm view on Meta::CPAN
In this case the config file is written in yaml.
---
url: https://jirahost/jira/
user: yourusername
pass: yourpassword
default:
tasktype: Aufgabe
Please make sure the config file is only readable by your user because a password is saved within it.
=head1 AUTHOR
Dominik Meyer <dmeyer@federationhq.de>
App-JESP
view release on metacpan or search on metacpan
lib/App/JESP.pm view on Meta::CPAN
# Settings
## DB Connection attrbutes.
has 'dsn' => ( is => 'ro', isa => 'Str', required => 1 );
has 'username' => ( is => 'ro', isa => 'Maybe[Str]', required => 1);
has 'password' => ( is => 'ro', isa => 'Maybe[Str]', required => 1);
has 'home' => ( is => 'ro', isa => 'Str', required => 1 );
## JESP Attributes
has 'prefix' => ( is => 'ro', isa => 'Str', default => 'jesp_' );
has 'driver_class' => ( is => 'ro', isa => 'Str', lazy_build => 1);
# Operational stuff
has 'get_dbh' => ( is => 'ro', isa => 'CodeRef', default => sub{
my ($self) = @_;
return sub{
return DBI->connect( $self->dsn(), $self->username(), $self->password(),
{ RaiseError => 1,
PrintError => 0,
AutoCommit => 1,
});
};
lib/App/JESP.pm view on Meta::CPAN
my $jesp = App::JESP->new({
interactive => 0, # No ANSI color
home => 'path/to/jesphome',
dsn => ...,
username => ...,
password => ...
});
$jesp->install();
$jesp->deploy();
App-JIRAPrint
view release on metacpan or search on metacpan
lib/App/JIRAPrint.pm view on Meta::CPAN
# Operation properties
has 'url' => ( is => 'ro', isa => 'Str', lazy_build => 1 );
has 'username' => ( is => 'ro', isa => 'Str' , lazy_build => 1);
has 'password' => ( is => 'ro', isa => 'Str' , lazy_build => 1);
has 'project' => ( is => 'ro', isa => 'Str' , lazy_build => 1 );
has 'sprint' => ( is => 'ro', isa => 'Str' , lazy_build => 1 );
has 'maxissues' => ( is => 'ro', isa => 'Int' , lazy_build => 1);
lib/App/JIRAPrint.pm view on Meta::CPAN
has 'tt' => ( is => 'ro', isa => 'Template', lazy_build => 1);
sub _build_jira{
my ($self) = @_;
$log->info("Accessing JIRA At ".$self->url()." as '".$self->username()."' (+password)");
return JIRA::REST->new( $self->url() , $self->username() , $self->password() );
}
sub _build_fields{
my ($self) = @_;
return $self->config()->{fields} // [ qw/key status summary assignee issuetype/ ];
lib/App/JIRAPrint.pm view on Meta::CPAN
sub _build_username{
my ($self) = @_;
return $self->config()->{username} // die "Missing username ".$self->config_place()."\n";
}
sub _build_password{
my ($self) = @_;
return $self->config()->{password} // die "Missing password ".$self->config_place()."\n";
}
sub _build_project{
my ($self) = @_;
return $self->config()->{project} // die "Missing project ".$self->config_place()."\n";
lib/App/JIRAPrint.pm view on Meta::CPAN
return $output;
}
=head2 fetch_fields
Returns the list of available fiels at this (url, username, password, project)
Usage:
my $fields = $this->fetch_fields();
lib/App/JIRAPrint.pm view on Meta::CPAN
return $self->jira->GET('/field');
}
=head2 fetch_issues
Fetches issues from JIRA Using this object properties (url, username, password, project, maxissues, fields)
Usage:
my $issues = $this->fetch_issues();
App-JenkinsCli
view release on metacpan or search on metacpan
lib/App/JenkinsCli.pm view on Meta::CPAN
The username to access jenkins by
=item api_pass
The password to access jenkins by
=item test
Flag to not actually perform changes
App-KGB
view release on metacpan or search on metacpan
lib/App/KGB/API.pm view on Meta::CPAN
the hash is the hexadecimal representation of the SHA-1 hash calculated over
the following data:
=over
=item Project password
This is the shared password known to the client and the server.
=item project-name
=item request-text
App-KeePass2
view release on metacpan or search on metacpan
lib/App/KeePass2.pm view on Meta::CPAN
}
);
$self->_fkp->unlock if $self->_fkp->is_locked;
my $master = $self->_get_master_key;
my $confirm = $self->_get_confirm_key;
croak "Your master password is different from the confirm password !"
if $master ne $confirm;
$self->_fkp->save_db( $self->file, $master );
return;
}
lib/App/KeePass2.pm view on Meta::CPAN
=head1 ATTRIBUTES
=head2 file
The password file
=head2 create
Create the keepass2 file
App-Koyomi
view release on metacpan or search on metacpan
lib/App/Koyomi/DataSource/Job/Teng.pm view on Meta::CPAN
my $connector
= $ctx->config->{datasource}{connector}{job}
// $ctx->config->{datasource}{connector};
my $teng = App::Koyomi::DataSource::Job::Teng::Object->new(
connect_info => [
$connector->{dsn}, $connector->{user}, $connector->{password},
+{ RaiseError => 1, PrintError => 0, AutoCommit => 1 },
],
schema => App::Koyomi::DataSource::Job::Teng::Schema->instance,
);
my %obj = (teng => $teng);
App-LDAP
view release on metacpan or search on metacpan
lib/App/LDAP/Command/Add/User.pm view on Meta::CPAN
);
my $user = App::LDAP::LDIF::User->new(
base => $self->base // config()->{nss_base_passwd}->[0],
uid => $username,
userPassword => encrypt(new_password()),
uidNumber => $uid->get_value("uidNumber"),
gidNumber => $self->gid_of( $self->group ),
sn => $self->surname,
mail => $self->mail,
);
App-LLEvalBot
view release on metacpan or search on metacpan
lib/App/LLEvalBot/CLI.pm view on Meta::CPAN
);
$parser->getoptionsfromarray(\@argv, \my %opt, qw/
host=s
port=s
password=s
channels=s@
nickname=s
enable-ssl
/) or pod2usage(1);
App-LXC-Container
view release on metacpan or search on metacpan
lib/App/LXC/Container/Run.pm view on Meta::CPAN
my $re_ids = $self->{user};
# TODO: Should we distinguish UIDs/GIDs? For now we just simply
# add them all. This has the charm that files of other users
# within the same group will be visible with their names in
# directory listings. The disadvantage is making them known by
# name (but the password hashes are always safe):
foreach (@{$self->{uids}}, @{$self->{gids}})
{ $re_ids .= '|' . $_; }
foreach (ACCOUNT_FILES)
{
# remove first to be sure not to overwrite something linked:
lib/App/LXC/Container/Run.pm view on Meta::CPAN
open my $out, '>', $lxc_etc . $_
or fatal 'can_t_open__1__2', $lxc_etc . $_, $!;
while (<$in>)
{
next unless m/(?:^|[:,])(?:$re_ids|root)(?:[:,]|$)/;
# If applicable, remove the encrypted password, as it's
# not needed inside of the container:
s/^([^:]+):([^!:*][^:*][^:]+):/$1:!:/;
print $out $_;
}
close $out;
( run in 1.001 second using v1.01-cache-2.11-cpan-49f99fa48dc )