Two malicious Rust crates—proc-macro1 version 1.0.107 and proc-macro-en version 1.0.10—impersonate the naming, source, authorship, and metadata of the legitimate proc-macro2 ecosystem.
Both contain the same malicious build.rs, byte for byte. Building either crate directly or as a transitive dependency downloads and launches a platform-specific payload. Commands that may trigger execution include cargo build, cargo check, and cargo test.
The build script:
| { | |
| "minecraft:dimension_type": { | |
| type: "minecraft:dimension_type", | |
| value: [ | |
| { | |
| name: "minecraft:overworld", | |
| id: 0, | |
| element: { | |
| piglin_safe: 0b, | |
| natural: 1b, |
https://github.com/spieglt/cloaker - password-based file encryptor (NOTE: uses Qt)
https://github.com/str4d/rage - file encryption tool and librarary that uses the age format
https://github.com/mohanson/gameboy - gameboy emulator
https://github.com/bartwillems/lyriek - fetch the lyrics of a song playing in an mpris-compatible player
https://github.com/JakeStanger/mpd-discord-rpc - discordrpc for mpd
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
| Pipeline | Pipeline io_uring | Non-pipelined | Non-pipelined io_uring | |
|---|---|---|---|---|
| CPU | 99 | 50 (-50%) | 97 | 48 (-50%) |
| RPS | 2,592,670 | 2,878,222 (+11%) | 497,429 | 631,976 (+26%) |
| Working set | 79 | 81 | 79 | 81 |
| Latency (mean) | 1.28 | 0.98 | 1.07 | 1.47 |
| Latency (99th) | n/a | 7.57 | 14.8 | 14.67 |
| 11foot8 | |
| 18650masterrace | |
| 1911 | |
| 2b2t | |
| 3Dprinting | |
| 3dshacks | |
| 3kliksphilip | |
| 45thworldproblems | |
| 5September2020 | |
| 9CB9D65 |
There are at least two valid, signed TLS certificates that are bundled with publicly available Netgear device firmware.
These certificates are trusted by browsers on all platforms, but will surely be added to revocation lists shortly.
The firmware images that contained these certificates along with their private keys were publicly available for download through Netgear's support website, without authentication; thus anyone in the world could have retrieved these keys.
| // Copyright (C) 2019 RoccoDev | |
| // Licensed under the MIT license. | |
| // <https://opensource.org/licenses/MIT> | |
| // Bench results: | |
| // First hash: 152ms | |
| // Second hash: 1ms | |
| // Third hash: 0ms | |
| extern crate crypto; // Tested with 0.2.36 |
| <# | |
| Downloads FireFox Send executable made by Tim Visée - https://github.com/timvisee/ffsend/releases | |
| Current Version ffsend v0.2.30 as of 03-14-19 | |
| Script made by John Davis @John_Davis - https://github.com/Belorum | |
| #> | |
| Net Session 2>&1 > $null | |
| if ( $? -eq "False" ) { | |
| $Current_Time = Get-Date |
