Skip to content
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

obfs option in json config file #1029

Closed
cokebar opened this issue Jan 3, 2017 · 2 comments
Closed

obfs option in json config file #1029

cokebar opened this issue Jan 3, 2017 · 2 comments

Comments

@cokebar
Copy link

cokebar commented Jan 3, 2017

What version of shadowsocks-libev are you using?

2.6.0

What operating system are you using?

Ubuntu 16.04/Windows7/Windows10

What did you do?

I'm not sure if obfs is enabled or not when set in json config file.

What did you expect to see?

A log shall be given out: obfuscating enabled

What did you see instead?

Ss will give out " obfuscating enabled" when obfs is enabled by command line:
ss-server(or ss-local) --obfs tls -s X.X.X.X -p XXXX ...

But when obfs is set in config.json like this:
"obfs":"tls"
there's no log given out about whether obfs is enabled.
I don't know if it is correct to set obfs like this in json file.

What is your config in detail (with all sensitive info masked)?

{
"server":"X.X.X.X",
"server_port":9999,
"local_port":9999,
"password":"pass",
"method":"chacha20",
"auth":true,
"obfs":"tls",
"obfs_host":"live.com"
}

@madeye
Copy link

madeye commented Jan 3, 2017

It should be a bug of log. However, as obfs is already deprecated, it won't be fixed in the future.

More details: shadowsocks/shadowsocks-org#26

@cokebar
Copy link
Author

cokebar commented Jan 3, 2017

thanks

@cokebar cokebar closed this as completed Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants