shadowsocks | Redirect attack on Shadowsocks stream ciphers | Proxy library

Replace:

It's not like there is any very specific guidance for -dev packages in general. The person who created the package created a debian/rules and its supporting infrastructure which builds two or more packages from the upstream package source, and decided to put some of those files in the -dev package so that people who only need the binary can install only the binary, and people who want more can install both packages.

Typically, the non-dev package installs the library file, and the -dev package contains C header files and/or similar resources for someone who wants to compile code which uses this library.

The Github project for this package contains the definitions in https://github.com/shadowsocks/shadowsocks-libev/tree/master/debian -- in particular, libshadowsocks-libev-dev.install installs the .so (probably a symlink) while libshadowsocks-libev2.install (the non-dev package) installs usr/lib/*/libshadowsocks-libev.so.* (i.e. the actual binary).

The README.md contains rather detailed instructions for building from source on Debian-based platforms.

It is possible as of mid-2019.

Start the line with # symbol. See the docs:

lines beginning with # are treated as comments.

For vlucas/phpdotenv the same situation.

delete -d in shell script

everything is ok

You would need to:

• configure shadowsocks for SSH traffic
• set your Git proxy accodingly

That is:

So, the problem you're having is that export does not REALLY capture a container (it just makes a tarball of the filesystem)- note that your new image has no entrypoint or command. That's what that error means- your container has no entrypoint specified, so it is interpreting -s 0.0.0.0 -p 12345 -k welcome -m aes-256-cfb。 as the entrypoint (and -s is not a valid command).

But... don't do this. Not sure what you're trying to accomplish, but its fighting the way the stuff works. If you need to modify a container, use a Dockerfile, build an image.

EDIT

To elaborate a bit- exporting a container (what you're doing) is a bad idea. Images, however are meant to be used this way. docker image save and docker image import are probably what you want- turn an image into a tarball, and then back into an image, with all the image metadata that was set up in the dockerfile preserved.

If you REALLY need to run a container and then move it, you can do docker commit to create a new image from a running container, followed by the save/import mentioned above.

the solution is: edit the VPS setting, vim /etc/hosts , under the vpi6, add below

Finally I found the solution!!! Because jupyter need the nginx to have websocket, so it will not work if you are using a general backproxy.

When you add proxy in the intellij IDEA it automatically adds the proxy in gradle.properties but when you remove it from settings it's still there. open gradle.properties and remove the proxy.

It should be something like this: