<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17/12/2016 23:22, Antoine Beaupré
wrote:<br>
</div>
<blockquote cite="mid:874m22jg3a.fsf@angela.anarc.at" type="cite">
<blockquote type="cite" style="color: #000000;">
<pre wrap="">base64 turns each group of 3 bytes into 4 characters, so 18 bytes => 24
characters
</pre>
</blockquote>
<pre wrap="">ah. yes. i was counting the last = sign, sorry.
</pre>
</blockquote>
"=" signs are only added if the input isn't a multiple of 3 bytes:<br>
<br>
$ echo -n "abc" | base64<br>
YWJj<br>
<br>
> > `base64` is not compatible with any password rules that
require a special character. <br>
> <br>
> actually, it is, often. i have observed that base64 will yield
a + or /<br>
> sign in about one out of 3 generated passwords.<br>
<br>
My experience is also that 16-character base64 passwords are
accepted most of the time, as long as the generated password has a
mix of upper-case/lower-case/digits.<br>
<br>
There are some sites which require a special symbol. However I also
recently came across a site which rejected a base64 password because
it did not allow + or / in a password. You can't have one algorithm
which always works :-(<br>
<br>
Regards,<br>
<br>
Brian.<br>
</body>
</html>