have found out an interesting thing. The issue is related to the length of the password, the previous two old wrong password had length of 8 chars. I tried to add to both other 6 chars at their end and they both now work fine. I didn't look for the minimum length working fine, but it's sure that a length of 14 chars is OK.

Derrick Brasher instead is ok with his 8 chars password. I have given my old wrong password not working to Derrick and Jeffrey and and I think they're investigating about this issue.

Currently  I decided to adopt a  password  14 chars.

Thanks again


Enzo

------------------------------------------------
| Enzo Vitale                                           |
| C.R. ENEA                                             |
| Via Enrico Fermi, 45                          |
| 00044 Frascati (Roma) - Italy         |
| Tel.:  +39 06 94005548                        |
| Fax : +39 06 94005524                 |
| E-mail: [email protected]       |
------------------------------------------------




On 10 Sep 2009, at 4:53 PM, Enzo Vitale wrote:

Hello Derrick,

I had already tried with an xterm and the result was the same.
Now instead I have tried klog with an other account ( and of course a different password ) and it works. So the problem seemed related to the password, then I changed the password, but the problem persisted. Then I changed again the password and I adopted the same belonging to the user tested before successfully and now klog works fine.

The problem seems related to some characters used in the password. How to overcome this issue? Moreover I can't understand why if I performed a ssh with the old password all worked fine, instead with klog not.



Thanks again Derrick for your valuable help

Enzo


On 10 Sep 2009, at 2:38 PM, Derrick Brashear wrote:

It's not going to be software conflicts.

It's either going to be that the string to key function fails in some
(but not all, obviously) cases or
an input failure. In fact, hm. Can you (install X11 if necessary,
then) try klog in an xterm, assuming you used Terminal before? It does work in both Terminal and xterm for me, but Terminal could conceivably
do something odd with character set encoding, whereas xterm is rather
unlikely to.

Beyond that, my next suggestion is to be able to share with me a
password that fails (not necessarily your current password) and if
that
fails, tell me who your administrator is so I can ask about a temporary account.


Reply via email to