Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
lookup other 'keys'
|
|
|
|
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}'").
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
make sure that what we get from the command line is a string
|
|
|
|
|
|
|
|
[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
|
|
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.
|
|
|
|
|
|
|
|
|
|
is just crap
|
|
bump version to 0.0.7
|
|
|
|
|