mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-15 01:50:08 +08:00
Merge pull request #11 from LCTT/master
preparing for seventh translation
This commit is contained in:
CanYellow
GitHub
commit
94736b37e8
@ -3,16 +3,18 @@
|
||||
[#]: author: "Sagar Sharma https://itsfoss.com/author/sagar/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15415-1.html"
|
||||
|
||||
我如何修复 Linux 中扬声器发出的嗡嗡声
|
||||
如何修复 Linux 中扬声器发出的嗡嗡声
|
||||
======
|
||||
|
||||
我使用笔记本电脑很长时间了，但最近才切换到桌面设置，以便在 It's FOSS 进行远程工作。
|
||||
![][0]
|
||||
|
||||
我注意到扬声器不断发出嗡嗡声。这很烦人，让我头疼。我开始着手解决这个问题。了解问题的根本原因非常有趣。
|
||||
我使用笔记本电脑很长时间了，但最近才切换到台式机上，以便进行远程工作。
|
||||
|
||||
我注意到我的扬声器不断发出嗡嗡声。这很烦人，让我头疼。我开始着手解决这个问题。了解问题的根本原因非常有趣。
|
||||
|
||||
我将分享我在 Linux 中修复扬声器嗡嗡声的经验。我发现它可以在同一硬件上对 Ubuntu、Debian 和 Pop OS 都有效。
|
||||
|
||||
@ -20,9 +22,9 @@
|
||||
|
||||
**在尝试修复之前**
|
||||
|
||||
我试图让事情变得容易安全地遵循。你尝试临时修复，如果有效，则将更改永久化。但是，最好使用 Timeshift 制作系统快照。如果你在出现故障时很容易惊慌失措，你可以将系统恢复到之前的状态。
|
||||
我试图让事情变得容易安全地遵循。你可以尝试临时修复，如果有效，则将更改永久化。但是，最好使用 Timeshift 制作系统快照。如果你在出现故障时很容易惊慌失措，你可以将系统恢复到之前的状态。
|
||||
|
||||
另外，检查你的声卡。在我的例子中，它是 snd_hda_intel。对于 USB 卡，它可以是 snd_usb_audio。你必须根据你的声卡更改命令。
|
||||
另外，检查你的声卡。在我的例子中，它是 `snd_hda_intel`。对于 USB 卡，它可以是 `snd_usb_audio`。你必须根据你的声卡更改命令。
|
||||
|
||||
```
|
||||
cat /proc/asound/modules
|
||||
@ -32,7 +34,7 @@ cat /proc/asound/modules
|
||||
|
||||
梳理了无数的论坛帖子和网站后，我了解了问题的根本原因。这是因为扬声器中的电容放电。它可以通过关闭声卡的省电设置来解决。
|
||||
|
||||
通过关闭省电，你允许系统在这些电容放电时为其充电。这类似于在不断充电时使用电话。
|
||||
通过关闭省电，你允许系统在这些电容放电时为其充电。这类似于在一直充电时使用电话。
|
||||
|
||||
你可以使用给定的命令检查你的系统是否启用了声卡的省电设置：
|
||||
|
||||
@ -42,13 +44,13 @@ cat /sys/module/snd_hda_intel/parameters/power_save
|
||||
|
||||
![power saving setting in sound card making buzzing sound in linux][1]
|
||||
|
||||
如果你像我一样输出是 1，那么省电功能已打开。因此，让我们看一下方案。
|
||||
如果你像我一样输出是 `1`，那么省电功能已打开。因此，让我们看一下方案。
|
||||
|
||||
不用担心。这不会显著影响你的电池百分比，因为所示方法仅适用于声卡。
|
||||
|
||||
### 尝试修复嗡嗡声问题（临时）
|
||||
|
||||
我之所以包括临时方法是为了确定嗡嗡声是由于电容放电引起的还是是否存在任何严重的硬件问题。
|
||||
我之所以包括临时方法是为了确定嗡嗡声是由于电容放电引起的，还是存在严重的硬件问题。
|
||||
|
||||
如果此临时方案有效，你可以继续使用永久方案。
|
||||
|
||||
@ -64,7 +66,7 @@ sudo su
|
||||
echo 0 > /sys/module/snd_hda_intel/parameters/power_save
|
||||
```
|
||||
|
||||
如果你使用的是 **USB 声卡**，则必须将 `snd_hda_intel` 与 `snd_usb_audio` 互换，如下所示：
|
||||
如果你使用的是 **USB 声卡**，则必须将 `snd_hda_intel` 替换为 `snd_usb_audio`，如下所示：
|
||||
|
||||
```
|
||||
echo 0 > /sys/module/snd_usb_audio/parameters/power_save
|
||||
@ -76,7 +78,7 @@ echo 0 > /sys/module/snd_usb_audio/parameters/power_save
|
||||
|
||||
在这里，我将对内核参数进行更改。
|
||||
|
||||
将你的工作目录更改为 /etc/modprobe.d：
|
||||
将你的工作目录更改为 `/etc/modprobe.d`：
|
||||
|
||||
```
|
||||
cd /etc/modprobe.d
|
||||
@ -96,13 +98,13 @@ options snd_hda_intel power_save=0
|
||||
|
||||
![fix buzzing sound in linux][2]
|
||||
|
||||
对于 **USB 声卡**，你可以使用 `snd_usb_audio`：
|
||||
对于 **USB 声卡**，你需要使用 `snd_usb_audio`：
|
||||
|
||||
```
|
||||
options snd_usb_audio power_save=0
|
||||
```
|
||||
|
||||
现在，[保存更改并退出 Nano 文本编辑器][3]并按 Ctrl+X 键。重启你的系统，你就可以享受无噪音的工作空间。
|
||||
现在，[保存更改并退出 Nano 文本编辑器][3] 并按 `Ctrl+X` 键。重启你的系统，你就可以享受无噪音的工作空间。
|
||||
|
||||
### 总结
|
||||
|
||||
@ -119,12 +121,13 @@ via: https://itsfoss.com/buzzing-noise-speaker-linux
|
||||
作者：[Sagar Sharma][a]
|
||||
选题：[lkxed][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/sagar/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/wp-content/uploads/2022/11/power-saving-setting-in-sound-card-making-buzzing-sound-in-linux.png
|
||||
[2]: https://itsfoss.com/wp-content/uploads/2022/11/fix-buzzing-sound-in-linux.png
|
||||
[1]: https://itsfoss.com/content/images/wordpress/2022/11/power-saving-setting-in-sound-card-making-buzzing-sound-in-linux.png
|
||||
[2]: https://itsfoss.com/content/images/wordpress/2022/11/fix-buzzing-sound-in-linux.png
|
||||
[3]: https://linuxhandbook.com/nano-save-exit/
|
||||
[0]: https://img.linux.net.cn/data/attachment/album/202301/05/150250sqbeq35bh699r157.jpg
|
||||
@ -0,0 +1,68 @@
|
||||
[#]: subject: "Official Fedora Budgie & Sway Spins to Arrive With Fedora 38 Release"
|
||||
[#]: via: "https://news.itsfoss.com/fedora-budgie-sway-official/"
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "wxy"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15418-1.html"
|
||||
|
||||
Fedora 38 将发布 Budgie 和 Sway 官方定制版
|
||||
======
|
||||
|
||||
> 两款新的 Fedora 定制版将在 Fedora 38 发布时首次亮相。
|
||||
|
||||
![][1]
|
||||
|
||||
我们期待着它们在 Fedora 37 时出现，但在 Fedora 38 中终于来了！
|
||||
|
||||
早在 2022 年 5 月，Budgie 项目的主要开发者 Joshua Strobl [宣布][2]，Budgie 已被提交到 Fedora 中。
|
||||
|
||||
遗憾的是，在那之后不久，我们并没有看到任何官方 [Fedora 定制版][3] 发布的迹象，尽管它在 [Fedora 37 发布][4] 期间进入了 Fedora 软件库。
|
||||
|
||||
**但现在有了。**
|
||||
|
||||
随着 Fedora 38 的发布，看起来我们会得到一个 [Budgie][5] 的官方定制版，同时还有一个 [Sway][6] 窗口管理器的定制版。
|
||||
|
||||
### Fedora Budgie 和 Sway
|
||||
|
||||
在 [最近的一次会议][9] 上，Fedora 工程和指导委员会（FESCo）投票决定将 Budgie 和 Sway 窗口管理器的 Fedora 官方定制版纳入 Fedora 38 的发布中。
|
||||
|
||||
根据 Budgie 和 Sway 的初步修改建议，我们可以期待很多变化。
|
||||
|
||||
对于 Budgie：
|
||||
|
||||
- Fedora 38 将提供 Budgie 桌面环境，包含一套核心应用程序，如用于更新/软件包管理的 GNOME “软件”应用、一个文本编辑器、一个网页浏览器和一个终端。
|
||||
- 它还将使用 [Materia GTK][10] 和 [Papirus][11] 图标主题，整个系统采用 GTK 主题设计。
|
||||
- Budgie 定制版还将采用 lightdm + slick-gtk-greeter，以获得更直观的用户问候体验。
|
||||
|
||||
对于 Sway 定制版：它旨在提供一个极简体验，只包括默认配置之上的一些元素。
|
||||
|
||||
预期时间：随着 Fedora 38 的开发在未来几个月内的加快，你可以期待这些定制版在 2023 年 4 月期间出现。当然，会有预装了 Budgie 和 Sway 的单独 ISO 文件。
|
||||
|
||||
因此，我认为看到 Budgie 与 Fedora 的体验会非常吸引人，特别是当 Budgie 的开发似乎正在发生一些有趣的变化。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/fedora-budgie-sway-official/
|
||||
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/sourav/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w2000/2023/01/fedora-budgie-sway-spins-arrive.png
|
||||
[2]: https://www.reddit.com/r/Fedora/comments/uq3gah/budgie_desktop_has_now_been_submitted_for/
|
||||
[3]: https://spins.fedoraproject.org
|
||||
[4]: https://news.itsfoss.com/fedora-37-release/
|
||||
[5]: https://blog.buddiesofbudgie.org
|
||||
[6]: https://swaywm.org
|
||||
[7]: https://unlocator.com/favicon.ico
|
||||
[8]: https://unlocator.com/wp-content/uploads/2019/05/unlocatoricon.jpg
|
||||
[9]: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RNJZUX3ZI34DIX6E4PVDKYQWCOFDQ4UY/
|
||||
[10]: https://github.com/nana-4/materia-theme
|
||||
[11]: https://github.com/PapirusDevelopmentTeam/papirus-icon-theme
|
||||
@ -0,0 +1,83 @@
|
||||
[#]: subject: "Nitrux 2.6.0 Takes Bold Steps: Drops apt, Adds Flathub and Pipewire"
|
||||
[#]: via: "https://debugpointnews.com/nitrux-2-6-0-release/"
|
||||
[#]: author: "arindam https://debugpointnews.com/author/dpicubegmail-com/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "wxy"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15420-1.html"
|
||||
|
||||
Nitrux 2.6.0 大胆抛弃 apt
|
||||
======
|
||||
|
||||
![][1]
|
||||
|
||||
> Nitrux 2.6.0 带有 Flathub、默认支持的 Pipewire、最新内核和 KDE 框架。
|
||||
|
||||
![Nitrux 2.6.0 Desktop][2]
|
||||
|
||||
[Nitrux Linux][3] 是基于 Debian 的，它带有一个名为 NX 桌面的修改版的 KDE Plasma 桌面。这个独特的 Linux 发行版带来了一套自己的建立在 Maui kit 和 Qt 之上的 Nitrux 应用程序。Nitrux 是无 systemd 的，使用 OpenRC 作为启动系统。所有这些独特的功能和令人惊叹的外观，使它成为当今最好的 Linux 发行版之一。
|
||||
|
||||
Nitrux 2.6.0 被提升为一个主要版本，因为它对 12 月发布的 2.5.1 版本进行了关键的更新。
|
||||
|
||||
### Nitrux 2.6.0 的新内容
|
||||
|
||||
这个版本的一个主要重点是在 SDDM 显示管理器中引入 Plasma Wayland 会话。Wayland 还不是默认的，但可以作为选项选择。X11 仍然是默认的。我相信在下一个主要版本中 NItrux 团队可以默认启用 Wayland。
|
||||
|
||||
此外，现代声音管理器 Pipewire 现在是默认的，因为它已经在 Ubuntu 和 Fedora 中标准化了，而且感觉很稳定。由于有了 Pipewire，你的音频工作流程将变得更好。
|
||||
|
||||
Nitrux 2.6.0 还默认启用了最大的 Flatpak 应用程序仓库 - Flathub。这意味着你不需要再手动设置 Flatpak 和启用 Flathub。现在，Flatpak 应用程序的安装变得更加容易。
|
||||
|
||||
其他值得注意的变化包括：Nitrux 使根（/）分区成为不可变分区，以防止它被破坏，Samba 包现在是 Nitrux 默认安装的一部分，Calamares 安装程序有了一个定制的自动分区方案。
|
||||
|
||||
![Nitrux 2.6 安装自动分区][4]
|
||||
|
||||
从一开始，Nitrux 就倾向于为其整个桌面组件提供自包含的可执行文件。主要的选择是 AppImage 文件格式。在这个版本中，你会得到默认的 Flathub 环境，而流行的 apt 软件包管理器现在被放弃了。这可能会改变一些用户的工作流程，因为 `apt` 命令将无法工作；尽管它是基于 Debian 的。
|
||||
|
||||
因此，Nitrux 团队建议使用 Distrobox 容器来设置单独的环境，以便与 apt 一起使用。然而，对于普通用户来说，理解容器、不可变的根分区会有点困难。
|
||||
|
||||
![apt 被放弃][5]
|
||||
|
||||
讽刺的是 `apt` 会在安装时使用，因为 Calamares 需要它。然而，在安装完成后，它会被删除。
|
||||
|
||||
> 现场 ISO 中包括 APT 和 dpkg，但这是因为 Calamares 需要它们来完成安装，并将从安装的系统中删除。
|
||||
>
|
||||
> —— NITRUX TEAM
|
||||
|
||||
Nitrux 2.6.0 的核心是 liqurix 内核 6.1，以及游戏和多媒体功能。这个版本由 KDE Plasma 2.26.4、KDE Framework 5.101.0 和 Qt 5.15.7 LTS 驱动。
|
||||
|
||||
如果你想阅读更多信息，可以在 [这里][6] 找到详细的发布说明。
|
||||
|
||||
### 下载
|
||||
|
||||
你可以从以下页面下载这个版本。然而，没有可用的升级路径。因此，建议进行新的安装。
|
||||
|
||||
- [FOSS Torrents（Torrent）][7]
|
||||
- [Sourceforge（镜像）][8]
|
||||
- [OSDN（镜像）][9]
|
||||
|
||||
参考自 [发布公告][10]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://debugpointnews.com/nitrux-2-6-0-release/
|
||||
|
||||
作者：[arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://debugpointnews.com/author/dpicubegmail-com/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://debugpointnews.com/wp-content/uploads/2023/01/nitrux-head.jpg
|
||||
[2]: https://debugpointnews.com/wp-content/uploads/2023/01/Nitrux-2.6.0-Desktop.jpg
|
||||
[3]: https://nxos.org/
|
||||
[4]: https://debugpointnews.com/wp-content/uploads/2023/01/Nitrux-2.6-install-automatic-partition.jpg
|
||||
[5]: https://debugpointnews.com/wp-content/uploads/2023/01/Screenshot-from-2023-01-05-13-44-57.png
|
||||
[6]: https://nxos.org/notes/notes-nitrux-2-6-0
|
||||
[7]: https://fosstorrents.com/distributions/nitrux/
|
||||
[8]: https://sourceforge.net/projects/nitruxos/files/Release/ISO
|
||||
[9]: https://osdn.net/projects/nitrux/releases/p18379
|
||||
[10]: https://nxos.org/changelog/release-announcement-nitrux-2-6-0/
|
||||
@ -0,0 +1,100 @@
|
||||
[#]: subject: "Pinta 2.1 Release Introduces WebP Support. But You Can't Use It Yet Unfortunately"
|
||||
[#]: via: "https://news.itsfoss.com/pinta-2-1-release/"
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Pinta 2.1 Release Introduces WebP Support. But You Can't Use It Yet Unfortunately
|
||||
======
|
||||
|
||||
Pinta 2.1 comes with WebP support and various other useful improvements.
|
||||
|
||||
![Pinta 2.1 Release Introduces WebP Support. But You Can't Use It Yet Unfortunately][1]
|
||||
|
||||
Pinta is a free and open-source drawing app for Linux that offers a ton of features in a relatively small package.
|
||||
|
||||
It is one of the [best Linux tools for digital artists][2] available.
|
||||
|
||||
Its last major release was in January 2022, introducing improved Hi DPI support, GTK 3 port, and [more][3].
|
||||
|
||||
Marking 2023's first release, Pinta 2.1 promises to offer even further refinements.
|
||||
|
||||
**Notice the new Pinta icon in the image above? Well, that's one of the changes.**
|
||||
|
||||
Let's see how this release pans out.
|
||||
|
||||
### 🆕 What's New in Pinta 2.1?
|
||||
|
||||
![pinta 2.1][4]
|
||||
|
||||
[Pinta 2.1][5] is offering plenty of new improvements; some notable ones include:
|
||||
|
||||
- **WebP Support**
|
||||
- **Improved .ora Support**
|
||||
- **Enhanced Handles**
|
||||
- **Dark Mode**
|
||||
- **Improved File Dialog**
|
||||
- **Various Bug Fixes and Changes**
|
||||
|
||||
**WebP Support:** Pinta finally has support for WebP files, but it does not come out of the box. For Linux users, the [webp-pixbuf-loader][6]**dependency is required to enable WebP support.**
|
||||
|
||||
> 📋 Unfortunately, WebP support is not included in the Flatpak and Snap builds of Pinta 2.1. Even if you have that library installed on your system. So, you probably have to build it from the source or use WebP files on Windows/macOS only.
|
||||
|
||||
**Improved .ora Support:** With Pinta 2.1, hidden layers are now round-tripped properly for .ora files.
|
||||
|
||||
Furthermore, when you save a .ora file, a flattened image is now included in the archive.
|
||||
|
||||
It is like this because it is required by the spec to accommodate the viewer software.
|
||||
|
||||
**Enhanced Handles:** The selection move and shape control point handles are now more intuitive, especially when working on zoomed-in or small images.
|
||||
|
||||
**Dark Mode:** Pinta has finally received full support for dark mode across the app; all icons, toolbars, dialogs, etc., are now in high-res SVG format.
|
||||
|
||||
**Improved File Dialog:** The file dialog now uses MIME types on Linux, allowing valid image files with unknown extensions to be included in the image file filter.
|
||||
|
||||
**Various Bug Fixes and Changes:** Apart from the changes I listed above, here are some that are also worth mentioning:
|
||||
|
||||
- Upgraded to .NET 7.
|
||||
- New '**Transparency Mode**' in Gradient Tool.
|
||||
- Standard GTK about dialog.
|
||||
- The gradient tool now updates properly while drawing transparent colors.
|
||||
- The new screenshot command now uses the XDG portal.
|
||||
|
||||
If you want to go deep into the technical details of the release, head to its [release notes][7].
|
||||
|
||||
### 📥 Download Pinta 2.1
|
||||
|
||||
Pinta 2.1 is available in the [Snap store][8], as well as on [Flathub][9]. The repositories include an outdated back, so you can safely ignore it.
|
||||
|
||||
You can also try building it from the [source code][10] and explore other download options for Windows/macOS.
|
||||
|
||||
[Download Pinta 2.1][11]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/pinta-2-1-release/
|
||||
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/sourav/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w2000/2023/01/pinta-2-1-release.png
|
||||
[2]: https://itsfoss.com/best-linux-graphic-design-software/
|
||||
[3]: https://news.itsfoss.com/pinta-2-0-release/
|
||||
[4]: https://news.itsfoss.com/content/images/2023/01/Pinta_2.1.png
|
||||
[5]: https://www.pinta-project.com
|
||||
[6]: https://github.com/aruiz/webp-pixbuf-loader/
|
||||
[7]: https://github.com/PintaProject/Pinta/releases/tag/2.1
|
||||
[8]: https://snapcraft.io/pinta
|
||||
[9]: https://flathub.org/apps/details/com.github.PintaProject.Pinta
|
||||
[10]: https://github.com/PintaProject/Pinta
|
||||
[11]: https://www.pinta-project.com/releases/
|
||||
|
||||
@ -1,163 +0,0 @@
|
||||
[#]: subject: (Is Open-Source Software Secure?)
|
||||
[#]: via: (https://news.itsfoss.com/open-source-software-security/)
|
||||
[#]: author: (Ankush Das https://news.itsfoss.com/author/ankush/)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (CanYellow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
Is Open-Source Software Secure?
|
||||
======
|
||||
|
||||
Being someone who prefers [Linux for desktop][1] and encourages using open-source software, you may expect the answer to the question raised in the headline with a big “**Yes**“.
|
||||
|
||||
But I am not going to limit discussing the benefits of open-source software. Let us explore more!
|
||||
|
||||
Here, I plan to share my thoughts on if open-source software is secure and what are the things involved in it that make secure or insecure.
|
||||
|
||||
### Why Should You Care if Open-Source Software is Secure?
|
||||
|
||||
No matter whether you use [Linux][2] or any other operating system, you will be surrounded with open-source software in some way (directly/indirectly).
|
||||
|
||||
To give you an example, most of the proprietary software tools depend on some form of open-source libraries to make things work.
|
||||
|
||||
Furthermore, there is a reason why companies of various scale (including Google, Microsoft, and Facebook) rely on open-source software or contribute their resources to the open-source community in one way or the other.
|
||||
|
||||
Hence, the security of open-source software is something essential to know about.
|
||||
|
||||
### Myths About Open-Source Software Security
|
||||
|
||||
![][3]
|
||||
|
||||
While there are several arguments to pitch the cons of open-source software in terms of security, some of them just do not make any sense.
|
||||
|
||||
#### Anyone Can See & Exploit the Code
|
||||
|
||||
The code is accessible to everyone, yes. But just because you can see the code—does that mean anyone can exploit it?
|
||||
|
||||
**Not really.**
|
||||
|
||||
Even though anyone can create a fork (or copy) of the software, the original software cannot be manipulated easily.
|
||||
|
||||
Usually, the project maintainer (or a group of them) manage the code repository and accept the commits from contributors. The code is reviewed before approval. And no one can hijack the code just like that.
|
||||
|
||||
**It takes effort for an attacker to exploit a vulnerability or add malicious code in a software, no matter if it is open-source or closed source.**
|
||||
|
||||
#### Without Dedicated Resources, Security Breaks down
|
||||
|
||||
Many believe that without dedicated employees or a team for an open-source software, it is difficult to maintain security.
|
||||
|
||||
In contrast, with several types of contributors joining and leaving, the software gets more attention from a wide range of developers.
|
||||
|
||||
And they may be able to spot security issues better than a few employees assigned for a proprietary software.
|
||||
|
||||
Some projects from the likes of Mozilla have a dedicated team to effectively iron out security issues. Similarly, most of the successful open source projects have plenty of resources to dedicate for security.
|
||||
|
||||
Hence, the open-source software ecosystem is a mixed bag for security. Even without dedicated resources, the projects get help from various contributors, and some are profitable to a great extent which helps them dedicate more resources.
|
||||
|
||||
### Open Source Software is Secure: Here’s How
|
||||
|
||||
![][3]
|
||||
|
||||
Now that we have tackled the myths, let me highlight how open-source software deals with security issues.
|
||||
|
||||
In other words, the benefits in security with open-source software.
|
||||
|
||||
Not to forget, the perks of open-source software translate to some of the reasons why [Linux is better than Windows][4].
|
||||
|
||||
#### More Eyes Looking at the Code
|
||||
|
||||
Unlike a proprietary software, access to code is not limited to a few developers.
|
||||
|
||||
Some projects may even have thousands of developers watching the code, reviewing them, and flagging or fixing security issues.
|
||||
|
||||
And this gives an edge over closed-source software by having **the ability to identify issues quickly and addressing them as soon as possible.**
|
||||
|
||||
Not just limited to more developers, often enterprises get involved with open-source projects that they utilize. And when they do, they will also go through the code and review it.
|
||||
|
||||
This gives another source of external audit that may help improve the security of the software.
|
||||
|
||||
In contrast, with a closed-source software, a limited number of developers may not be able to find all kinds of security issues. And it may take them longer to fix all the issues one by one.
|
||||
|
||||
#### Community Decision Making to Prioritize Security Issues
|
||||
|
||||
The developers of a closed-source software may have certain restrictions and priorities as what to work on and when to resolve an issue.
|
||||
|
||||
However, in case of an open-source project, the community of contributors can prioritize and assign themselves what they want to work on and when to fix an issue. You do not need to depend on a vendor or follow their instructions to address a security issue.
|
||||
|
||||
The decision making that goes into addressing and fixing the security issues is more transparent and flexible in case of an open-source software. Hence, it can prove to be more effective leaving you with three specific benefits:
|
||||
|
||||
* **Transparency**
|
||||
* **No dependency on the vendor**
|
||||
* **Faster security updates**
|
||||
|
||||
|
||||
|
||||
### Open Source Software is not Bulletproof: Here’s Why
|
||||
|
||||
![][3]
|
||||
|
||||
While there are cases where open-source software may get an edge for security, there could be instances or factors that affects it.
|
||||
|
||||
It is important to acknowledge that these problems exist, accordingly, an enterprise or an individual can make better decision about the state of security for an open-source software.
|
||||
|
||||
#### Not enough Eyes to Review Code and Uncertainty
|
||||
|
||||
Even if the code is accessible the world of developers, there are chances that a **project does not have enough contributors/developers to thoroughly review the code**.
|
||||
|
||||
In that case, we cannot have great confidence of an open-source software being peer-reviewed, because it lacks exactly that.
|
||||
|
||||
The open-source software may “claim” to have the best security just because its open-source, which is misleading when there are not enough developers working on it.
|
||||
|
||||
Also, we do not know how many developers are looking/reviewing the code and how exactly the code walkthrough is going on.
|
||||
|
||||
For instance, the Heartbleed bug was spotted after 2 years of its introduction in a project that was already popular i.e **OpenSSL**.
|
||||
|
||||
#### Software Responsibility or Accountability
|
||||
|
||||
This may not be important for individuals, but an **open-source software often comes with no warranties**.
|
||||
|
||||
So, if a business uses it, they must take the responsibility of any losses or damages caused by the use of that software.
|
||||
|
||||
This is something that tells you that nothing can be 100% secure and bug-free. No matter how many eyes you have on a code, or how skilled the contributors are, there will be risks in some form, be it security or data loss.
|
||||
|
||||
And this brings us to the fact that open-source software is not bulletproof.
|
||||
|
||||
### Open Source May Have its Edge for Better Security But…
|
||||
|
||||
Nothing is superior when it comes to security. No matter if it is closed-source or open-source, the same set of principles apply when it comes to security.
|
||||
|
||||
There are various external factors that can affect the security of a software, and **many of those are not source dependent**.
|
||||
|
||||
The code must be monitored in the same way to keep things secure.
|
||||
|
||||
Yes, the **open-source approach introduces benefits that closed-source software will never have**, but that does not mean that it is bulletproof.
|
||||
|
||||
_What do you think about the state of security when it comes to open-source software?_ _Do you think it is superior to proprietary solutions?_
|
||||
|
||||
I would appreciate your valuable thoughts in the comments down below.
|
||||
|
||||
#### Big Tech Websites Get Millions in Revenue, It's FOSS Got You!
|
||||
|
||||
If you like what we do here at It's FOSS, please consider making a donation to support our independent publication. Your support will help us keep publishing content focusing on desktop Linux and open source software.
|
||||
|
||||
I'm not interested
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/open-source-software-security/
|
||||
|
||||
作者：[Ankush Das][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://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://news.itsfoss.com/linux-foundation-linux-desktop/
|
||||
[2]: https://itsfoss.com/what-is-linux-distribution/
|
||||
[3]: data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjQzOSIgd2lkdGg9Ijc4MCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB2ZXJzaW9uPSIxLjEiLz4=
|
||||
[4]: https://itsfoss.com/linux-better-than-windows/
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://opensource.com/article/21/10/linux-timers"
|
||||
[#]: author: "Stephan Avenwedde https://opensource.com/users/hansic99"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "FigaroCao"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -1,142 +0,0 @@
|
||||
[#]: subject: "What is Firefox ESR? How to Install it in Ubuntu?"
|
||||
[#]: via: "https://itsfoss.com/firefox-esr-ubuntu/"
|
||||
[#]: author: "Sagar Sharma https://itsfoss.com/author/sagar/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
What is Firefox ESR? How to Install it in Ubuntu?
|
||||
======
|
||||
|
||||
The snap version of Ubuntu is not to your liking? Don’t like constantly changing things with every Firefox release? You can try the Firefox ESR version if you value stability over features.
|
||||
|
||||
### What is Firefox ESR?
|
||||
|
||||
Firefox ESR is a special edition of Firefox browser that doesn’t necessarily get new features monthly as the regular edition but it provides a stable and secure browsing experience. This is suitable for enterprises, organizations and institutes where stability and core features matter more than shiny new features.
|
||||
|
||||
Think of Firefox ESR as the long-term stable release of Linux distributions. They do not necessarily get brand-new features but they get regular security and maintenance updates. This gives the users a familiar and stable environment.
|
||||
|
||||
#### Why should you care for Firefox ESR?
|
||||
|
||||
Firefox releases a new version almost every month. It contains security and feature updates.
|
||||
|
||||
But some people may not like the inclusion and removal of features. If, after an update, you keep wondering where did certain settings go or do not like things that are different than before, Firefox ESR could be worth a try.
|
||||
|
||||
Basically, if you value stability more than new features, Firefox ESR is for you. This is the same version of Firefox that ships with Debian, which is known for being one of the most stable distros you can get in the market.
|
||||
|
||||
Let me show you how to get Firefox ESR on Ubuntu. **_You can have both Firefox and Firefox-ESR versions installed simultaneously. There is no visual difference in their logos so you have to pay attention to which Firefox version you are opening._**
|
||||
|
||||
### Installing Firefox ESR in Ubuntu
|
||||
|
||||
Before I jump to the installation part, let me share what’s the version difference between regular Firefox and Firefox-ESR. While writing,
|
||||
|
||||
- Firefox is running at version **107.0-2**.
|
||||
- Firefox-ESR is currently having **102.5.0esr**.
|
||||
|
||||
So if that’s fine for you, let’s look at the first method.
|
||||
|
||||
#### Method 1: Install Firefox-ESR using PPA
|
||||
|
||||
Firefox-ESR is not available in the default repository of Ubuntu, so you can use the PPA.
|
||||
|
||||
PPA is nothing but a repository being maintained by individual techies or developers to have what the default repository does not.
|
||||
|
||||
And if you want to learn more about PPA, I would recommend checking our other guide that explains [how you can use PPA on Linux.][1]
|
||||
|
||||
Open your terminal and use the given command to add PPA for Firefox-ESR:
|
||||
|
||||
```
|
||||
sudo add-apt-repository ppa:mozillateam/ppa
|
||||
```
|
||||
|
||||
And press Enter to confirm you want to add PPA:
|
||||
|
||||
![add firefox esr repository in ubuntu][2]
|
||||
|
||||
Once done, you will have to update the repository index in Ubuntu to take effect from the changes:
|
||||
|
||||
```
|
||||
sudo apt update
|
||||
```
|
||||
|
||||
And now, you can install Firefox-ESR by using the given command:
|
||||
|
||||
```
|
||||
sudo apt install firefox-esr
|
||||
```
|
||||
|
||||
Next, you can use the given command to check the installed version of Firefox-ESR in your system:
|
||||
|
||||
```
|
||||
firefox-esr -v
|
||||
```
|
||||
|
||||
![check installed version of firefox esr in ubuntu][3]
|
||||
|
||||
##### Uninstalling Firefox-ESR from Ubuntu
|
||||
|
||||
If the ESR felt too outdated for your work or for any other reason you want to remove it from your system, you can follow the steps to remove the Firefox-ESR package and the repository.
|
||||
|
||||
First, let’s remove the Firefox-ESR package using the following:
|
||||
|
||||
```
|
||||
sudo apt remove firefox-esr
|
||||
```
|
||||
|
||||
Now, you can use the given command to [remove PPA from Ubuntu][4]:
|
||||
|
||||
```
|
||||
sudo add-apt-repository --remove ppa:mozillateam/ppa
|
||||
```
|
||||
|
||||
And that’s it!
|
||||
|
||||
#### Method 2: Install Firefox-ESR using Snap
|
||||
|
||||
Love it or hate it, Snaps comes pre-configured on Ubuntu and I find using snaps a neat way of installing packages, especially when you want to avoid building them for source or using PPA.
|
||||
|
||||
All you need to do to install Firefox-ESR using snaps is to follow the given command:
|
||||
|
||||
```
|
||||
sudo snap install firefox --channel=esr/stable
|
||||
```
|
||||
|
||||
![install firefox esr using snaps in ubuntu][5]
|
||||
|
||||
##### Removing Firefox-ESR Snap
|
||||
|
||||
To remove Firefox-ESR (snap package), use the [snap remove command][6]:
|
||||
|
||||
```
|
||||
sudo snap remove firefox
|
||||
```
|
||||
|
||||
And that’s it!
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
I explained how to install Firefox-ESR in Ubuntu using multiple methods in this guide. I personally use Firefox-ESR instead of the regular version as I was having random crashes.
|
||||
|
||||
Since I shifted to Firefox-ESR, things have been going rock-solid for me. And if you were having the same, you should give it a try.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/firefox-esr-ubuntu/
|
||||
|
||||
作者：[Sagar Sharma][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/sagar/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/ppa-guide/
|
||||
[2]: https://itsfoss.com/wp-content/uploads/2022/11/add-firefox-esr-repository-in-ubuntu.png
|
||||
[3]: https://itsfoss.com/wp-content/uploads/2022/11/check-installed-version-of-firefox-esr-in-ubuntu.png
|
||||
[4]: https://itsfoss.com/how-to-remove-or-delete-ppas-quick-tip/
|
||||
[5]: https://itsfoss.com/wp-content/uploads/2022/11/install-firefox-esr-using-snaps-in-ubuntu.png
|
||||
[6]: https://itsfoss.com/remove-snap/
|
||||
@ -1,80 +0,0 @@
|
||||
[#]: subject: "An Open-Source Alternative to Google, Alexa, and Siri in Works for Home Assistant Platform"
|
||||
[#]: via: "https://news.itsfoss.com/open-source-assistant/"
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
An Open-Source Alternative to Google, Alexa, and Siri in Works for Home Assistant Platform
|
||||
======
|
||||
|
||||
An open-source assistant to replace Google, Alexa, Siri?
|
||||
|
||||
![An Open-Source Alternative to Google, Alexa, and Siri in Works for Home Assistant Platform][1]
|
||||
|
||||
**Home Assistant** is an open-source smart home platform that focuses on providing local control and privacy to its users. It can run off a Raspberry Pi or even a local server.
|
||||
|
||||
They also have a subscription service for access to additional features such as support for Alexa and Google Assistant, which is managed by a company called '[Nabu Casa][2]'.
|
||||
|
||||
> 💡 The company is led by [Paulus Schoutsen][3], the founder of Home Assistant.
|
||||
|
||||
In a [blog][4] last week, Paulus announced **a new open-source project that aims to offer a voice assistant without an active internet connection** or any other big tech voice assistants.
|
||||
|
||||
So, an _open-source challenger to Google, Alexa, and Siri?_😲
|
||||
|
||||
Let's see what this is all about, then.
|
||||
|
||||
**What is it?:** This will be a part of the Home Assistant application and will offer the ability to run voice commands locally to control the connected smart devices.
|
||||
|
||||
Paulus also asserts that their most important priority is to support different languages, he says:
|
||||
|
||||
> People need to be able to speak in their own language, as that is the most accessible and only acceptable language for a voice assistant for the smart home.
|
||||
|
||||
To fuel this endeavor, the creator of Rhasspy, [Mike Hansen][5], has been roped in to make this possible.
|
||||
|
||||
For those of you who don't know, [Rhasspy][6] is another open-source software that specializes in providing a fully offline voice assistant that is backed by its community of users.
|
||||
|
||||
If you ask me, I feel that this feature of Home Assistant will be powered by Rhasspy, which is a good thing.
|
||||
|
||||
_Why reinvent something that already exists? It's better to improve upon it._
|
||||
|
||||
**What to expect?:** Initially, the voice assistant won't be able to do things you might expect. So, things like making a web search, making calls, playing voice games, etc., are a no-go.
|
||||
|
||||
What it will focus on instead are the **basics of what a voice assistant should be**; this was done to make sure that the work ahead of them was manageable.
|
||||
|
||||
They aim to start with a few actions and then build up language models around them.
|
||||
|
||||
In its current state, Home Assistant supports 62 different languages in its user interface. They plan to add support for all these languages with their voice assistant.
|
||||
|
||||
**When to expect?:** They have already started work on this by building a [collection of intent matching sentences][7] for every language.
|
||||
|
||||
What this means is that the community can contribute to the development of the voice assistant by adapting the commands for smart devices to their respective native languages.
|
||||
|
||||
They aim for a release sometime in **2023** and have mentioned that it will be the '_year of voice_'.
|
||||
|
||||
I think an open-source voice assistant that works offline can be a very useful thing to have; it lets you be free of any tracking from big tech.
|
||||
|
||||
💬 _With the added benefit of having a large community behind its development of it, what's not to like?_
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/open-source-assistant/
|
||||
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/sourav/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w2000/2022/12/open-source-home-assistant-in-works.png
|
||||
[2]: https://www.nabucasa.com
|
||||
[3]: https://twitter.com/balloob
|
||||
[4]: https://www.home-assistant.io/blog/2022/12/20/year-of-voice/
|
||||
[5]: https://synesthesiam.com
|
||||
[6]: https://rhasspy.readthedocs.io
|
||||
[7]: https://github.com/home-assistant/intents
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://opensource.com/article/23/1/read-write-files-rust"
|
||||
[#]: author: "Stephan Avenwedde https://opensource.com/users/hansic99"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://www.debugpoint.com/who-command-linux/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -0,0 +1,210 @@
|
||||
[#]: subject: "Learn to code with my retro computer program"
|
||||
[#]: via: "https://opensource.com/article/23/1/learn-machine-language-retro-computer"
|
||||
[#]: author: "Jim Hall https://opensource.com/users/jim-hall"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Learn to code with my retro computer program
|
||||
======
|
||||
|
||||
I teach university courses part-time, including a class about general computing topics, open to all majors. This is an introductory course that teaches students about how technology works, to remove the mystery around computing.
|
||||
|
||||
While not a computer science course, one section of this course covers computer programming. I usually talk about programming in very abstract terms, so I don't lose my audience. But this year, I wanted my students to do some "hands-on" programming in an "old school" way. At the same time, I wanted to keep it simple, so everyone could follow along.
|
||||
|
||||
I like to structure my lessons to show how you got from "there" to "here." Ideally, I would let my students learn how to write a simple program. Then I would pick it up from there to show how modern programming allows developers to create more complex programs. I decided to try an unconventional approach — teach the students about the ultimate in low-level programming: machine language.
|
||||
|
||||
### Machine language programming
|
||||
|
||||
Early personal computers like the Apple II (1977), TRS-80 (1977), and IBM PC (1981) let users enter programs with a keyboard, and displayed results on a screen. But computers didn't always come with a screen and keyboard.
|
||||
|
||||
The Altair 8800 and IMSAI 8080 (both made in 1975) required users to enter a program using "switches and lights" on a panel. You would enter an instruction in machine language, using a bank of switches, and the machine would light up the ones and zeros of each binary instruction using LEDs.
|
||||
|
||||
![Image of an Altair 8800 Computer.][1]
|
||||
|
||||
Programming these early machines required knowing the machine language instructions, called opcodes, short for operation codes, to perform basic operations like adding two numbers or storing a value into the computer's memory. I wanted to show my students how programmers would enter a series of instructions and memory addresses by hand, using the switches and lights.
|
||||
|
||||
However, using an actual Altair 8800 would be too much overhead in this class. I needed something simple that any beginner-level student could grasp. Ideally, I hoped to find a simple "hobby" retro computer that worked similarly to the Altair 8800, but I couldn't find a suitable "Altair-like" device for less than $100. I found several "Altair" software emulators, but they faithfully reproduce the Altair 8800 opcodes, and that was too much for my needs.
|
||||
|
||||
I decided to write my own "educational" retro computer. I call it the Toy CPU. You can find it on my [GitHub repository][2], including several releases to play with. Version 1 was an experimental prototype that ran on [FreeDOS][3]. Version 2 was an updated prototype that ran on Linux with [ncurses][4]. Version 3 is a FreeDOS program that runs in graphics mode.
|
||||
|
||||
### Programming the Toy CPU
|
||||
|
||||
The Toy CPU is a very simple retro computer. Sporting only 256 bytes of memory and a minimal instruction set, the Toy CPU aims for simplicity while replicating the "switches and lights" programming model. The interface mimics the Altair 8800, with a series of eight LEDs for the counter (the "line number" for the program), instruction, accumulator (internal memory used for temporary data), and status.
|
||||
|
||||
When you start the Toy CPU, it simulates "booting" by clearing the memory. While the Toy CPU is starting up, it also displays `INI` ("initialize") in the status lights at the bottom-right of the screen. The `PWR` ("power") light indicates the Toy CPU has been turned on.
|
||||
|
||||
![Image of start screen for the toy cpu.][5]
|
||||
|
||||
When the Toy CPU is ready for you to enter a program, it indicates `INP` ("input" mode) via the status lights, and starts you at counter 0 in the program. Programs for the Toy CPU always start at counter 0.
|
||||
|
||||
In "input" mode, use the up and down arrow keys to show the different program counters, and press Enter to edit the instruction at the current counter. When you enter "edit" mode, the Toy CPU shows `EDT` ("edit" mode) on the status lights.
|
||||
|
||||
![Image of the toy CPU editing screen.][6]
|
||||
|
||||
The Toy CPU has a cheat sheet that's "taped" to the front of the display. This lists the different opcodes the Toy CPU can process:
|
||||
|
||||
- `00000000` (`STOP`): Stop program execution.
|
||||
- `00000001` (`RIGHT`): Shift the bits in the accumulator to the right by one position. The value 00000010 becomes 00000001, and 00000001 becomes 00000000.
|
||||
- `00000010` (`LEFT`): Shift the bits in the accumulator to the left by one position. The value 01000000 becomes 10000000, and 10000000 becomes 00000000.
|
||||
- `00001111` (`NOT`): Binary NOT the accumulator. For example, the value 10001000 becomes 01110111.
|
||||
- `00010001` (`AND`): Binary AND the accumulator with the value stored at an address. The address is stored in the next counter.
|
||||
- `00010010` (`OR`): Binary OR the accumulator with the value stored at an address.
|
||||
- `00010011` (`XOR`): Binary XOR (“exclusive or”) the accumulator with the value stored at an address.
|
||||
- `00010100` (`LOAD`): Load (copy) the value from an address into the accumulator.
|
||||
- `00010101` (`STORE`): Store (copy) the value in the accumulator into an address.
|
||||
- `00010110` (`ADD`): Add the value stored at an address to the accumulator.
|
||||
- `00010111` (`SUB`): Subtract the value stored at an address from the accumulator.
|
||||
- `00011000` (`GOTO`): Go to (jump to) a counter address.
|
||||
- `00011001` (`IFZERO`): If the accumulator is zero, go to (jump to) a counter address.
|
||||
- `10000000` (`NOP`): No operation; safely ignored.
|
||||
|
||||
When in "edit" mode, use the left and right arrow keys to select a bit in the opcode, and press `Space`to flip the value between off (0) and on (1). When you are done editing, press `Enter`to go back to "input" mode.
|
||||
|
||||
![Image of the toy CPU input mode screen.][7]
|
||||
|
||||
### A sample program
|
||||
|
||||
I want to explore the Toy CPU by entering a short program that adds two values, and stores the result in the Toy's memory. Effectively, this performs the arithmetic operation **A+B=C**. To create this program, you only need a few opcodes:
|
||||
|
||||
- `00010100` (`LOAD`): Load (copy) the value from an address into the accumulator.
|
||||
- `00010110` (`ADD`): Add the value stored at an address to the accumulator.
|
||||
- `00010101` (`STORE`): Store (copy) the value in the accumulator into an address.
|
||||
- `00000000` (`STOP`): Stop program execution.
|
||||
|
||||
The `LOAD`, `ADD`, and `STORE` instructions require a memory address, which will always be in the next counter location. For example, the first two instructions of the program are:
|
||||
|
||||
```
|
||||
counter 0: 00010100
|
||||
counter 1: some memory address where the first value A is stored
|
||||
```
|
||||
|
||||
The instruction in counter 0 is the `LOAD`operation, and the value in counter 1 is the memory address where you have stored some value. The two instructions together copy a value from memory into the Toy's accumulator, where you can work on the value.
|
||||
|
||||
Having loaded a number **A** into the accumulator, you need to add the value **B** to it. You can do that with these two instructions:
|
||||
|
||||
```
|
||||
counter 2: 00010110
|
||||
counter 3: a memory address where the second value B is stored
|
||||
```
|
||||
|
||||
Say that you loaded the value 1 (**A**) into the accumulator, then added the value 3 (**B**) to it. The accumulator will now have the value 4. Now you need to copy the value 4 into another memory address (**C**) with these two instructions:
|
||||
|
||||
```
|
||||
counter 4: 00010101
|
||||
counter 5: a memory address (C) where we can save the new value
|
||||
```
|
||||
|
||||
Having added the two values together, you can now end the program with this instruction:
|
||||
|
||||
```
|
||||
counter 6: 00000000
|
||||
```
|
||||
|
||||
Any instructions after counter 6 are available for the program to use as stored memory. That means you can use the memory at counter 7 for the value **A**, the memory in counter 8 for the value **B**, and the memory at counter 9 for the stored value **C**. You need to enter these separately into the Toy:
|
||||
|
||||
```
|
||||
counter 7: 00000001 (1)
|
||||
counter 8: 00000011 (3)
|
||||
counter 9: 00000000 (0, will be overwritten later)
|
||||
```
|
||||
|
||||
Having figured out all the instructions and the memory locations for **A**, **B**, and **C**, you can now enter the full program into the Toy. This program adds the values 1 and 3 to get 4:
|
||||
|
||||
```
|
||||
counter 0: 00010100
|
||||
counter 1: 00000111 (7)
|
||||
counter 2: 00010110
|
||||
counter 3: 00001000 (8)
|
||||
counter 4: 00010101
|
||||
counter 5: 00001001 (9)
|
||||
counter 6: 00000000
|
||||
counter 7: 00000001 (1)
|
||||
counter 8: 00000011 (3)
|
||||
counter 9: 00000000 (0, will be overwritten later)
|
||||
```
|
||||
|
||||
To run the program, press the `R` key when in "input" mode. The Toy CPU will show `RUN` ("run" mode) in the status lights, and execute your program starting at counter 0.
|
||||
|
||||
The Toy has a significant delay built into it, so you can watch the Toy execute each step in the program. You should see the counter move from 00000000 (0) to 00000110 (6) as the program progresses. After counter 1, the program loads the value 1 from memory location 7, and the accumulator updates to 00000001 (1). After counter 3, the program will add the value 3 and update the accumulator to show 00000100 (4). The accumulator will remain that way until the program stores the value into memory location 9 after counter 5 then ends at counter 6.
|
||||
|
||||
![Image of the Toy in RUN mode.][8]
|
||||
|
||||
### Exploring machine language programming
|
||||
|
||||
You can use the Toy to create other programs and further explore machine language programming. Test your creativity by writing these programs in machine language.
|
||||
|
||||
### A program to flash the lights on the accumulator
|
||||
|
||||
Can you light up the right four bits on the accumulator, then the left four bits, then all of the bits? You can write this program in one of two ways:
|
||||
|
||||
A straightforward approach would be to load three values from different memory addresses, like this:
|
||||
|
||||
```
|
||||
counter 0: LOAD
|
||||
counter 1: "right"
|
||||
counter 2: LOAD
|
||||
counter 3: "left"
|
||||
counter 4: LOAD
|
||||
counter 5: "all"
|
||||
counter 6: STOP
|
||||
counter 7: 00001111 ("right")
|
||||
counter 8: 11110000 ("left")
|
||||
counter 9: 11111111 ("all")
|
||||
```
|
||||
|
||||
Another way to write this program is to experiment with the NOT and OR binary operations. This results in a smaller program:
|
||||
|
||||
```
|
||||
counter 0: LOAD
|
||||
counter 1: "right"
|
||||
counter 2: NOT
|
||||
counter 3: OR
|
||||
counter 4: "right"
|
||||
counter 5: STOP
|
||||
counter 6: 00001111 ("right")
|
||||
```
|
||||
|
||||
### Count down from a number
|
||||
|
||||
You can use the Toy as a countdown timer. This program exercises the IFZERO test, which will jump the program to a new counter only if the accumulator is zero:
|
||||
|
||||
```
|
||||
counter 0: LOAD
|
||||
counter 1: "initial value"
|
||||
counter 2: IFZERO (this is also the "start" of the countdown)
|
||||
counter 3: "end"
|
||||
counter 4: SUB
|
||||
counter 5: "one"
|
||||
counter 6: GOTO
|
||||
counter 7: "start"
|
||||
counter 8: STOP
|
||||
counter 9: 00000111 ("initial value")
|
||||
counter 10: 00000001 ("one")
|
||||
```
|
||||
|
||||
The Toy CPU is a great way to learn about machine language. I used the Toy CPU in my introductory course, and the students said they found it difficult to write the first program, but writing the next one was much easier. The students also commented that writing programs in this way was actually fun, and they learned a lot about how computers actually work. The Toy CPU is educational and fun!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/1/learn-machine-language-retro-computer
|
||||
|
||||
作者：[Jim Hall][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jim-hall
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/2022-12/MITS_Altair_8800_Computer_%281975%29.png
|
||||
[2]: https://github.com/freedosproject/toycpu
|
||||
[3]: https://opensource.com/downloads/guide-using-freedos
|
||||
[4]: https://opensource.com/article/21/8/ncurses-linux
|
||||
[5]: https://opensource.com/sites/default/files/2022-12/toycpu.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-12/edit0-load.png
|
||||
[7]: https://opensource.com/sites/default/files/2022-12/input0-load.png
|
||||
[8]: https://opensource.com/sites/default/files/2022-12/run-3.png
|
||||
@ -0,0 +1,101 @@
|
||||
[#]: subject: "6 tips for building an effective DevOps culture"
|
||||
[#]: via: "https://opensource.com/article/23/1/tips-effective-devops-culture"
|
||||
[#]: author: "Yauhen Zaremba https://opensource.com/users/yauhen-zaremba"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
6 tips for building an effective DevOps culture
|
||||
======
|
||||
|
||||
Why would you want to build a [DevOps][1] culture? There are many benefits to the streamlined collaboration of the development and operations teams. A major goal is efficiency: Increasing the speed of new software deployments and reducing idle time for workers. Fostering trust between colleagues can improve employee satisfaction, produce new innovations, and positively impact profitability.
|
||||
|
||||
[DevOps][2] is a broad philosophy with a range of interpretations. In other words, you can visit 40 companies and find 40,000 different ideas about using DevOps effectively in the workplace. This diversity of opinion is actually a good thing–so many perspectives are useful for building stronger teams. This guide will look at the top tips for encouraging better collaboration between colleagues within a DevOps culture.
|
||||
|
||||
Each section offers a different aspect of DevOps culture and looks at ways to introduce it into your workforce.
|
||||
|
||||
![DevOps includes collaboration, workflow, infosec, and iteration.][3]
|
||||
|
||||
### Continuous development of processes
|
||||
|
||||
This core tenet of DevOps culture sets it apart from many other types of workplace ethos. The DevOps philosophy says that it is essential to make mistakes because it shows you are trying out new ideas.
|
||||
|
||||
The heart of DevOps culture is a commitment to evolving creativity. Practically, that means not yelling at your direct reports when test results show that things were better before they changed it. It means recognizing that progress is not linear and success is never a straight line.
|
||||
|
||||
DevOps expert [Gene Kim][4] advocates for risk-taking and experimentation. This implies letting your team work on unusual tasks to find new insights.
|
||||
|
||||
Should your organization be profit-driven? Can you allow your teams to try something new? I'm talking about something other than unrelated passion projects. Continuous process development means being open to upgrading present methods. Great sales leaders appreciate that results matter more than presenteeism, so it is always crucial to focus on how teams are working rather than how much.
|
||||
|
||||
### Readily give feedback and actively seek it
|
||||
|
||||
Increased trust between individuals is another key feature of a thriving DevOps culture. Whether your staff is learning how to build affiliate network contacts or trying to design their next [UX][5] survey, everyone should be open to feedback on their work. But this will never happen until your teammates respect each other's opinions and trust that feedback is given in a spirit of good intention.
|
||||
|
||||
This culture may sound impossible to cultivate; indeed, some companies will struggle to achieve this more than others. Granted, a large part of the success of giving and receiving feedback depends on the personalities of your employees. It is possible to screen for this during the recruitment process.
|
||||
|
||||
Before you expect staff to readily offer feedback to colleagues and seek it in the first place, you should lead by example. Members of the C-suite should be modeling this behavior, openly asking members of the company to pose probing questions about their strategic decisions, and providing balanced feedback.
|
||||
|
||||
![DevOps is the intersection of development, quality assurance, and operations][6]
|
||||
|
||||
### Always look for improvements
|
||||
|
||||
Building on increased intellectual trust between colleagues, your team should look for ways to improve its work. The nature of DevOps means the software development team will be producing deployments more rapidly than with traditional approaches.
|
||||
|
||||
However, this culture of openness to improvement can positively impact departments beyond development and operations. Ask yourself what other areas of your business could do with a burst of optimism.
|
||||
|
||||
Be on the lookout for training and upskilling opportunities. Even if a training course is less salient than advertised, the chance to network with industry professionals and build contacts for the future can only enhance the diversity of ideas within your organization.
|
||||
|
||||
### Save ideas for later development
|
||||
|
||||
Part of your DevOps toolchain should be a heavily used account on [Git][7]. You can use Git as a common repository for scripts produced during software development and other related projects. Known as "version control," Git allows programmers to save iterations of their work and reuse or improve the work of others.
|
||||
|
||||
You're aiming for the ability to keep hold of good ideas for future use. A certain pathway did not work out for specific reasons. However, just because that set of ideas was wrong for the time it was conceived does not mean it can never become helpful in the future.
|
||||
|
||||
As the entire focus of DevOps rests on end-to-end ownership of software in production, saving iterations of developments truly supports this principle. You want to see an improved focus on and commitment to the software testing project at hand.
|
||||
|
||||
A simple way to incorporate this is to request that developers include ideas for future work in the developer contract and final project report. Make sure tech services managers know they should ask for examples of side-branching ideas that cropped up during the build. The more minds aware of these little innovations, the more likely someone will remember one when needed.
|
||||
|
||||
### Sit close together (physically or virtually)
|
||||
|
||||
The goal is to share a common understanding of one another's job roles and how they interrelate. You can achieve this in a few simple ways, summarized by three words: Sit close together. Invite other teams to your meetings and share user feedback reports in their entirety. Have lunch together, plan virtual happy hours together, and generally make sure your colleagues are in close proximity. About 90% of teams with a mature DevOps protocol report a clear understanding of their responsibilities to other teams compared to only about 46% of workers in immature DevOps teams.
|
||||
|
||||
Although it can be tempting to form cliques with like-minded folk and only hang out with staff hired to carry out the same tasks as you, this is terrible for the business as a whole. Whether you like it or not, all humans are multi-faceted and capable of contributing their unique talents to a whole host of scenarios.
|
||||
|
||||
The idea of closer collaboration is to honor the ability of anyone to suggest improvements to the products or work processes going on around them. If you only ever sit at a distance from the other departments within the company, you will miss countless opportunities to share intelligent ideas. After all, you often learn best in the free flow of ideas during a conversation.
|
||||
|
||||
### Commit to automation
|
||||
|
||||
You should be looking to automate mundane and repetitive tasks in the name of efficiency and process acceleration. Every industry has boring–and quite frankly, silly–exercises carried out daily or weekly.
|
||||
|
||||
Whether this is manually copying data from one page to another or typing out audio transcripts by hand, staff at every level should insist that machines take on such burdens where possible. The reality is automation technology advances every single year, and operational processes should, too. [Automation testing][8] is so crucial to DevOps that it is the second principle of the CALMS framework (the "C" of which stands for "culture").
|
||||
|
||||
How can you make this happen? Invite staff to openly express which aspects of their job they feel could be automated and then–here is the crucial part–support the facilities needed to automate them. That might mean a $600 annual subscription to a software program, a complete enterprise application modernization, or two days of developers' time to build a new tool to use in-house.
|
||||
|
||||
Either way, you should assess the benefits of automation and consider how much time you could save for everyone. DevOps statistics continually indicate just how much better off modern companies are by integrating these beneficial principles year after year.
|
||||
|
||||
### Explore new ways of working successfully
|
||||
|
||||
A culture shift doesn't happen overnight. The sooner you start, though, the sooner you see results. In my experience, people embrace change when it's a genuine improvement on what has gone before. DevOps provides a framework for such improvements. Whether you're just getting started with DevOps in your organization or simply want to improve your existing culture, consider the above points and how they relate to your organization's future.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/1/tips-effective-devops-culture
|
||||
|
||||
作者：[Yauhen Zaremba][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/yauhen-zaremba
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/resources/devops
|
||||
[2]: https://opensource.com/article/22/2/devops-documentation-maturity
|
||||
[3]: https://opensource.com/sites/default/files/2022-12/devop.png
|
||||
[4]: https://enterprisersproject.com/user/gene-kim
|
||||
[5]: https://opensource.com/article/22/7/awesome-ux-cli-application
|
||||
[6]: https://opensource.com/sites/default/files/2022-12/devop-venn.png
|
||||
[7]: https://opensource.com/article/22/11/git-concepts
|
||||
[8]: https://opensource.com/article/20/7/open-source-test-automation-frameworks
|
||||
161
translated/talk/20210718 Is Open-Source Software Secure.md
Normal file
161
translated/talk/20210718 Is Open-Source Software Secure.md
Normal file
@ -0,0 +1,161 @@
|
||||
[#]: subject: (Is Open-Source Software Secure?)
|
||||
[#]: via: (https://news.itsfoss.com/open-source-software-security/)
|
||||
[#]: author: (Ankush Das https://news.itsfoss.com/author/ankush/)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (CanYellow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
开源软件安全吗？
|
||||
======
|
||||
|
||||
作为一个偏爱 [Linux桌面发行版][1] 并鼓励使用开源软件的人，你可能期待就标题中提出的问题得到一个响亮的**肯定**回答。
|
||||
|
||||
然而，我并不打算仅限于讨论开源软件的优点。让我们一起探索更多的内容吧！
|
||||
|
||||
本文，我计划分享我关于开源软件是否安全的思考以及哪些事情与开源软件的安全性相关。
|
||||
|
||||
### 为什么你需要关注开源软件是否安全？
|
||||
|
||||
不论你是使用 [Linux][2] 系统还是使用其他类型的操作系统，你都会在某种程度上（直接地/间接地）被开源软件所包围。
|
||||
|
||||
举个例子，大多数专有软件工具依赖于某种形式的开源库来保证其正常工作。
|
||||
|
||||
此外，各种规模的公司（包括 Google、Microsoft 和 Facebook ）依赖开源软件或者以某种途径向开源社区贡献资源是有原因的。
|
||||
|
||||
因此，开源软件的安全性是有必要了解的。
|
||||
|
||||
### 有关开源软件安全性的谣言
|
||||
|
||||
![][3]
|
||||
|
||||
虽然有多种理由证明开源软件在安全性方面的缺陷，然而其中一些实际毫无意义。
|
||||
|
||||
#### 任何人都可以查看 & 恶意利用开源软件代码
|
||||
|
||||
是的，开源软件代码对于任何人都是可访问的。但是你可以查看代码并不意味着你可以利用它。
|
||||
|
||||
**不现实**
|
||||
|
||||
即使任何人都可以克隆（或者拷贝）该软件，原始软件也不能轻易地被修改使用。
|
||||
|
||||
通常，项目维护人员（或者维护团队）管理代码仓库并且接受来自贡献者的提交。开源软件代码在接受之前被审查。没有人可以像那样劫持代码。
|
||||
|
||||
**不论是开源软件还是闭源软件，攻击者都需要付出努力来利用软件中的代码漏洞或者添加恶意代码**
|
||||
|
||||
#### 失去专用资源，安全性无从谈起
|
||||
|
||||
很多人相信如果开源软件没有专职人员或者专职团队，维护软件安全性是困难的。
|
||||
|
||||
恰恰相反，由于各种个样类型的贡献者的加入与离开，开源软件获得了来自更大范围的开发者的更多关注。
|
||||
|
||||
他们可能比由专用软件所聘用的少数开发者更能够发现安全问题。
|
||||
|
||||
一些来自 Mozilla 等同类公司的项目拥有自己的专职团队来高效处理安全问题。同样的，大部分成功的开源项目拥有大量的资源用于保障安全性。
|
||||
|
||||
因此，开源软件的生态系统是安全性的组合包。即使没有专职资源，开源项目也可以得到来自各类贡献者的帮助，他们中的一些很大程度上是有利可图的，这有助于他们投入更多的精力。
|
||||
|
||||
### 开源软件是安全的，以下是原因
|
||||
|
||||
![][3]
|
||||
|
||||
既然我们已经解决了有关开源软件安全性的谣言，让我重点展示一下开源软件是如何处理安全问题的。
|
||||
|
||||
换句话说，开源软件在安全性上的优势。
|
||||
|
||||
请不要忘记，开源软件的优势也是 [ Linux 比 Windows 更好][4]的一些原因。
|
||||
|
||||
#### 更多的眼晴关注开源软件代码
|
||||
|
||||
不像专有软件，代码访问仅不限于少数开发者。
|
||||
|
||||
一些开源项目甚至可能拥有数以万记的开发者查看代码、审查它们并标记和修复其中的安全性问题。
|
||||
|
||||
这给予了开源项目拥有**快速识别问题并尽快修复它们的能力**的相比闭源软件的优势。
|
||||
|
||||
不仅仅限于拥有更多的开发者，企业通常也会参与他们所使用的开源项目。当他们这样做的时候，他们也会查阅代码并审查它们。
|
||||
|
||||
这提供了外部审查的另一条途径，而这可能有助于提升开源软件的安全性。
|
||||
|
||||
反之，就闭源软件而言，有限人数的开发者可能并不能找出所有种类的安全问题。而且他们可能需要花费更长的时间来一一修复发现的问题。
|
||||
|
||||
#### 社区决定安全问题的优先级
|
||||
|
||||
闭源软件的开发者可能在处理什么问题和什么时候解决问题等方面有某些限制或者优先等级。
|
||||
|
||||
而如果是开源项目，贡献者社区可以自行决定优先级并自行安排他们想解决的问题以及决定合适修复问题。你不需要依赖于供应商的决定或者按照他们的指示来解决一个安全问题。
|
||||
|
||||
着手处理和修复安全问题的决定在开源软件项目中更加透明和灵活。因此，它可以被证明是更有效的，并为你带来以下三个益处：
|
||||
|
||||
* **透明度**
|
||||
* **不依赖供应商**
|
||||
* **更快的安全更新**
|
||||
|
||||
### 开源软件不是刀枪不入的，以下是原因
|
||||
|
||||
![][3]
|
||||
|
||||
虽然有开源软件可能在安全性上具有优势的案例，然而仍有一些因素影响它。
|
||||
|
||||
承认这些问题的存在是很重要的，据此，企业或者个人可以就一款开源软件的安全情况做出更好的决定。
|
||||
|
||||
#### 并无足够的眼睛来审查代码和不确定性
|
||||
|
||||
即使开源软件代码可以由全世界的开发者自由访问，**项目没有足够的贡献者/开发者彻底审查开源代码**的可能性仍然存在。
|
||||
|
||||
既如此，我们不能对经同行审查的开源软件抱有极高的信心，因为它恰好缺失了这一点。
|
||||
|
||||
开源软件可能“声称”拥有最高的安全性因为它们是开源的。在没有足够的开发者致力于该项目时，这是一种误导。
|
||||
|
||||
同样，我们也无从得知有多少开发者在查看/检查代码以及代码走查在多大程度上进行。
|
||||
|
||||
举例而言，心脏出血漏洞（[Heartbleed][T1]）是在其在广泛使用项目—— **OpenSSL** ——中引入了2年以后才被发现的。
|
||||
|
||||
#### 软件责任与义务
|
||||
|
||||
对于个人用户这可能并不重要，但是**开源项目通常并无任何保证**。
|
||||
|
||||
因此，如果一家公司使用它，它们必须自行承担任何由该软件使用造成的数据丢失与损坏。
|
||||
|
||||
这告诉你没有什么是100%安全和没有漏洞的。无论有多少眼睛聚焦在代码上或者贡献者的技术多么精湛，总会存在某种形式的风险，可能是安全风险可能是数据丢失。
|
||||
|
||||
这告诉我们一个现实：开源软件并非刀枪不入。
|
||||
|
||||
### 开源软件有其更高安全性的优势，但是...
|
||||
|
||||
就安全性而言没有什么优胜者。不论是闭源还是开源，当涉及安全问题时都适用同一套原则。
|
||||
|
||||
有很多外部因素可以印象软件安全性，而**其中很多都不是来源相关的**。
|
||||
|
||||
代码必须被以某种形式监控以保证安全。
|
||||
|
||||
是的，**开源道路提供了闭源软件所不具备的优势**，但是这并不意味着开源软件是刀枪不入的。
|
||||
|
||||
_你对开源软件安全状况有何思考？_ _你又是否认为开源软件比专有软件解决方案更好呢？_
|
||||
|
||||
提前感谢您在下面的评论中提出的宝贵意见。
|
||||
|
||||
#### 大型科技网站坐拥百万收入，而 It's FOSS 拥有每一个你！
|
||||
|
||||
如果你喜欢我们在 It's FOSS 中所做的工作，请您考虑捐赠以支持我们的独立出版物。你的支持将有助于我们继续发布有关 Linux 桌面版以及开源软件的内容。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/open-source-software-security/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[CanYellow](https://github.com/CanYellow)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://news.itsfoss.com/linux-foundation-linux-desktop/
|
||||
[2]: https://itsfoss.com/what-is-linux-distribution/
|
||||
[3]: data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjQzOSIgd2lkdGg9Ijc4MCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB2ZXJzaW9uPSIxLjEiLz4=
|
||||
[4]: https://itsfoss.com/linux-better-than-windows/
|
||||
|
||||
[T1]: https://www.cve.org/CVERecord?id=CVE-2014-0160
|
||||
@ -0,0 +1,142 @@
|
||||
[#]: subject: "What is Firefox ESR? How to Install it in Ubuntu?"
|
||||
[#]: via: "https://itsfoss.com/firefox-esr-ubuntu/"
|
||||
[#]: author: "Sagar Sharma https://itsfoss.com/author/sagar/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
什么是 Firefox ESR？如何在 Ubuntu 中安装它？
|
||||
======
|
||||
|
||||
Ubuntu 的 snap 版本你不喜欢？不喜欢每一次 Firefox 的发布都要不断地改变东西？如果你重视稳定性而不是功能，你可以试试 Firefox ESR 版本。
|
||||
|
||||
### 什么是 Firefox ESR？
|
||||
|
||||
Firefox ESR 是 Firefox 的特别版，它不一定像普通版那样每月都有新功能，但它能提供稳定和安全的浏览体验。这适用于企业、组织和机构，在这些地方，稳定性和核心功能比闪亮的新功能更重要。
|
||||
|
||||
把 Firefox ESR 看作是 Linux 发行版的长期稳定版本。他们不一定得到全新的功能，但他们会得到定期的安全和维护更新。这给了用户一个熟悉和稳定的环境。
|
||||
|
||||
#### 你为什么要关心 Firefox ESR？
|
||||
|
||||
Firefox 几乎每个月都会发布一个新版本。它包含安全和功能更新。
|
||||
|
||||
但有些人可能不喜欢功能的加入和删除。如果在更新之后，你一直想知道某些设置到哪里去了，或者不喜欢与以前不同的东西，Firefox ESR可能值得一试。
|
||||
|
||||
基本上，如果你更看重稳定性而不是新功能，那么 Firefox ESR 就适合你。这也是与 Debian 相同的 Firefox 版本，Debian 以其是市场上最稳定的发行版之一而闻名。
|
||||
|
||||
让我告诉你如何在 Ubuntu 上获得 Firefox ESR。**_你可以同时安装 Firefox 和 Firefox-ESR 两个版本。它们的标识没有视觉上的区别，所以你必须注意你打开的是哪个火狐版本。_**
|
||||
|
||||
### 在 Ubuntu 中安装 Firefox ESR
|
||||
|
||||
在进入安装之前，让我来分享一下普通 Firefox 和 Firefox-ESR 之间的版本差异是什么。在写这篇文章的时候：
|
||||
|
||||
- Firefox 的版本是 **107.0-2**。
|
||||
- Firefox-ESR 目前的版本是 **102.5.0esr**。
|
||||
|
||||
所以，如果这对你来说没问题，让我们看看第一个方法。
|
||||
|
||||
#### 方法 1：使用 PPA 安装 Firefox-ESR
|
||||
|
||||
Firefox-ESR 在 Ubuntu 的默认仓库中是不可用的，所以你可以使用 PPA。
|
||||
|
||||
PPA 只不过是一个由个别技术人员或开发者维护的仓库，拥有默认仓库所没有的东西。
|
||||
|
||||
如果你想了解更多关于 PPA 的信息，我建议你查看我们的其他指南，其中解释了[如何在 Linux 上使用 PPA][1]。
|
||||
|
||||
打开你的终端，使用给定的命令来添加 Firefox-ESR 的 PPA：
|
||||
|
||||
```
|
||||
sudo add-apt-repository ppa:mozillateam/ppa
|
||||
```
|
||||
|
||||
然后按回车键确认你要添加 PPA：
|
||||
|
||||
![add firefox esr repository in ubuntu][2]
|
||||
|
||||
完成后，你需要更新 Ubuntu 中的仓库索引，以便从这些变化中生效：
|
||||
|
||||
```
|
||||
sudo apt update
|
||||
```
|
||||
|
||||
现在，你可以通过使用给定的命令来安装 Firefox-ESR：
|
||||
|
||||
```
|
||||
sudo apt install firefox-esr
|
||||
```
|
||||
|
||||
接下来，你可以使用给定的命令来检查你系统中 Firefox-ESR 的安装版本：
|
||||
|
||||
```
|
||||
firefox-esr -v
|
||||
```
|
||||
|
||||
![check installed version of firefox esr in ubuntu][3]
|
||||
|
||||
##### 从 Ubuntu 卸载 Firefox-ESR
|
||||
|
||||
如果 ESR 对你的工作来说感觉太过时了，或者由于其他原因你想从你的系统中删除它，你可以按照以下步骤删除 Firefox-ESR 包和仓库。
|
||||
|
||||
首先，让我们用下面的方法删除 Firefox-ESR 包：
|
||||
|
||||
```
|
||||
sudo apt remove firefox-esr
|
||||
```
|
||||
|
||||
现在，你可以使用给定的命令来[从 Ubuntu 删除 PPA][4]：
|
||||
|
||||
```
|
||||
sudo add-apt-repository --remove ppa:mozillateam/ppa
|
||||
```
|
||||
|
||||
这就完成了！
|
||||
|
||||
#### 方法 2：使用 Snap 安装 Firefox-ESR
|
||||
|
||||
不管你爱不爱它，Snaps 在 Ubuntu 上是预先配置好的，我发现使用 Snaps 是安装软件包的一个很好的方法，特别是当你想避免从源码构建它们或使用 PPA 时。
|
||||
|
||||
使用 Snaps 安装 Firefox-ESR，你需要做的就是使用给定的命令：
|
||||
|
||||
```
|
||||
sudo snap install firefox --channel=esr/stable
|
||||
```
|
||||
|
||||
![install firefox esr using snaps in ubuntu][5]
|
||||
|
||||
##### 删除 Firefox-ESR Snap
|
||||
|
||||
要删除 Firefox-ESR（snap 包），请使用 [snap remove 命令][6]：
|
||||
|
||||
```
|
||||
sudo snap remove firefox
|
||||
```
|
||||
|
||||
这就完成了！
|
||||
|
||||
### 总结
|
||||
|
||||
我在本指南中解释了如何使用多种方法在 Ubuntu 中安装 Firefox-ESR。我个人使用 Firefox-ESR 而不是普通版本，因为我有随机崩溃的情况。
|
||||
|
||||
自从我改用 Firefox-ESR 后，一切都变得稳如磐石。如果你也有同样的问题，你应该试一试。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/firefox-esr-ubuntu/
|
||||
|
||||
作者：[Sagar Sharma][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/sagar/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/ppa-guide/
|
||||
[2]: https://itsfoss.com/wp-content/uploads/2022/11/add-firefox-esr-repository-in-ubuntu.png
|
||||
[3]: https://itsfoss.com/wp-content/uploads/2022/11/check-installed-version-of-firefox-esr-in-ubuntu.png
|
||||
[4]: https://itsfoss.com/how-to-remove-or-delete-ppas-quick-tip/
|
||||
[5]: https://itsfoss.com/wp-content/uploads/2022/11/install-firefox-esr-using-snaps-in-ubuntu.png
|
||||
[6]: https://itsfoss.com/remove-snap/
|
||||
@ -0,0 +1,80 @@
|
||||
[#]: subject: "An Open-Source Alternative to Google, Alexa, and Siri in Works for Home Assistant Platform"
|
||||
[#]: via: "https://news.itsfoss.com/open-source-assistant/"
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Google、Alexa 和 Siri 的开源替代品 Home Assistant 平台
|
||||
======
|
||||
|
||||
一个开源助手可以取代谷歌、Alexa 和 Siri？
|
||||
|
||||
![An Open-Source Alternative to Google, Alexa, and Siri in Works for Home Assistant Platform][1]
|
||||
|
||||
**Home Assistant** 是一个开源的智能家居平台，专注于为用户提供本地控制和隐私。它可以从树莓派或甚至本地服务器上运行。
|
||||
|
||||
他们还有一个订阅服务，可以获得额外的功能，如支持 Alexa 和谷歌助理，它由一家名为 “[Nabu Casa][2]” 的公司管理。
|
||||
|
||||
> 💡 该公司由 Home Assistant 的创始人 [Paulus Schoutsen][3] 领导。
|
||||
|
||||
在上周的[博客][4]中，Paulus 宣布了**一个新的开源项目，旨在提供一个没有主动互联网连接的语音助手**或任何其他大型科技语音助手。
|
||||
|
||||
这是_一个对 Google、Alexa 和 Siri 的开源挑战者？_ 😲
|
||||
|
||||
让我们看看这到底是怎么回事。
|
||||
|
||||
**它是什么？：**这将是 Home Assistant 应用的一部分，将提供在本地运行语音命令的能力，以控制连接的智能设备。
|
||||
|
||||
Paulus 还断言，他们最重要的优先事项是支持不同的语言，他说：
|
||||
|
||||
> 人们需要能够用自己的语言说话，因为对于智能家居的语音助手来说，这是最容易接受和唯一可以接受的语言。
|
||||
|
||||
为了推动这一努力，Rhasspy 的创造者 [Mike Hansen][5] 已经被拉来实现这一目标。
|
||||
|
||||
对于那些不知道的人来说，[Rhasspy][6] 是另一个开源软件，专门提供一个由其用户社区支持的完全离线的语音助手。
|
||||
|
||||
如果你问我，我觉得 Home Assistant 的这个功能将由 Rhasspy 提供，这是一件好事。
|
||||
|
||||
_为什么要重新发明已经存在的东西？最好是在它的基础上进行改进。_
|
||||
|
||||
**可以期待什么？：**最初，语音助手将不能做你可能期待的事情。因此，像进行网络搜索、打电话、玩语音游戏等，都是不可能的。
|
||||
|
||||
它所关注的反而是**语音助手应该有的基本功能**。这样做是为了确保他们面前的工作是可控的。
|
||||
|
||||
他们的目标是从几个动作开始，然后围绕它们建立语言模型。
|
||||
|
||||
在目前的状态下，Home Assistant 在其用户界面上支持 62 种不同的语言。他们计划用他们的语音助手增加对所有这些语言的支持。
|
||||
|
||||
**何时期待？：**他们已经开始了这方面的工作，为每种语言建立一个[意图匹配句子集合][7]。
|
||||
|
||||
这意味着社区可以通过将智能设备的命令改编成各自的母语来为语音助手的发展做出贡献。
|
||||
|
||||
他们的目标是在 **2023** 年的某个时候发布，并提到这将是“_语音年_”。
|
||||
|
||||
我认为一个可以离线工作的开源语音助手可以是一个非常有用的东西。它可以让你不受大科技公司的任何追踪。
|
||||
|
||||
💬 _还有一个额外的好处是，它的开发背后有一个庞大的社区，有什么理由不喜欢呢？_
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/open-source-assistant/
|
||||
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/sourav/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w2000/2022/12/open-source-home-assistant-in-works.png
|
||||
[2]: https://www.nabucasa.com
|
||||
[3]: https://twitter.com/balloob
|
||||
[4]: https://www.home-assistant.io/blog/2022/12/20/year-of-voice/
|
||||
[5]: https://synesthesiam.com
|
||||
[6]: https://rhasspy.readthedocs.io
|
||||
[7]: https://github.com/home-assistant/intents
|
||||
Loading…
Reference in New Issue
Block a user