-
Notifications
You must be signed in to change notification settings - Fork 55
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
Allow appimageupdatetool work with Torsocks #244
Comments
As someone who has never heard of Torsocks: |
Hi @probonopd this package is in the repo of almost all distributions https://gitlab.torproject.org/tpo/core/torsocks/ it is enough to use it before a command, for example
the behaviour should be the same for This is a comparison between simplescreenrecorder-2025-02-02_19.51.10.mp4this is the message
|
So how does it work? Does it do some |
yes, according to what they wrote on the README
|
@probonopd according to this https://gitlab.torproject.org/legacy/trac/-/issues/34158 it is enough to uncomment Just tested using an alternative torsocks.conf file and the update worked. Btw would like to know how much is safe this approach. simplescreenrecorder-2025-02-03_15.06.41.mp4 |
* Update APP-MANAGER - fix AppImageCommunity/AppImageUpdate#244 - remove "$AMDATADIR"/torsocks.conf after the use - suggest to restart tor.service - fix plural on 1 second elapsed
* Update APP-MANAGER - fix AppImageCommunity/AppImageUpdate#244 - remove "$AMDATADIR"/torsocks.conf after the use - suggest to restart tor.service - fix plural on 1 second elapsed
Hi, in my scripts I often need to update AppImages from several github sources, and these may fail if I reach github API calls limit per hour. Normally as a workaround I use Torsocks, and in other cases, when I don't use
appimageupdatetool
, it works. On the contrary, usingappimageupdatetool
with Torsocks fails. I get an error message about insecure Torsocks connection, as it is not secure.Please, made
appimageupdatetool
work withtorsocks
.Thanks in advance.
The text was updated successfully, but these errors were encountered: