diff --git a/translated/tech/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md b/published/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md similarity index 67% rename from translated/tech/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md rename to published/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md index e93ae319a9..3afa479e52 100644 --- a/translated/tech/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md +++ b/published/20190429 How To Turn On And Shutdown The Raspberry Pi -Absolute Beginner Tip.md @@ -1,16 +1,18 @@ [#]: collector: (lujun9972) [#]: translator: (geekpi) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) +[#]: reviewer: (wxy) +[#]: publisher: (wxy) +[#]: url: (https://linux.cn/article-11245-1.html) [#]: subject: (How To Turn On And Shutdown The Raspberry Pi [Absolute Beginner Tip]) [#]: via: (https://itsfoss.com/turn-on-raspberry-pi/) [#]: author: (Chinmay https://itsfoss.com/author/chinmay/) -如何打开和关闭树莓派（新手教程） +如何打开和关闭树莓派（绝对新手） ====== -_ **简介：这个贴士教你如何打开树莓派以及如何在之后正确关闭它。** _ +> 这篇短文教你如何打开树莓派以及如何在之后正确关闭它。 + +![](https://img.linux.net.cn/data/attachment/album/201908/19/192825rlrjy3sj77j7j79y.jpg) [树莓派][1]是[最流行的 SBC（单板计算机）][2]之一。如果你对这个话题感兴趣，我相信你已经有了一个树莓派。我还建议你使用[其他树莓派配件][3]来开始使用你的设备。 @@ -26,12 +28,14 @@ _ **简介：这个贴士教你如何打开树莓派以及如何在之后正确 micro USB 口为树莓派供电，打开它的方式是将电源线插入 micro USB 口。但是开始之前，你应该确保做了以下事情。 - * 根据官方[指南][8]准备带有 Raspbian 的 micro SD 卡并插入 micro SD 卡插槽。 -  * 插入 HDMI 线、USB 键盘和鼠标。 -  * 插入以太网线（可选）。 +* 根据官方[指南][8]准备带有 Raspbian 的 micro SD 卡并插入 micro SD 卡插槽。 +* 插入 HDMI 线、USB 键盘和鼠标。 +* 插入以太网线（可选）。 成上述操作后，请插入电源线。这会打开树莓派，显示屏将亮起并加载操作系统。 +如果您将其关闭并且想要再次打开它，则必须从电源插座（首选）或从电路板的电源端口拔下电源线，然后再插上。它没有电源按钮。 + ### 关闭树莓派 关闭树莓派非常简单，单击菜单按钮并选择关闭。 @@ -44,9 +48,11 @@ micro USB 口为树莓派供电，打开它的方式是将电源线插入 micro sudo shutdown now ``` -shutdown 执行后**等待**它完成，接着你可以关闭电源。树莓派关闭后，没有真正的办法可以在不重新打开电源的情况下打开树莓派。你可以使用 GPIO 打开树莓派，但这需要额外的改装。 +`shutdown` 执行后**等待**它完成，接着你可以关闭电源。 -_注意：Micro USB 口往往是脆弱的，因此请关闭/打开电源，而不是经常拔出插入 micro USB 口。_ +再说一次，树莓派关闭后，没有真正的办法可以在不关闭再打开电源的情况下打开树莓派。你可以使用 GPIO 打开树莓派，但这需要额外的改装。 + +*注意：Micro USB 口往往是脆弱的，因此请关闭/打开电源，而不是经常拔出插入 micro USB 口。 好吧，这就是关于打开和关闭树莓派的所有内容，你打算用它做什么？请在评论中告诉我。 @@ -57,13 +63,14 @@ via: https://itsfoss.com/turn-on-raspberry-pi/ 作者：[Chinmay][a] 选题：[lujun9972][b] 译者：[geekpi](https://github.com/geekpi) -校对：[校对者ID](https://github.com/校对者ID) +校对：[wxy](https://github.com/wxy) 本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 [a]: https://itsfoss.com/author/chinmay/ [b]: https://github.com/lujun9972 [1]: https://www.raspberrypi.org/ +[2]: https://linux.cn/article-10823-1.html [3]: https://itsfoss.com/things-you-need-to-get-your-raspberry-pi-working/ [7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/04/raspberry-pi-3-microusb.png?fit=800%2C532&ssl=1 [8]: https://www.raspberrypi.org/documentation/installation/installing-images/README.md diff --git a/published/20190815 SSLH - Share A Same Port For HTTPS And SSH.md b/published/20190815 SSLH - Share A Same Port For HTTPS And SSH.md new file mode 100644 index 0000000000..88bbbfc21a --- /dev/null +++ b/published/20190815 SSLH - Share A Same Port For HTTPS And SSH.md @@ -0,0 +1,205 @@ +[#]: collector: (lujun9972) +[#]: translator: (wxy) +[#]: reviewer: (wxy) +[#]: publisher: (wxy) +[#]: url: (https://linux.cn/article-11247-1.html) +[#]: subject: (SSLH – Share A Same Port For HTTPS And SSH) +[#]: via: (https://www.ostechnix.com/sslh-share-port-https-ssh/) +[#]: author: (sk https://www.ostechnix.com/author/sk/) + +SSLH：让 HTTPS 和 SSH 共享同一个端口 +====== + +![SSLH - Share A Same Port For HTTPS And SSH][1] + +一些 ISP 和公司可能已经阻止了大多数端口，并且只允许少数特定端口（如端口 80 和 443）访问来加强其安全性。在这种情况下，我们别无选择，但同一个端口可以用于多个程序，比如 HTTPS 端口 443，很少被阻止。通过 SSL/SSH 多路复用器 SSLH 的帮助，它可以侦听端口 443 上的传入连接。更简单地说，SSLH 允许我们在 Linux 系统上的端口 443 上运行多个程序/服务。因此，你可以同时通过同一个端口同时使用 SSL 和 SSH。如果你遇到大多数端口被防火墙阻止的情况，你可以使用 SSLH 访问远程服务器。这个简短的教程描述了如何在类 Unix 操作系统中使用 SSLH 让 https、ssh 共享相同的端口。 + +### SSLH：让 HTTPS、SSH 共享端口 + +#### 安装 SSLH + +大多数 Linux 发行版上 SSLH 都有软件包，因此你可以使用默认包管理器进行安装。 + +在 Debian、Ubuntu 及其衍生品上运行： + +``` +$ sudo apt-get install sslh +``` + +安装 SSLH 时，将提示你是要将 sslh 作为从 inetd 运行的服务，还是作为独立服务器运行。每种选择都有其自身的优点。如果每天只有少量连接，最好从 inetd 运行 sslh 以节省资源。另一方面，如果有很多连接，sslh 应作为独立服务器运行，以避免为每个传入连接生成新进程。 + +![][2] + +*安装 sslh* + +在 Arch Linux 和 Antergos、Manjaro Linux 等衍生品上，使用 Pacman 进行安装，如下所示： + +``` +$ sudo pacman -S sslh +``` + +在 RHEL、CentOS 上，你需要添加 EPEL 存储库，然后安装 SSLH，如下所示： + +``` +$ sudo yum install epel-release +$ sudo yum install sslh +``` + +在 Fedora： + +``` +$ sudo dnf install sslh +``` + +如果它在默认存储库中不可用，你可以如[这里][3]所述手动编译和安装 SSLH。 + +#### 配置 Apache 或 Nginx Web 服务器 + +如你所知，Apache 和 Nginx Web 服务器默认会监听所有网络接口（即 `0.0.0.0:443`）。我们需要更改此设置以告知 Web 服务器仅侦听 `localhost` 接口（即 `127.0.0.1:443` 或 `localhost:443`）。 + +为此，请编辑 Web 服务器（nginx 或 apache）配置文件并找到以下行： + +``` +listen 443 ssl; +``` + +将其修改为： + +``` +listen 127.0.0.1:443 ssl; +``` + +如果你在 Apache 中使用虚拟主机，请确保你也修改了它。 + +``` +VirtualHost 127.0.0.1:443 +``` + +保存并关闭配置文件。不要重新启动该服务。我们还没有完成。 + +#### 配置 SSLH + +使 Web 服务器仅在本地接口上侦听后，编辑 SSLH 配置文件： + +``` +$ sudo vi /etc/default/sslh +``` + +找到下列行： + +``` +Run=no +``` + +将其修改为： + +``` +Run=yes +``` + +然后，向下滚动一点并修改以下行以允许 SSLH 在所有可用接口上侦听端口 443（例如 `0.0.0.0:443`）。 + +``` +DAEMON_OPTS="--user sslh --listen 0.0.0.0:443 --ssh 127.0.0.1:22 --ssl 127.0.0.1:443 --pidfile /var/run/sslh/sslh.pid" +``` + +这里， + + * `–user sslh`：要求在这个特定的用户身份下运行。 + * `–listen 0.0.0.0:443`：SSLH 监听于所有可用接口的 443 端口。 + * `–sshs 127.0.0.1:22` : 将 SSH 流量路由到本地的 22 端口。 + * `–ssl 127.0.0.1:443` : 将 HTTPS/SSL 流量路由到本地的 443 端口。 + +保存并关闭文件。 + +最后，启用并启动 `sslh` 服务以更新更改。 + +``` +$ sudo systemctl enable sslh +$ sudo systemctl start sslh +``` + +#### 测试 + +检查 SSLH 守护程序是否正在监听 443。 + +``` +$ ps -ef | grep sslh +sslh 2746 1 0 15:51 ? 00:00:00 /usr/sbin/sslh --foreground --user sslh --listen 0.0.0.0 443 --ssh 127.0.0.1 22 --ssl 127.0.0.1 443 --pidfile /var/run/sslh/sslh.pid +sslh 2747 2746 0 15:51 ? 00:00:00 /usr/sbin/sslh --foreground --user sslh --listen 0.0.0.0 443 --ssh 127.0.0.1 22 --ssl 127.0.0.1 443 --pidfile /var/run/sslh/sslh.pid +sk 2754 1432 0 15:51 pts/0 00:00:00 grep --color=auto sslh +``` + +现在，你可以使用端口 443 通过 SSH 访问远程服务器： + +``` +$ ssh -p 443 [email protected] +``` + +示例输出： + +``` +[email protected]'s password: +Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-55-generic x86_64) + +* Documentation: https://help.ubuntu.com +* Management: https://landscape.canonical.com +* Support: https://ubuntu.com/advantage + +System information as of Wed Aug 14 13:11:04 IST 2019 + +System load: 0.23 Processes: 101 +Usage of /: 53.5% of 19.56GB Users logged in: 0 +Memory usage: 9% IP address for enp0s3: 192.168.225.50 +Swap usage: 0% IP address for enp0s8: 192.168.225.51 + +* Keen to learn Istio? It's included in the single-package MicroK8s. + +https://snapcraft.io/microk8s + +61 packages can be updated. +22 updates are security updates. + + +Last login: Wed Aug 14 13:10:33 2019 from 127.0.0.1 +``` + +![][4] + +*通过 SSH 使用 443 端口访问远程系统* + +看见了吗？即使默认的 SSH 端口 22 被阻止，我现在也可以通过 SSH 访问远程服务器。正如你在上面的示例中所看到的，我使用 https 端口 443 进行 SSH 连接。 + +我在我的 Ubuntu 18.04 LTS 服务器上测试了 SSLH，它如上所述工作得很好。我在受保护的局域网中测试了 SSLH，所以我不知道是否有安全问题。如果你在生产环境中使用它，请在下面的评论部分中告诉我们使用 SSLH 的优缺点。 + +有关更多详细信息，请查看下面给出的官方 GitHub 页面。 + +资源： + +* [SSLH GitHub 仓库][12] + +-------------------------------------------------------------------------------- + +via: https://www.ostechnix.com/sslh-share-port-https-ssh/ + +作者：[sk][a] +选题：[lujun9972][b] +译者：[wxy](https://github.com/wxy) +校对：[wxy](https://github.com/wxy) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://www.ostechnix.com/author/sk/ +[b]: https://github.com/lujun9972 +[1]: https://www.ostechnix.com/wp-content/uploads/2017/08/SSLH-Share-A-Same-Port-For-HTTPS-And-SSH-1-720x340.jpg +[2]: https://www.ostechnix.com/wp-content/uploads/2017/08/install-sslh.png +[3]: https://github.com/yrutschle/sslh/blob/master/doc/INSTALL.md +[4]: https://www.ostechnix.com/wp-content/uploads/2017/08/Access-remote-systems-via-SSH-using-port-443.png +[5]: https://www.ostechnix.com/how-to-ssh-into-a-particular-directory-on-linux/ +[6]: https://www.ostechnix.com/how-to-create-ssh-alias-in-linux/ +[7]: https://www.ostechnix.com/configure-ssh-key-based-authentication-linux/ +[8]: https://www.ostechnix.com/how-to-stop-ssh-session-from-disconnecting-in-linux/ +[9]: https://www.ostechnix.com/allow-deny-ssh-access-particular-user-group-linux/ +[10]: https://www.ostechnix.com/4-ways-keep-command-running-log-ssh-session/ +[11]: https://www.ostechnix.com/scanssh-fast-ssh-server-open-proxy-scanner/ +[12]: https://github.com/yrutschle/sslh diff --git a/sources/tech/20181202 How To Customize The GNOME 3 Desktop.md b/sources/tech/20181202 How To Customize The GNOME 3 Desktop.md index 91c16e4e99..84b8ab119d 100644 --- a/sources/tech/20181202 How To Customize The GNOME 3 Desktop.md +++ b/sources/tech/20181202 How To Customize The GNOME 3 Desktop.md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: (robsean) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: subject: (How To Customize The GNOME 3 Desktop?) diff --git a/sources/tech/20190815 SSLH - Share A Same Port For HTTPS And SSH.md b/sources/tech/20190815 SSLH - Share A Same Port For HTTPS And SSH.md deleted file mode 100644 index f7cc8ef1f3..0000000000 --- a/sources/tech/20190815 SSLH - Share A Same Port For HTTPS And SSH.md +++ /dev/null @@ -1,227 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: ( ) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (SSLH – Share A Same Port For HTTPS And SSH) -[#]: via: (https://www.ostechnix.com/sslh-share-port-https-ssh/) -[#]: author: (sk https://www.ostechnix.com/author/sk/) - -SSLH – Share A Same Port For HTTPS And SSH -====== - -![SSLH - Share A Same Port For HTTPS And SSH][1] - -Some Internet service providers and corporate companies might have blocked most of the ports, and allowed only a few specific ports such as port 80 and 443 to tighten their security. In such cases, we have no choice, but use a same port for multiple programs, say the HTTPS Port **443** , which is rarely blocked. Here is where **SSLH** , a SSL/SSH multiplexer, comes in help. It will listen for incoming connections on a port 443. To put this more simply, SSLH allows us to run several programs/services on port 443 on a Linux system. So, you can use both SSL and SSH using a same port at the same time. If you ever been in a situation where most ports are blocked by the firewalls, you can use SSLH to access your remote server. This brief tutorial describes how to share a same port for https, ssh using SSLH in Unix-like operating systems. - -### SSLH – Share A Same Port For HTTPS, SSH, And OpenVPN - -##### Install SSLH - -SSLH is packaged for most Linux distributions, so you can install it using the default package managers. - -On **Debian** , **Ubuntu** , and derivatives, run: - -``` -$ sudo apt-get install sslh -``` - -While installing SSLH, you will prompted whether you want to run sslh as a service from inetd, or as a standalone server. Each choice has its own benefits. With only a few connection per day, it is probably better to run sslh from inetd in order to save resources. On the other hand, with many connections, sslh should run as a standalone server to avoid spawning a new process for each incoming connection. - -![][2] - -Install sslh - -On **Arch Linux** and derivatives like Antergos, Manjaro Linux, install it using Pacman as shown below. - -``` -$ sudo pacman -S sslh -``` - -On **RHEL** , **CentOS** , you need to add **EPEL** repository and then install SSLH as shown below. - -``` -$ sudo yum install epel-release - -$ sudo yum install sslh -``` - -On **Fedora** : - -``` -$ sudo dnf install sslh -``` - -If it is not available on default repositories, you can manually compile and install SSLH as described [**here**][3]. - -##### Configure Apache or Nginx webservers - -As you already know, Apache and Nginx webservers will listen on all network interfaces (i.e **0.0.0.0:443** ) by default. We need to change this setting to tell the webserver to listen on the localhost interface only (i.e **127.0.0.1:443 **or **localhost:443** ). - -To do so, edit the webserver (nginx or apache) configuration file and find the following line: - -``` -listen 443 ssl; -``` - -And, change it to: - -``` -listen 127.0.0.1:443 ssl; -``` - -If you’re using Virutalhosts in Apache, make sure you have changed that it too. - -``` -VirtualHost 127.0.0.1:443 -``` - -Save and close the config files. Do not restart the services. We haven’t finished yet. - -##### Configure SSLH - -Once you have made the webservers to listen on local interface only, edit SSLH config file: - -``` -$ sudo vi /etc/default/sslh -``` - -Find the following line: - -``` -Run=no -``` - -And, change it to: - -``` -Run=yes -``` - -Then, scroll a little bit down and modify the following line to allow SSLH to listen on port 443 on all available interfaces (Eg. 0.0.0.0:443). - -``` -DAEMON_OPTS="--user sslh --listen 0.0.0.0:443 --ssh 127.0.0.1:22 --ssl 127.0.0.1:443 --pidfile /var/run/sslh/sslh.pid" -``` - -Where, - - * –user sslh : Requires to run under this specified username. - * –listen 0.0.0.0:443 : SSLH is listening on port 443 on all available interfaces. - * –sshs 127.0.0.1:22 : Route SSH traffic to port 22 on the localhost. - * –ssl 127.0.0.1:443 : Route HTTPS/SSL traffic to port 443 on the localhost. - - - -Save and close the file. - -Finally, enable and start sslh service to update the changes. - -``` -$ sudo systemctl enable sslh - -$ sudo systemctl start sslh -``` - -##### Testing - -Check if the SSLH daemon is listening to 443. - -``` -$ ps -ef | grep sslh -sslh 2746 1 0 15:51 ? 00:00:00 /usr/sbin/sslh --foreground --user sslh --listen 0.0.0.0 443 --ssh 127.0.0.1 22 --ssl 127.0.0.1 443 --pidfile /var/run/sslh/sslh.pid -sslh 2747 2746 0 15:51 ? 00:00:00 /usr/sbin/sslh --foreground --user sslh --listen 0.0.0.0 443 --ssh 127.0.0.1 22 --ssl 127.0.0.1 443 --pidfile /var/run/sslh/sslh.pid -sk 2754 1432 0 15:51 pts/0 00:00:00 grep --color=auto sslh -``` - -Now, you can access your remote server via SSH using port 443: - -``` -$ ssh -p 443 [email protected] -``` - -**Sample output:** - -``` -[email protected]'s password: -Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-55-generic x86_64) - -* Documentation: https://help.ubuntu.com -* Management: https://landscape.canonical.com -* Support: https://ubuntu.com/advantage - -System information as of Wed Aug 14 13:11:04 IST 2019 - -System load: 0.23 Processes: 101 -Usage of /: 53.5% of 19.56GB Users logged in: 0 -Memory usage: 9% IP address for enp0s3: 192.168.225.50 -Swap usage: 0% IP address for enp0s8: 192.168.225.51 - -* Keen to learn Istio? It's included in the single-package MicroK8s. - -https://snapcraft.io/microk8s - -61 packages can be updated. -22 updates are security updates. - - -Last login: Wed Aug 14 13:10:33 2019 from 127.0.0.1 -``` - -![][4] - -Access remote systems via SSH using port 443 - -See? I can now be able to access the remote server via SSH even if the default SSH port 22 is blocked. As you see in the above example, I have used the https port 443 for SSH connection. Also, we can use the same port 443 for openVPN connections too. - -* * * - -**Suggested read:** - - * [**How To SSH Into A Particular Directory On Linux**][5] - * [**How To Create SSH Alias In Linux**][6] - * [**How To Configure SSH Key-based Authentication In Linux**][7] - * [**How To Stop SSH Session From Disconnecting In Linux**][8] - * [**Allow Or Deny SSH Access To A Particular User Or Group In Linux**][9] - * [**4 Ways To Keep A Command Running After You Log Out Of The SSH Session**][10] - * [**ScanSSH – Fast SSH Server And Open Proxy Scanner**][11] - - - -* * * - -I tested SSLH on my Ubuntu 18.04 LTS server and it worked just fine as described above. I tested SSLH in a protected local area network, so I am not aware of the security issues. If you’re using it in production, let us know the advantages and disadvantages of using SSLH in the comment section below. - -For more details, check the official GitHub page given below. - -**Resource:** - - * [**SSLH GitHub Repository**][12] - - - --------------------------------------------------------------------------------- - -via: https://www.ostechnix.com/sslh-share-port-https-ssh/ - -作者：[sk][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://www.ostechnix.com/author/sk/ -[b]: https://github.com/lujun9972 -[1]: https://www.ostechnix.com/wp-content/uploads/2017/08/SSLH-Share-A-Same-Port-For-HTTPS-And-SSH-1-720x340.jpg -[2]: https://www.ostechnix.com/wp-content/uploads/2017/08/install-sslh.png -[3]: https://github.com/yrutschle/sslh/blob/master/doc/INSTALL.md -[4]: https://www.ostechnix.com/wp-content/uploads/2017/08/Access-remote-systems-via-SSH-using-port-443.png -[5]: https://www.ostechnix.com/how-to-ssh-into-a-particular-directory-on-linux/ -[6]: https://www.ostechnix.com/how-to-create-ssh-alias-in-linux/ -[7]: https://www.ostechnix.com/configure-ssh-key-based-authentication-linux/ -[8]: https://www.ostechnix.com/how-to-stop-ssh-session-from-disconnecting-in-linux/ -[9]: https://www.ostechnix.com/allow-deny-ssh-access-particular-user-group-linux/ -[10]: https://www.ostechnix.com/4-ways-keep-command-running-log-ssh-session/ -[11]: https://www.ostechnix.com/scanssh-fast-ssh-server-open-proxy-scanner/ -[12]: https://github.com/yrutschle/sslh