-
-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues logging in with Warp as the client. #2115
Comments
Warp seems to run in this quite unusual way. Not sure this will be supported. |
@micheloosterhof I saw you closed this issue. Do I understand correctly it's a wontfix for now, or has it been fixed (both are fine obviously, but just clarifying the result of this GH issue). |
Won'tfix. I don't expect any attackers to login with the Warp client. |
To clarify maybe a bit further, I'm not intending to build out full support for Warp as a client, but I am curious why the the current login is failing at this point, it should fail a little bit further down the line. |
Describe the bug
Connecting to Cowrie using Warp.dev terminal throws error. Using macOS standard terminal works fine.
SSH Terminal throws:
exec request failed on channel 1
Cowrie container logs:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connect, stay connected, and be able to navigate through the Cowrie Honeypot.
Server (please complete the following information):
cowrie/cowrie:latest
macOS
The text was updated successfully, but these errors were encountered: