 OK, thank you, everyone. Here is my presentation to introduce how to fight against the censorship using Japan languages. And it's alternative into other than for first and self introduction. I'm an arm holder, basically, and for the Japan install, to a few arm-based NASA devices. So maybe you already hear the talk that Vigran gave the other day that when doing full porting, usually it's related to some patches to the kernel and some patches to the devane installer itself. And in order to make it easier to port the GNOME screen to the devane installer, because it only has the theory concept of SSH connection during the install, so maybe when we like read it. I already did the talk last day talk. And second, I'm a package maintainer. I maintain a few packages like Shadow, Sox, EV, and these dependencies, some libraries. Today I'm going to talk about the package by maintainer. And here I want to say I'm not a security expert, so maybe there is some flow in the protocol or in the code. Just a shout out and the eye and the upstream maintainer can help. I want to say the problem to solve, the session, right? The session should have a few sets. Some is like a very large session, like you go into the cafe or restaurant just connected to the Wi-Fi, and you find your internet is hijacked. You are going to visit Google, but actually it's not Google. The data is through the other website, and then it has to go Google. So this is one kind of. The other kind of is when you travel to some certain countries, some countries in the middle or far east block there, just like Google, Gmail, Wikipedia, Facebook, Twitter, social network. Basically it doesn't work there. Here the real problem, why we cannot use those sites and why the internet is hijacked in the cafe. So the real problem is the DNS quality. You get the DNS, the result is not correct. The result is timed by the DNS server at the cafe or restaurant. And the second is the IP address of certain sites are blocked in some countries. And previously we know the problem and how to resolve it. Maybe you think we can use Tor. We just use Tor. But here is the standard for Tor. Tor is great because it can protect you from the privacy. It's not anonymous. And there is no required to reduce the account. And it's free of charge, which is great. But there are some problems on the Tor. It's slow, right? I confirmed with the Tor members here in their comment. And the Tor member told me, actually, Tor is not that slow. It just has some latency problem. But for video streaming 1080 HD should be OK. I tried, yes. In Canada, it's OK. But maybe in some countries, like heavily used package loss, QoS, the environment, it's not so good. So the video streaming maybe is the problem. And some Tor IP address are blocked in some part of this planet. For this case, Tor invented the bridge. But the end user need to collect the bridge. IP address of bridge themselves, I think, is not that positive for the real user. Let's talk about the scenario that Tor works well for some text-based application like Wikipedia or messaging, an email, and search engine Tor works quite good. But for Wikipedia editing or the video is not so good. So I'm going to talk about alternative ways to Tor. So if you buy a VPS account, which is very cheap currently, about five or $10 each month, so when you have the VPS account, now you can set up the accession term. I think maybe you have already tried that. Can I know how many of you have already tried the SSH channel? Oh, nearly half of you have already tried it. So this is very convenient, but this works only for the laptop or PC, not for mobile device like mobile phone or iPad. We have the second choice, it's OpenVPN. OpenVPN has some problems, like there's fingerprint in the negotiation stage, because the client and the server need to handshake. When handshake, they need to disclose some information in plain text, not equipped, like which cyber they use, which IP address. So it's not so IU way. And the last one is the Shadow Socks I'm going to talk about. Shadow Socks is basically the soft spot proxy. Traditional soft spot proxy is very simple, but here we can separate, we can split the server and the client. So you can install the server on the VPS, and on the client, on your PC, it connects to the server. You're using its own protocol and it's encrypted data. And you browse internet through the browser, right? So you set up the soft spot proxy in the browser. Because the cypher is pretty fine on both server and the client. It's pretty fine in the configuration part. It's no need to handshake. So there's no problem, as I said previously, about the OpenVPN. OpenVPN has a problem when handshake. So Shadow Socks just avoid that problem by not handshake at all. And originally, the Shadow Socks implementation was in Python. And now, it has a live EV port. So it's written in C language. So it's currently most widely used and used in PC, and even in the Wi-Fi router, the OpenWLT, and Android. And about one year ago, someone for the implementation to go language. So now, it's even on the windows. Support OS, the next, of course, OpenWLT, yes, and Android. For the iOS, they are an exception, because there is some application supported. But it's not open source. So if you want to volunteer your time, you can implement open source at the time. And there, I heard a story about the Shadow Socks because it's so effective by passing the network restriction. And the user base increased quickly. So some governments don't like it. And the agents want to kill the project by contacting to the author of the app. So the code author, by telling them, please shut down the code in the GitHub. So you can still see a message of code removed due to regulation on the GitHub page. You can check the project there. And now, the original Python implementation and the EVE port, Retain C, is already and enters Debian Archon. So I'm not afraid of losing the software now. And so the Debian is not a platform to include the Tor and the Shadow Socks to fight with censorship, but also an infrastructure to protect the software itself. So thank you very much, EVE. There are some advanced use about the Shadow Socks, like gate the script around the gateway, like open WIT, and some extension to work better on the package logs from the environment network. I'm going to skip this. Because we are running out of time. And the project is still growing. And we welcome new contributors, such as, I already mentioned, open source IOS client. And I think maybe you can help on the source for the order like any flaws in the protocol or any security fault in code. As I know, TrueCrypt already passed the code order. OK, thank you very much. Thanks very much, Monster. What's the distribution model for the Socks proxies addresses? Is it like something that's spread in private forums, stuff like that, and people share a single proxy? Or is it something where users are expected to set up their own proxy in a VPS that we train themselves? OK, this is a software. So you need to buy your own VPS and install that software on that VPS. So presumably, the target user base is rather tech-savvy, correct? Because if we run that service, the IP address is easy to get blocked. I think it's a merit, not a disadvantage. OK, thanks. OK, thank you. Questions? Not well. Please thank Roger for his talk. OK, thank you very much.