[HTCondor-users] Pool-Password problems when changing to 8.5.5

[Matthias Schnepf <udcqn@xxxxxxxxxxxxxxx>]

Hi,

I wanted to test condor's current development release (8.5.5) and ran 
some tests locally and on remote sites.

We usually authenticate our machines via a pool_password file and it 
worked flawlessly on all different condor versions I can think of 
(8.4.6, 8.4.7, 8.5.4(!)).
The Negotiator/Collector is still running on 8.4.2, but we have an 
update planned in the next few weeks.

> 07/01/16 17:27:58 (pid:4052) HANDSHAKE: in handshake(my_methods = 'PASSWORD')
> 07/01/16 17:27:58 (pid:4052) HANDSHAKE: handshake() - i am the client
> 07/01/16 17:27:58 (pid:4052) HANDSHAKE: sending (methods == 512) to server
> 07/01/16 17:27:58 (pid:4052) HANDSHAKE: server replied (method = 512)
> 07/01/16 17:27:58 (pid:4052) PW.
> 07/01/16 17:27:58 (pid:4052) PW: getting name.
> 07/01/16 17:27:58 (pid:4052) PW: Generating ra.
> 07/01/16 17:27:58 (pid:4052) PW: Client sending.
> 07/01/16 17:27:58 (pid:4052) Client sending: 0, 24(condor_pool@[*our domain name*]), 256
> 07/01/16 17:27:58 (pid:4052) PW: Client receiving.
> 07/01/16 17:27:58 (pid:4052) Wrote server ra.
> 07/01/16 17:27:58 (pid:4052) PW: Client setting keys.
> 07/01/16 17:27:58 (pid:4052) PW: Client checking T.
> 07/01/16 17:27:58 (pid:4052) Calculating hkt 'condor_pool@[*our domain name*]' (24), 'condor_pool@[*our domain name*]' (35).
> 07/01/16 17:27:58 (pid:4052) Hash supplied by server doesn't match that calculated by the client.
> 07/01/16 17:27:58 (pid:4052) PW: CLient sending two.
> 07/01/16 17:27:58 (pid:4052) In client_send_two.
> 07/01/16 17:27:58 (pid:4052) Client sending: 0() 0 0
> 07/01/16 17:27:58 (pid:4052) Sent ok.
> 07/01/16 17:27:58 (pid:4052) AUTHENTICATE: method 512 (PASSWORD) failed.

When testing version 8.5.5, our tests results in "Hash supplied by 
server doesn't match that calculated by the client." although absolutely 
nothing changed on the system.
If I revert to 8.4.7/8.5.4 (or older) without changing any files it 
works and the machine can connect and authenticate.

Has someone else encountered this problem?
Does anyone have an idea how we can resolve the issue?

Thanks & best regards
Matthias