Marcin Szewczyk

1.1K posts

Marcin Szewczyk

Marcin Szewczyk

@wodny

Katılım Haziran 2009
334 Takip Edilen19 Takipçiler
mejm
mejm@mejmpl·
XD
mejm tweet media
7
1
108
5.2K
Marcin Szewczyk
Marcin Szewczyk@wodny·
@PUsiadek Całkiem przyzwoity materiał o tym, jak może dojść na drodze ewolucji do sytuacji, gdy finalny efekt jest złożony z kilku współpracujących ze sobą również dość skomplikowanych elementów: youtube.com/playlist?list=…
Polski
1
0
1
413
Paweł Usiądek
Paweł Usiądek@PUsiadek·
Dowód na Stworzenie Życia. Replikacja DNA wymaga 9 złożonych nano-maszyn pracujących razem. Bez nich DNA nie może się replikować. Jeśli DNA nie może się replikować, Życie nie może ewoluować.
Polski
99
59
320
37K
Marcin Szewczyk
Marcin Szewczyk@wodny·
@donald_PL_ Wspaniały prezent dla PiS-u w temacie wymiaru sprawiedliwości. Najpierw dostaje 2 lata, potem 1.5 roku i mówi się o wolnościowych środkach, a na koniec po prostu ucieka, jak kilku poprzednich mistrzów kierownicy...
Polski
0
0
4
472
donald.pl
donald.pl@donald_PL_·
Mecenas Kozanecki, ten od "trumien na kółkach", jest poszukiwany przez policję.
donald.pl tweet media
Polski
42
72
1.1K
51K
Rust Bytes 🦀
Rust Bytes 🦀@rustaceans_rs·
Rust, Ubuntu and Lunduke moment!
Rust Bytes 🦀 tweet media
The Lunduke Journal@LundukeJournal

Remember the security firm that Ubuntu hired to audit the (ill-advised, highly buggy) Rust-rewrites of all of the GNU Coreutils? Turns out that security firm is run by @gf_256, who: - Appears to be a man who thinks he's a woman ("trans"). - Uses an anime cartoon of a girl as his avatar. - Appears to have an OnlyFans page. I repeat: Ubuntu hired a "Trans" man, with an anime girl avatar and an OnlyFans page... to audit Rust code. It's hard to get more on-the-nose than that.

Indonesia
5
4
143
10.9K
Marcin Szewczyk
Marcin Szewczyk@wodny·
@LukeDashjr @brian_pak Yeah. When the trivial exploit code dropped I asked on #debian-security what was the projected timeline. There was none as there were no patches upstream for 6.1 and 6.12.
English
0
0
2
125
Luke Dashjr
Luke Dashjr@LukeDashjr·
@brian_pak You claim you "waited for the patch to land", but it didn't actually exist or land until April 30th! Mainline Linux is not what people actually use.
English
2
2
42
3.5K
Brian Pak
Brian Pak@brian_pak·
Hey everyone. We’ve seen the discussions around Copy Fail (CVE-2026-31431) and the disclosure process. We appreciate the passion from distro maintainers, defenders, and the broader Linux community. This is a serious issue, and we want to share some context on our side in good faith. 🧵
English
16
86
537
103.6K
Marcin Szewczyk
Marcin Szewczyk@wodny·
@brian_pak That does not seem to match Greg KH's statement: > Why do you think that we knew this was "imminent"? The CVE team has no such knowlege as no one is obligated to tell us that they are about to let loose a trivial exploit. openwall.com/lists/oss-secu…
English
0
0
0
428
Brian Pak
Brian Pak@brian_pak·
We also provided a fully working exploit to the kernel security team when we reported. We’ve since learned that such details don’t automatically get forwarded downstream and that Linux kernel commit messages are typically kept minimal. That’s simply how the process works.
English
2
2
58
21.4K
Marcin Szewczyk
Marcin Szewczyk@wodny·
@brian_pak You're omitting at least one important fact. Greg KH: > Why do you think that we knew this was "imminent"? The CVE team has no such knowlege as no one is obligated to tell us that they are about to let loose a trivial exploit. openwall.com/lists/oss-secu…
English
0
0
1
894
International Cyber Digest
International Cyber Digest@IntCyberDigest·
Thank you for making Linux more secure. Disclosures like this one have serious real-world implications when downstream distros are still lagging behind on patches. Did you also share the details with the linux-distros mailing list (or equivalent) under embargo so vendors could prepare backports? How come they weren’t ready upon your disclosure?
English
1
0
29
4.1K
sudox
sudox@kmcnam1·
Ughhh can we not?
sudox tweet media
English
25
3
88
3.4K
Xint
Xint@xint_official·
Patch your Linux boxes! Copy.Fail is a trivially exploitable logic bug in Linux, reachable on all major distros released in the last 9 years. A small, portable python script gets root on all platforms. Found by the teams at @theori_io and @xint_official More details below xint.io/blog/copy-fail…
English
24
365
985
242.1K
Brad Spengler
Brad Spengler@spendergrsec·
@xint_official @theori_io Why tell people to patch when you know their distros don't have fixes because you enabled upstream to obfuscate the vulnerability fix? The CVE (copy+pasting the fix description, as all Linux CNA CVEs do): @gregkh/" target="_blank" rel="nofollow noopener">lore.kernel.org/linux-cve-anno… makes no mention of any vulnerability.
English
2
9
81
8.7K
retrocvnt
retrocvnt@retrocvnty·
Repo! The Genetic Opera (2008)
retrocvnt tweet mediaretrocvnt tweet mediaretrocvnt tweet mediaretrocvnt tweet media
Español
15
753
3.2K
69.3K
sudox
sudox@kmcnam1·
sudox tweet media
ZXX
10
5
62
2.2K
Erik Ex Plano
Erik Ex Plano@ErikExplains·
@kmcnam1 Consdering how much of that stuff still runs over RS232 to this day, (or USB pretending to not be RS232 but in reality is emulating RS232, or an Ethernet and TCP/IP stack that winds up feeding RS232), it's probably just a wrong baud rate / word size / partity setting somewhere.
English
3
0
5
78
Wiz
Wiz@wiz_io·
🚨 BREAKING: Wiz Research discovered Remote Code Execution on GitHub.com with a single git push The flaw in @github allowed unauthorized access to millions of repositories belonging to other users and organizations 🤯
Wiz tweet media
English
92
1K
4.5K
536.6K