| Age | Commit message (Collapse) | Author |
|---|
|
|
|
tilya-charset_option
& simplify charset selection
Conflicts:
lib/trocla.rb
lib/trocla/util.rb
|
|
|
|
asquelt-safechars
Conflicts:
lib/trocla.rb
|
|
x509 format
|
|
|
|
integer for ranges
ie. for this to work:
$short_and_safe = {
'shellsafe' => 'true',
'length' => 6, # THIS WILL BE STRING!
}
$x = trocla('foo', 'plain', $short_and_safe)
notify { "test: $x": }
|
|
basically excludes characters that might be dangerous if used in shell.
many passwords generated by trocla may end up in some sort of bash
scripts (initscripts, sourced shell variables, etc) which may yeld
problems with default trocla random generator.
this can be now changed either in troclarc (with "shellsafe: true")
or on (ie. "trocla create foo plain '{ length: 32, shellsafe: true}'").
|
|
changes bcrypt-ruby to bcrypt in gemspec
|
|
|
|
integer for ranges
ie. for this to work:
$short_and_safe = {
'shellsafe' => 'true',
'length' => 6, # THIS WILL BE STRING!
}
$x = trocla('foo', 'plain', $short_and_safe)
notify { "test: $x": }
|
|
basically excludes characters that might be dangerous if used in shell.
many passwords generated by trocla may end up in some sort of bash
scripts (initscripts, sourced shell variables, etc) which may yeld
problems with default trocla random generator.
this can be now changed either in troclarc (with "shellsafe: true")
or on (ie. "trocla create foo plain '{ length: 32, shellsafe: true}'").
|
|
basically excludes characters that might be dangerous if used in shell.
many passwords generated by trocla may end up in some sort of bash
scripts (initscripts, sourced shell variables, etc) which may yeld
problems with default trocla random generator.
this can be now changed either in troclarc (with "shellsafe: true")
or on (ie. "trocla create foo plain '{ length: 32, shellsafe: true}'").
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Extending the README
- Add a trocla::yaml class for a simple quickstart.
- Fixes issues: #4 & #5
|
|
|
|
Release of 0.0.2 module which includes template base configuration for t...
|
|
make sure that what we get from the command line is a string
|
|
|
|
|
|
|
|
|
|
trocla CLI.
|
|
[BUG] Store hashed password supplied via 'set' instead of plaintext
|
|
Trocla doesn't save the hashed password in the data file, even if the
format passed to 'set' is not 'plain':
$ echo foobar | trocla set testuser sha512crypt -p
$ grep -A1 testuser trocla_data.yaml
testuser:
sha512crypt: foobar
|
|
Compatibility with latest Puppet version (v3.1.0)
|
|
This makes the Gem usable in the latest Puppet versions.
The handling of RubyGems got revised in Puppet 3.0.1-rc1:
http://projects.puppetlabs.com/issues/16757
The new policy is that either bundler and/or rubygems are guaranteed to
be loaded and initialized when the Puppet manifest is evaluated, making
it unnecessary for Puppet modules to load rubygems.
This new policy broke the puppet-trocla module. This is because
'Puppet.features.rubygems?' always evaluates to false now, which causes
the module to abort the manifest compilation with a message informing
about the necessity of RubyGems to be present.
|
|
markdown
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
as the old code only checks if the format name is empty, we can set any
kind of key/value in the database. for example, this command will work
without any error reported:
trocla set someuser strange_format
I replace the method miss_format by check_format that should be invoked
before any thing related to format.
|
|
|
|
You can use pipe to provide multiple line password.
Side effect: you can use trocla to store/retreive any kind of data,
for example, public SSH key for your deployment tool.
The former way of --pwd-from-stdin should be provided by the
option --password / -p. STDIN has a different mean, IMHO.
|
|
|
