ssh: return unexpected msg error when server fails keyboard-interactive auth early by samiponkanen · Pull Request #297 · golang/crypto

samiponkanen · 2024-06-06T09:09:20Z

Seems the OpenSSH server running on windows fails keyboard-interactive
auth this way without sending any prompt to client. In such case the
golang ssh client should not retry keyboard-interactive auth when the
auth method is wrapped in a RetryableAuthMethod(). Rather the auth
method should be immediately marked as tried&failed and the client auth
process should move on to next available and acceptable auth method.

Fixes golang/go#67855

gopherbot · 2024-06-06T09:13:52Z

This PR (HEAD: 4df2f67) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-06T09:20:18Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-06-16T16:24:47Z

Message from Nicola Murino:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-06-16T17:32:14Z

This PR (HEAD: 95b457c) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-16T17:38:49Z

This PR (HEAD: 732afad) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-16T17:45:21Z

This PR (HEAD: b5cef16) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-16T17:51:51Z

Message from Sami Pönkänen:

Patch Set 4:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-06-16T17:58:25Z

This PR (HEAD: 28c1119) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-16T18:04:59Z

Message from Sami Pönkänen:

Patch Set 5:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-06-17T06:03:41Z

This PR (HEAD: 3197aea) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-06-17T06:17:07Z

This PR (HEAD: b0e0ee1) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-28T19:27:22Z

Message from Sami Pönkänen:

Patch Set 8:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T04:45:05Z

Message from Ian Lance Taylor:

Patch Set 8: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T04:45:06Z

Message from Go LUCI:

Patch Set 8:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-29T04:44:17Z","revision":"05fa40fa25835defdf17389e58de831828ad5d97"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T04:51:54Z

Message from Ian Lance Taylor:

Patch Set 8: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T04:51:54Z

Message from Go LUCI:

Patch Set 8:

This CL has failed the run. Reason:

Tryjob golang/try/x_crypto-gotip-windows-amd64 has failed with summary (view all results):

go on master (commit eb6f2c2)
crypto on master (change 590956)

Build or test failure, click here for results.

To reproduce, try gomote repro 8735489480551926145.

Additional links for debugging:

Output for test golang.org/x/crypto module

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T04:51:54Z

Message from Go LUCI:

Patch Set 8: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T13:04:28Z

Message from Nicola Murino:

Patch Set 8:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T13:11:24Z

Message from Nicola Murino:

Patch Set 8:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T13:32:14Z

This PR (HEAD: f2a8ba2) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-29T14:07:46Z

This PR (HEAD: 4f1243e) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-29T14:14:34Z

Message from Nicola Murino:

Patch Set 13: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T14:14:35Z

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-29T14:08:10Z","revision":"abbd9b1b5bb33fde96cf620bbb60bb40349ed5aa"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T14:21:20Z

Message from Nicola Murino:

Patch Set 13: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T14:21:20Z

Message from Go LUCI:

Patch Set 13:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-29T14:21:21Z

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T12:47:50Z

Message from Nicola Murino:

Patch Set 13:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:02:23Z

This PR (HEAD: e902116) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

…ve auth early

gopherbot · 2024-10-15T13:09:51Z

This PR (HEAD: 7fafc4d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/crypto/+/590956.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-10-15T13:17:16Z

Message from Sami Pönkänen:

Patch Set 15:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:24:41Z

Message from Nicola Murino:

Patch Set 15: Code-Review+2

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:24:42Z

Message from Nicola Murino:

Patch Set 15: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:32:00Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-10-15T13:20:26Z","revision":"7caa73b438116475ede4ee66f6813f8b61bb8d37"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:32:01Z

Message from Nicola Murino:

Patch Set 15: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:32:02Z

Message from Go LUCI:

Patch Set 15:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T13:32:02Z

Message from Go LUCI:

Patch Set 15: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T01:53:39Z

Message from Dmitri Shuralyov:

Patch Set 15: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:40:04Z

Message from Ian Lance Taylor:

Patch Set 16: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:40:04Z

Message from Ian Lance Taylor:

Patch Set 16: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:46:41Z

Message from Go LUCI:

Patch Set 16:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-10-16T02:36:47Z","revision":"5f5cfd4ef501d97b3bfca21afe6a7ec7f4fecb53"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:53:17Z

Message from Ian Lance Taylor:

Patch Set 16: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:53:17Z

Message from Go LUCI:

Patch Set 16:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T02:53:18Z

Message from Go LUCI:

Patch Set 16: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/590956.
After addressing review feedback, remember to publish your drafts!

…ve auth early Seems the OpenSSH server running on windows fails keyboard-interactive auth this way without sending any prompt to client. In such case the golang ssh client should not retry keyboard-interactive auth when the auth method is wrapped in a RetryableAuthMethod(). Rather the auth method should be immediately marked as tried&failed and the client auth process should move on to next available and acceptable auth method. Fixes golang/go#67855 Change-Id: I6c64ae58ff8325774e37af716601b112f8833d8f GitHub-Last-Rev: 7fafc4d GitHub-Pull-Request: #297 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/590956 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Auto-Submit: Nicola Murino <[email protected]> Reviewed-by: Nicola Murino <[email protected]>

gopherbot · 2024-10-16T07:23:15Z

This PR is being closed because golang.org/cl/590956 has been merged.

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from 4df2f67 to 95b457c Compare June 16, 2024 17:28

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from 95b457c to 732afad Compare June 16, 2024 17:37

samiponkanen changed the title ~~ssh: fail keyboard-interactive auth with unexpectedMessageError() when auth fails before receiving the UserAuthInfoRequest from server~~ crypto/ssh: crypto/ssh: return unexpected msg error when server fails keyboard-interactive auth early Jun 16, 2024

samiponkanen changed the title ~~crypto/ssh: crypto/ssh: return unexpected msg error when server fails keyboard-interactive auth early~~ crypto/ssh: return unexpected msg error when server fails keyboard-interactive auth early Jun 16, 2024

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch 2 times, most recently from 006afc3 to b5cef16 Compare June 16, 2024 17:44

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from b5cef16 to 28c1119 Compare June 16, 2024 17:56

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from 28c1119 to 3197aea Compare June 17, 2024 06:03

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from 3197aea to b0e0ee1 Compare June 17, 2024 06:16

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from b0e0ee1 to f2a8ba2 Compare September 29, 2024 13:28

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from 4f1243e to e902116 Compare October 15, 2024 13:00

samiponkanen changed the title ~~crypto/ssh: return unexpected msg error when server fails keyboard-interactive auth early~~ ssh: return unexpected msg error when server fails keyboard-interactive auth early Oct 15, 2024

ssh: return unexpected msg error when server fails keyboard-interacti…

7fafc4d

…ve auth early

samiponkanen force-pushed the pull-request/ssh-keyboard-interactive-fail-early-with-unexpected-msg-error branch from e902116 to 7fafc4d Compare October 15, 2024 13:08

gopherbot closed this Oct 16, 2024

Conversation

samiponkanen commented Jun 6, 2024 • edited by dmitshur Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Jun 6, 2024

Uh oh!

gopherbot commented Jun 6, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 16, 2024

Uh oh!

gopherbot commented Jun 17, 2024

Uh oh!

gopherbot commented Jun 17, 2024

Uh oh!

gopherbot commented Sep 28, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Sep 29, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 15, 2024

Uh oh!

gopherbot commented Oct 16, 2024

Uh oh!

gopherbot commented Oct 16, 2024

Uh oh!

samiponkanen commented Jun 6, 2024 •

edited by dmitshur

Loading