SOCKS5 stopped to work after upgrade from 0.6.2 to 0.6.3.2 #1134
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-11-28#1134
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Python 2.7
I had to release 0.6.3 due to the vulnerability before all the details were tested. I haven't tested SOCKS5 authentication so it's possible it doesn't work. It works without authentication. I am still trying to get the binaries built so I don't have time today but if someone would like to submit a pull request, I'd be very happy to merge it.
I think it's hard to be maintainer when 0-day issue appear in an inopportune moment. All ok.
If you need SOCKS authentication, you can downgrade to 0.6.1, that is not vulnerable to the exploit and the SOCKS code is working.
I added socks authentication to the v0.6 branch but I only have very limited ability to test it. Can you try it?
I have tried to reproduce the issue by setting the proxy server/ tor type to SOCKS5 and did not face the above problem. Can anybody let me know, Is it working fine now?
I have followed
https://community.hetzner.com/tutorials/install-and-configure-danted-proxy-socks5
reference and install Dante-server socks5 and created username and password for authentication and
then tested the connection with curl command and Dante-server is successfully running then I
have tested it with the Qt app and set the network setting according to socks5 username and password
authentication and tested message sending and receiving and both work fine.
Closing as the tests show no issue, current SOCKS5 code works with authentication.