On 08/01/2012 12:29 AM, [email protected] wrote:
Hello!
I upgraded Sage to 5.2 today and I have noticed some strange
behaviour with passwords.
First of all, I noticed that new Sage Notebook did not accept my old
password (which consisted of 3 letters). I started it with
'require_login=False" and reset the password for my regular user. After
that I had an ability to login with the generated password and change
it. However, after changing it to some 3-letters password I cannot
login. I tried the passwords gradually "123456", "12345", "1234" and
"123". All of them worked fine except for the last one. So, "1234"
worked fine, but another 4-letter password did not.
And what is the most strange is that any password is accepted by the
Notebook server at the time of changing it, but not every password is
accepted at login time.
P.S. I read that Sage 5.2 includes the flask Notebook. Does it mean
that in sage-on-gentoo overlay we have the flask Notebook as well?
Regards,
Vladimir
-----
<[email protected]>
This is a bit strange. What I do know is that a couple of months ago
(6-7 months ago?), the password length for admin was changed to at least
6 letters, to be consistent with the documentation. The documentation
has always stated that the password length must be at least 6 letters.
Now, I am not sure if it affects the users too. The type of password
probably shouldn't matter. If it does, then it is a serious problem.
Can you check and reproduce these problems in a new notebook directory?
This might help in narrowing down whether the problem is in sagenb or in
the old worksheet directory. To create a new notebook directory, you
need to run sage as follows:
sage -n directory=/tmp/new.sagenb
The directory /tmp/new.sagenb need not be present. It will be created by
sage. By the way, sage-5.2 works with flask notebook. It won't work
with the old notebook since there are changes to sage itself brought
about by the transition to flask notebook.
