Why do we base64 encode Shadowsocks URL? about shadowsocks-org HOT 7 CLOSED

For better exchange, I guess.

The base64 encoded string is simple to handle because it's all in human readable characters. Which means, it can be handled by any electronic device.

from shadowsocks-org.

The short story is we don't want the URL to be searchable, which seems not necessary today.

Then, it's been fixed via SIP002, #27 (comment)

from shadowsocks-org.

from shadowsocks-org.

I don't get it. The base64 encoded "URI" still has the ss:// scheme prefix, so still searchable?

Just finished reading SIP002. Feels like this is still a work-in-progress? What's the plan? I was working on simplifying the command line arguments. Instead of taking separate arguments for cipher/password/host/port, it could take a plain URL as a whole, e.g.

go-shadowsocks2 -c ss://aes-128-gcm:your-password@[server_address]:8488

and then I'm puzzled by the base64-encoded format.

from shadowsocks-org.

@Mygod has finalized the new schema in this comment: #27 (comment).

Now, only the cipher name and password are encoded in URL-safe BASE64 in case we need to support key file directly in the URL.

from shadowsocks-org.

@riobard Hmm, most of search engine doesn't support search the URL schema directly, e.g. https://www.google.com.hk/search?q="ss%3A%2F%2F".

Anyway, I agree it's not necessary at all.

from shadowsocks-org.

I see. Let's continue the discussion under SIP002.

from shadowsocks-org.