Shakedown Social

Scripter :verified_flashing:chwoot: Kritische Linux-Lücke macht Nutzer auf den meisten Systemen zu Root | heise online <a href="https://www.heise.de/news/chwoot-Kritische-Linux-Luecke-macht-Nutzer-auf-den-meisten-Systemen-zu-Root-10466885.html" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/chwoot-Kritische-Linux-Luecke-macht-Nutzer-auf-den-meisten-Systemen-zu-Root-10466885.html</a> <a href="https://social.tchncs.de/tags/Betriebssystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Betriebssystem</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücke</a> <a href="https://social.tchncs.de/tags/sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#sudo</a> <a href="https://social.tchncs.de/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> <a href="https://social.tchncs.de/tags/chwoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chwoot</a>

Verfassungklage@troet.cafe<a href="https://troet.cafe/tags/Root" class="mention hashtag" rel="nofollow noopener" target="_blank">#Root</a>-Zugriff für alle: <a href="https://troet.cafe/tags/Kritische" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kritische</a> <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sudo</a>-Lücke gefährdet unzählige <a href="https://troet.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>-Systeme<a href="https://troet.cafe/tags/Forscher" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forscher</a> haben eine gefährliche <a href="https://troet.cafe/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücke</a> im <a href="https://troet.cafe/tags/Kommandozeilentool" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kommandozeilentool</a> <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sudo</a> entdeckt. Angreifer können mit wenig Aufwand Root-Rechte erlangen.Die <a href="https://troet.cafe/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücke</a> besteht laut Blogbeitrag der <a href="https://troet.cafe/tags/Forscher" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forscher</a> seit der im Juni 2023 veröffentlichten <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sudo</a>-Version 1.9.14 – und damit seit rund zwei Jahren. Ursache ist wohl ein Fehler in der <a href="https://troet.cafe/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a>- <a href="https://troet.cafe/tags/Implementierung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Implementierung</a>. <a href="https://www.golem.de/news/root-zugriff-fuer-alle-kritische-sudo-luecke-gefaehrdet-unzaehlige-linux-systeme-2507-197635.html" rel="nofollow noopener" translate="no" target="_blank">https://www.golem.de/news/root-zugriff-fuer-alle-kritische-sudo-luecke-gefaehrdet-unzaehlige-linux-systeme-2507-197635.html</a>

Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:<a href="https://infosec.space/@MsDropbear42" class="u-url mention" rel="nofollow noopener" target="_blank">@MsDropbear42</a> Weeeeeeeeell, now i've made time to investigate what ails poor lil ol' ONT, & it seems pretty terminal [boom, tish]. The failure to finish booting occurred after i did a system update after not doing so for several months. OS was <a href="https://infosec.space/tags/SparkyLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#SparkyLinux</a> Testing / semi-rolling. Afaict, whatever caused the damage did a pretty good job:<ul><li>the <a href="https://infosec.space/tags/bootloader" class="mention hashtag" rel="nofollow noopener" target="_blank">#bootloader</a> had vaporised</li><li>the <a href="https://infosec.space/tags/LUKS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LUKS</a> <a href="https://infosec.space/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a> seems to have been damaged [even booting from a Live usb stick couldn't unlock the drive, my LUKS pswd being rejected despite absolutely certainly being correct]; it accepts my LUKS password during boot, then says "Slot 0 opened", then... just sits there, evermore. Sigh. </li></ul>I considered trying to repair the bootloader via a <a href="https://infosec.space/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a>, but even if that succeeded i frankly had little appetite to then do battle with a sulky LUKS. This pc is a very old clunker, spinning rust HDDs only, merely 8 GB RAM, i7 though old model, & i'd repurposed it to be my lounge-room media pc several months ago without bothering to change anything about its extant OS... & tbh Sparky had been wearing a bit thin on me anyway for a coupla months in this role. So i decided not to bother attempting repairs, & instead make a clean break with an alternative distro that i feel should be just about ideal for this use as a media pc, whose only function is to run a browser, & my VPN app, for my nightly movies & shows streaming. As such, i really just don't wanna be arsed with running updates on it often, & generally mollycoddling it like i do with my real pooter [<a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> <a href="https://infosec.space/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> <a href="https://infosec.space/tags/Plasma" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plasma</a>]... i just want it to live happily in the darkness of my timber cabinet, asking little of me re upkeep, & just purring away. Thus, it now has <a href="https://infosec.space/tags/LinuxMint" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMint</a> <a href="https://infosec.space/tags/LMDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#LMDE</a> 6. Gotta hand it to ol' Clem & Co; they've done a really nice job with it. <a href="https://infosec.space/tags/ONT" class="mention hashtag" rel="nofollow noopener" target="_blank">#ONT</a> <a href="https://infosec.space/tags/PistonBroke" class="mention hashtag" rel="nofollow noopener" target="_blank">#PistonBroke</a>

