GNU bug report logs - #45856
Shadowsocks issue

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 45856 in the body.
You can then email your comments to 45856 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: musics <at> tutanota.com
To: Bug Guix <bug-guix <at> gnu.org>
Subject: Shadowsocks issue
Date: Thu, 14 Jan 2021 12:43:54 +0100 (CET)

[Message part 1 (text/plain, inline)]

I have been trying to connect to shadowsock for several months, but I have never been successful!

Commands: https://paste.debian.net/1181082

(I do not know much about shadowsocks)

[Message part 2 (text/html, inline)]

Message #8 received at 45856 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: musics <at> tutanota.com
Cc: 45856 <at> debbugs.gnu.org
Subject: bug#45856: Shadowsocks issue
Date: Thu, 14 Jan 2021 19:56:58 +0100

Hello musics,

I don't think that's necessarily a bug in Guix or even in shadowsocks. 
shadowsocks actually has a wiki including an example configuration [1].
To be fair, however, that configuation is not immediately usable, as
you are supposed to change both server and password to make it run.

Even if you aren't very knowledgeable on it, you should try consulting
that manual first and not Guix folk here or in IRC.  There aren't many
shadowsocks users here -- the fact, that no one noticed it was missing
OpenSSL for more than 2.5 years, speaks volumes -- or in other words,
the overlap between "people who could help you set up shadowsocks" and
"people, who use Guix" is rather small.  The reason I was able to fix
that issue, was because I know a little Python and I know how to
package stuff in Guix, not because of some higher knowledge about
shadowsocks itself.  And I only noticed, because someone (else?) was
reporting it at the time.

The fact, that shadowsocks has not seen a single commit for two years
(and only one in nearly three years) does not make it seem as if it is
still maintained upstream either.  That being said, good luck getting
it to run.

Regards,
Leo

[1] 
https://github.com/shadowsocks/shadowsocks/wiki/Configuration-via-Config-File

Message #11 received at 45856 <at> debbugs.gnu.org (full text, mbox):

From: musics <at> tutanota.com
To: 45856 <at> debbugs.gnu.org
Date: Fri, 15 Jan 2021 12:41:21 +0100 (CET)

[Message part 1 (text/plain, inline)]

Yes that's right. I'd better work with the shadowsocks-rust  or new packages... Thank you.

[Message part 2 (text/html, inline)]

Message #16 received at 45856-done <at> debbugs.gnu.org (full text, mbox):

From: musics <at> tutanota.com
To: 45856-done <at> debbugs.gnu.org
Subject: Done
Date: Fri, 15 Jan 2021 12:42:18 +0100 (CET)

[Message part 1 (text/plain, inline)]

Done

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.