Bugzilla – Activity log for bug 4062: Client can't log in to SSH server with ChallengeResponseAutentication without UsePAM
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | New Account
- | Log In
- | Forgot Password
Back to bug 4062
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| ossman | 2011-11-22 10:21:13 CET | Target Milestone | --- | Future |
| aaron | 2012-11-02 09:28:35 CET | Target Milestone | Future | --- |
| ossman | 2012-11-06 10:18:41 CET | Target Milestone | --- | NearFuture |
| astrand | 2012-11-26 13:44:31 CET | Group | thinlinc-int | |
| astrand | 2013-05-28 08:37:04 CEST | Group | thinlinc-int | |
| ossman | 2013-12-03 12:56:20 CET | Target Milestone | NearFuture | 4.2.0 |
| ossman | 2013-12-04 16:13:25 CET | Assignee | astrand | derfian |
| derfian | 2013-12-05 13:32:36 CET | Whiteboard | 3/4/5 | |
| ossman | 2013-12-12 10:38:35 CET | Target Milestone | 4.2.0 | NearFuture |
| didibus | 2016-02-26 22:26:55 CET | CC | didibus | |
| frifl | 2021-08-26 15:25:48 CEST | Assignee | derfian | frifl |
| Target Milestone | MediumPrio | 4.14.0 | ||
| CC | frifl | |||
| frifl | 2021-08-27 14:19:13 CEST | Acceptance Criteria | are available from the server. (If the password was sent it should be seen in the sshd server log) - If it works to ssh with password authentication it should work to log in to thinlinc with password. - Only the authentication method configured in the ThinLinc client should be used. - For password there are two auth methods from the server: keyboard-interactive and password. We should always check the password ONCE against the server even if both |
|
| frifl | 2021-08-30 09:17:47 CEST | Acceptance Criteria | are available from the server. (If the password was sent it should be seen in the sshd server log) - If it works to ssh with password authentication it should work to log in to thinlinc with password. - Only the authentication method configured in the ThinLinc client should be used. - For password there are two auth methods from the server: keyboard-interactive and password. We should always check the password ONCE against the server even if both | are available from the server. (If the password was sent it should be seen in the sshd server log) - If it works to ssh with password authentication it should work to log in to thinlinc with password. - If the wrong password is entered the user should still be presented with the usual error message ("Wrong username or password"). - Only the authentication method configured in the ThinLinc client should be used. - For password there are two auth methods from the server: keyboard-interactive and password. We should always check the password ONCE against the server even if both |
| frifl | 2021-08-30 13:08:39 CEST | Status | NEW | RESOLVED |
| Resolution | --- | FIXED | ||
| Keywords | relnotes | |||
| wilsj | 2021-08-30 14:18:09 CEST | Keywords | wilsj_tester | |
| CC | wilsj | |||
| wilsj | 2021-08-31 11:07:28 CEST | Status | RESOLVED | CLOSED |
| samuel | 2022-01-18 10:52:49 CET | Resolution | FIXED | --- |
| Status | CLOSED | REOPENED | ||
| CC | samuel | |||
| samuel | 2022-01-19 16:10:05 CET | Status | REOPENED | RESOLVED |
| Resolution | --- | FIXED | ||
| samuel | 2022-01-19 16:52:34 CET | Status | RESOLVED | CLOSED |
Back to bug 4062