It does not run from docker image
See original GitHub issueI have ran the mentioned command: docker run --tty --rm balasys/dheater --protocol ssh ecc256.badssl.com andresulted the following error:
#docker run --tty --rm balasys/dheater --thread-num 4 --protocol ssh ecc256.badssl.com
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/common/transfer.py", line 139, in _init_connection
self._socket = socket.create_connection((self.ip, self.port), self.timeout)
File "/usr/local/lib/python3.9/socket.py", line 844, in create_connection
raise err
File "/usr/local/lib/python3.9/socket.py", line 832, in create_connection
sock.connect(sa)
socket.timeout: timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/dheat", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.9/site-packages/dheater/__main__.py", line 258, in main
enforcer = DHEnforcerThreadSSH(args.uri, args.timeout, pre_check_result)
File "<attrs generated init dheater.__main__.DHEnforcerThreadBase>", line 15, in __init__
File "/usr/local/lib/python3.9/site-packages/dheater/__main__.py", line 89, in __attrs_post_init__
self._pre_check()
File "/usr/local/lib/python3.9/site-packages/dheater/__main__.py", line 117, in _pre_check
self.pre_check_result = analyzer.analyze(self._get_client())
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/ssh/dhparams.py", line 111, in analyze
analyzer_result = AnalyzerCiphers().analyze(analyzable)
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/ssh/ciphers.py", line 80, in analyze
server_messages = analyzable.do_handshake(last_message_type=SshMessageCode.KEXINIT)
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/ssh/client.py", line 111, in do_handshake
self.init_connection()
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/common/transfer.py", line 251, in init_connection
self._init_connection()
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/ssh/client.py", line 102, in _init_connection
self.l4_transfer.init_connection()
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/common/transfer.py", line 73, in init_connection
self._init_connection()
File "/usr/local/lib/python3.9/site-packages/cryptolyzer/common/transfer.py", line 142, in _init_connection
six.raise_from(NetworkError(NetworkErrorType.NO_CONNECTION), e)
File "<string>", line 3, in raise_from
cryptolyzer.common.exception.NetworkError: connection to target cannot be established
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
docker - Container is not running
After running the container normally with docker run IMAGE_ID , you can just go to another terminal and use docker exec -it CONTAINER_ID...
Read more >How to Fix and Debug Docker Containers Like a Superhero
Take the container's default command and attempt to run it again. A “command not found” error message will appear.
Read more >I can create image, but image will not start - General
Basically the run command is create+start. Using the command docker run --rm -it centos:centos7 bash shoud work to create a new centos container ......
Read more >Run your image as a container
To run an image inside of a container, we use the docker run command. The docker run command requires one parameter and that...
Read more >Run your image as a container
To run an image inside of a container, we use the docker run command. It requires one parameter and that is the image...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Docker images has been updated. Now neither the latest version nor 0.2.1 version gives you Python traceback in the case of a connection error.
ecc256.badssl.com is not reachable on port 22. besides, you should not run this against servers you do not control. by doing so you are effectively performing a cyber attack. depending on your location this may be a crime if you direct this at a server that you are not permitted to target.
you’re supposed to replace ecc256.badssl.com with a target you’re permitted to attack, e.g. a server under your control.
for your second test that seems like you probably can’t reach the host on the port you’re trying to target.