Bug 4697 - tlclient should log if the user decides to not accept a changed/new host key
Summary: tlclient should log if the user decides to not accept a changed/new host key
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.13.0
Assignee: Pierre Ossman
URL:
Keywords: frifl_tester, prosaic
Depends on:
Blocks:
 
Reported: 2013-06-12 09:00 CEST by Karl Mikaelsson
Modified: 2021-01-05 08:50 CET (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2013-06-12 09:00:39 CEST 
Right now the log says:

> 2013-06-12T08:54:16: Fingerprint from server: |39:11:e2:3a:61:d1:9d:ea:c6:06:11:6f:ae:33:8a:c1|
> 2013-06-12T08:54:16: Known host key fingerprints:
> 2013-06-12T08:54:16:     |df:ba:58:05:7a:56:a7:0d:92:98:ef:63:0f:37:a3:41|
> 2013-06-12T08:54:16: Unexpected host key received from server. Possible attack in progress.
> 2013-06-12T08:54:18: Process 16751 killed by signal 15

It would be helpful if we could log why the process was killed.
Comment 2 Pierre Ossman cendio 2020-12-28 16:11:23 CET 
Works now.

Tester needs to check both a new host, and a known host with a new key.
Comment 3 Frida Flodin cendio 2021-01-05 08:50:56 CET 
Indeed, tested both rejecting a new host key and an updated one. Also tested to accept the new and updated keys and the log looks like before.
Note You need to log in before you can comment on or make changes to this bug.