r1w1s1I wrote a simple shell script to manage a Slackware chroot environment for building packages. Tested with Slackware-current. You can create and access the chroot easily with just a few commands. Source: <a href="https://git.sr.ht/~r1w1s1/slackbuilds/blob/main/chroot-manager.sh" rel="nofollow noopener" target="_blank">https://git.sr.ht/~r1w1s1/slackbuilds/blob/main/chroot-manager.sh</a> <a href="https://snac.bsd.cafe?t=slackware" class="mention hashtag" rel="nofollow noopener" target="_blank">#slackware</a> <a href="https://snac.bsd.cafe?t=shellscript" class="mention hashtag" rel="nofollow noopener" target="_blank">#shellscript</a> <a href="https://snac.bsd.cafe?t=chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> <a href="https://snac.bsd.cafe?t=linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

OSTechNixHow To Automate Mounting /dev In Chroot Environments In Linux <a href="https://floss.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a> <a href="https://floss.social/tags/mmdebstrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#mmdebstrap</a> <a href="https://floss.social/tags/Troubleshooting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Troubleshooting</a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://floss.social/tags/Linuxhowto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxhowto</a> <a href="https://floss.social/tags/Linuxadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxadmin</a> <a href="https://ostechnix.com/auto-mount-dev-in-chroot/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/auto-mount-dev-in-chroot/</a>

OSTechNixHow To Create Chroot Environments Using Mmdebstrap In Debian Linux <a href="https://floss.social/tags/Mmdebstrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mmdebstrap</a> <a href="https://floss.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a> <a href="https://floss.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://floss.social/tags/Linuxadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxadmin</a> <a href="https://floss.social/tags/Linuxhowto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxhowto</a> <a href="https://ostechnix.com/create-chroot-environments-using-mmdebstrap-in-debian-linux/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/create-chroot-environments-using-mmdebstrap-in-debian-linux/</a>

Kevin Karhan :verified:<a href="https://hackers.town/@calcifer" class="u-url mention" rel="nofollow noopener" target="_blank">@calcifer</a> personally, I want really simple applications that have all their dependencies statically.compiled into them and run under their own "username" to enshure encapsulation and isolation...<ul><li>is that <a href="https://infosec.space/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> <a href="https://infosec.space/tags/jails" class="mention hashtag" rel="nofollow noopener" target="_blank">#jails</a> / <a href="https://infosec.space/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#bhyve</a> but worse?</li></ul>

Josh Braun<a href="https://toot.liw.fi/@liw" class="u-url mention" rel="nofollow noopener" target="_blank">@liw</a> <a href="https://fediscience.org/@martinvermeer" class="u-url mention" rel="nofollow noopener" target="_blank">@martinvermeer</a> Yeah, given the number of times my Linux machine has refused to boot properly after an update, I’m not exactly crowing about this. 😂 <a href="https://sciences.social/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a>

V_SAND WE ARE LIVE!!!STEP ONE COMPLETE!! Now to learn how to use the darn thing.Also the <a href="https://furry.engineer/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> idea worked!! I AM RUNNING APPIMAGES ON VOID LINUX!!! L E T ' S F _ C K I N G G O O O O O O O O O O O O O _<a href="https://furry.engineer/tags/voidlinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#voidlinux</a> <a href="https://furry.engineer/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://furry.engineer/tags/hardwarehacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardwarehacking</a> <a href="https://furry.engineer/tags/logicanalyzer" class="mention hashtag" rel="nofollow noopener" target="_blank">#logicanalyzer</a> <a href="https://furry.engineer/tags/HYPED" class="mention hashtag" rel="nofollow noopener" target="_blank">#HYPED</a> <a href="https://furry.engineer/tags/EXCITED" class="mention hashtag" rel="nofollow noopener" target="_blank">#EXCITED</a>

Recent searches

Search options

Administered by:

Server stats:

#chroot