SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Please remove rust and Firefox. The rust team has poor security hygiene. They believe it's OK to download untrusted binaries in order to compile their compiler. They don't even ask the user if that is acceptable. Because Firefox is built on rust, it has to go as well.
Please remove rust and Firefox. The rust team has poor security hygiene. They believe it's OK to download untrusted binaries in order to compile their compiler. They don't even ask the user if that is acceptable. Because Firefox is built on rust, it has to go as well.
Good luck on getting this to happen. Not everyone shares your misguided sense of security (as has been heavily discussed in your other thread).
Please remove rust and Firefox. The rust team has poor security hygiene. They believe it's OK to download untrusted binaries in order to compile their compiler. They don't even ask the user if that is acceptable. Because Firefox is built on rust, it has to go as well.
Normal users do not have to compile rust from sources, they use their distro's packages. A distro packager will make all the difficult decisions on behalf of the software's end-users. This is not a trivial task. Not just for rust but also for other pieces of software.
IF you think you are qualified to build your own packages - then the rule number one is that you read the documentation about what you are supposed to do and what you can expect.
As I told you in your other ridiculous topic, you could have simply read the docs and noticed that the script you wanted to use needs to download a bootstrap compiler. If you want to use an already installed rust compiler, that is entirely possible and does not require a download of a bootstrap compiler. You can tell the script about that.
You are confusing security with ignorance.
The latest update for setuptools, again broken lib path
for x64 goes under /usr/lib instead of /usr/lib64
that cause extra modules depending of setuptool fail to build.
I'm also having this issue. A bunch of python stuff is broken. In one package (networkx):
Code:
from pkg_resources import parse_version
ModuleNotFoundError: No module named 'pkg_resources'
And then when I tried to reinstall networkx from SBo:
Code:
Traceback (most recent call last):
File "setup.py", line 16, in <module>
from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'
We are pleased to announce the availability of a new GnuPG release:
version 2.2.23. This version fixes a *critical security bug* in
versions 2.2.21 and 2.2.22.
(…)
Importing an OpenPGP key having a preference list for AEAD algorithms
will lead to an array overflow and thus often to a crash or other
undefined behaviour.
Importing an arbitrary key can often easily be triggered by an attacker
and thus triggering this bug. Exploiting the bug aside from crashes is
not trivial but likely possible for a dedicated attacker. The major
hurdle for an attacker is that only every second byte is under their
control with every first byte having a fixed value of 0x04.
Software distribution verification should not be affected by this bug
because such a system uses a curated list of keys.
Would be nice if we could get glib 2.66.x series and friends into current, they should arrive at the end of this month.
Most probably will be just a simple matter of upgradepkg on the once we have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.