<p dir="ltr">When using base64, if your input size is not a multiple of 3, you are guaranteed to have at least one symbol, the = used for padding.</p>
<br><div class="gmail_quote"><div dir="ltr">On Sat, Nov 12, 2016, 5:45 PM Kenny Evitt <<a href="mailto:kenny.evitt@gmail.com">kenny.evitt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">You're right, and you provided me with a nice little (fun) project yesterday. <a href="http://stats.stackexchange.com/questions/245610/not-generating-a-valid-password" class="gmail_msg" target="_blank">I asked a question on the statistics Stack Exchange site</a> about how likely it is for those commands to fail to generate a password of sufficient length. While writing up the question I also tested it. In the 12,000 times I ran the commands only <i class="gmail_msg">one</i> execution failed to generate a password of less than 32 characters (really, 130 characters). The one failure was actually the 'worst' possible failure – the password was empty! But given a success rate of 11,999 out of 12,000, the commands seem even more likely to be good enough for a lot of cases.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Regarding the larger discussion, I think options or settings to specify an external password generator, both as a default and as an argument for generating a specific password, would be both useful and keeping with the relative compactness of Pass's features.</div></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg">On Fri, Nov 11, 2016 at 4:41 AM, Kevin Cox <span dir="ltr" class="gmail_msg"><<a href="mailto:kevincox@kevincox.ca" class="gmail_msg" target="_blank">kevincox@kevincox.ca</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_-8269786286034109290HOEnZb gmail_msg"><div class="m_-8269786286034109290h5 gmail_msg">On 11/11/16 09:26, Henrik Christian Grove wrote:<br class="gmail_msg">
<blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Den 10-11-2016 kl. 16:14 skrev Kevin Cox:<br class="gmail_msg">
<blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
On Nov 10, 2016 14:43, "Kenny Evitt" <<a href="mailto:kenny.evitt@gmail.com" class="gmail_msg" target="_blank">kenny.evitt@gmail.com</a><br class="gmail_msg">
<mailto:<a href="mailto:kenny.evitt@gmail.com" class="gmail_msg" target="_blank">kenny.evitt@gmail.com</a>>> wrote:<br class="gmail_msg">
<br class="gmail_msg">
I then edited "test.txt", inserted a newline between the `4` and<br class="gmail_msg">
`5`, and saved the file. I reran the same command as before:<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
Head be default takes 10 lines. So you'll need a couple more newlines.<br class="gmail_msg">
</blockquote>
By default, yes, but he explicit specifies '-c 10' overriding the<br class="gmail_msg">
default, and tr will have removed the newlines before head gets them.<br class="gmail_msg">
Can you actually demonstrate the bug you claim to be there? (I'm not<br class="gmail_msg">
sure no kind of nastiness can hide in those pipes)<br class="gmail_msg">
<br class="gmail_msg">
.Henrik<br class="gmail_msg">
<br class="gmail_msg">
PS. The lack of a way to choose passwords without/with only certain<br class="gmail_msg">
characters is one of the reasons I still haven't switched to pass (using<br class="gmail_msg">
pwsafe), even though I like the project.<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
Password-Store mailing list<br class="gmail_msg">
<a href="mailto:Password-Store@lists.zx2c4.com" class="gmail_msg" target="_blank">Password-Store@lists.zx2c4.com</a><br class="gmail_msg">
<a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br class="gmail_msg">
</blockquote>
<br class="gmail_msg"></div></div>
I'm talking about the first head, not the second. This command gives you 12345 when you expected 12345678.<br class="gmail_msg">
<br class="gmail_msg">
echo '12345<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
67890' | head | tr -dc '0-9 | head -c 8 && echo<br class="gmail_msg">
<br class="gmail_msg">
A fixed command looks like this (drop the unnecessary head)<br class="gmail_msg">
<br class="gmail_msg">
tr -dc 'A-Za-z0-9!"#$%&'\''()*+,-./:;<=>?@[\]^_`{|}~' </dev/random | head -c 32 && echo<div class="m_-8269786286034109290HOEnZb gmail_msg"><div class="m_-8269786286034109290h5 gmail_msg"><br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
Password-Store mailing list<br class="gmail_msg">
<a href="mailto:Password-Store@lists.zx2c4.com" class="gmail_msg" target="_blank">Password-Store@lists.zx2c4.com</a><br class="gmail_msg">
<a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br class="gmail_msg">
</div></div></blockquote></div><br class="gmail_msg"></div>
_______________________________________________<br class="gmail_msg">
Password-Store mailing list<br class="gmail_msg">
<a href="mailto:Password-Store@lists.zx2c4.com" class="gmail_msg" target="_blank">Password-Store@lists.zx2c4.com</a><br class="gmail_msg">
<a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br class="gmail_msg">
</blockquote></div>