OpenSSL-2022
nixpkgs
| OpenSSL-2022 | nixpkgs | |
|---|---|---|
| 21 | 977 | |
| 528 | 15,931 | |
| -0.6% | 3.9% | |
| 10.0 | 10.0 | |
| over 1 year ago | 7 days ago | |
| Nix | ||
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OpenSSL-2022
-
OpenSSL CVE Remediation?
NCSC-NL is keeping an up to list of affected software here: https://github.com/NCSC-NL/OpenSSL-2022/tree/main/software. Salesforce is not mentioned but if their servers were using 3.0–3.6 I'd expect them to be upgraded already.
- M365 Defender Vulnerability Management - OpenSSL
- Overview of software (un)affected by the OpenSSL vulnerability
- List of software (un)affected by OpenSSL vulnerability
-
CVE-2022-3786 and CVE-2022-3602: X.509 Email Address Buffer Overflows
NCSC is calling it SpookySSL but I think it is just for funsies. https://github.com/NCSC-NL/OpenSSL-2022
- SSL RCE Vulnerability
- Security issue with OpenSSL
- OpenSSL 3.0.7 - CVE-2022-3602
-
OpenSSL 3.0.7 Published
I'm oversimplifying it a bit, but anything that hasn't reached stable this year is still using v1.1.1 (and therefore unaffected).
Ubuntu v22.04 is vulnerable, but any before it is not. Debian is good (except bookworm which is currently in testing), Fedora (<36) is good, RHEL/CentOS (<9), Arch...
So on top of being not as serious as Heartbleed, servers that are a bit longer in operation (but still well within their support cycle) don't need patching.
https://github.com/NCSC-NL/OpenSSL-2022/tree/main/software
- Urgent: Patch OpenSSL on November 1 to avoid “Critical” Security Vulnerability - GlobalSign
nixpkgs
-
Tracexec: TUI for tracing execve and pre-exec behavior
This will drop you into a shell where `tracexec` is installed.
[1]: https://github.com/NixOS/nixpkgs/pull/310158
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
What are some alternatives?
betterscan-ce - Code Scanning/SAST/Static Analysis/Linting using many tools/Scanners + OpenAI GPT with One Report (Code, IaC) - Betterscan Community Edition (CE)
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
rustls - A modern TLS library in Rust
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
CVE-2022-3602
git-lfs - Git extension for versioning large files
OpenSSL - TLS/SSL and crypto library
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
openssl-vuln-nov-2022 - List of software impacted by OpenSSL 3.x Nov 2022 vulnerability
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
nixos - My NixOS Configurations