MastodonTech.de

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>

Marcel SIneM(S)US<a href="https://social.tchncs.de/tags/chwoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chwoot</a>: Kritische <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> :tux: -Lücke macht Nutzer auf den meisten Systemen zu Root | Security <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/Patchday" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patchday</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/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> :ubuntu: <a href="https://social.tchncs.de/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> :fedora: <a href="https://social.tchncs.de/tags/SuSe" class="mention hashtag" rel="nofollow noopener" target="_blank">#SuSe</a> <a href="https://social.tchncs.de/tags/OpenSuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSuse</a> :opensuse: <a href="https://social.tchncs.de/tags/RedHatEnterpriseLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHatEnterpriseLinux</a> <a href="https://social.tchncs.de/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RHEL</a>

Deutschland<a href="https://www.europesays.com/de/234230/" rel="nofollow noopener" translate="no" target="_blank">https://www.europesays.com/de/234230/</a> chwoot: Kritische Linux-Lücke macht Nutzer auf den meisten Systemen zu Root <a href="https://pubeurope.com/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> <a href="https://pubeurope.com/tags/Deutschland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Deutschland</a> <a href="https://pubeurope.com/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> <a href="https://pubeurope.com/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://pubeurope.com/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://pubeurope.com/tags/Science" class="mention hashtag" rel="nofollow noopener" target="_blank">#Science</a> <a href="https://pubeurope.com/tags/Science" class="mention hashtag" rel="nofollow noopener" target="_blank">#Science</a>&Technology <a href="https://pubeurope.com/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://pubeurope.com/tags/Sicherheitsl%C3%BCcken" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücken</a> <a href="https://pubeurope.com/tags/sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#sudo</a> <a href="https://pubeurope.com/tags/Technik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technik</a> <a href="https://pubeurope.com/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://pubeurope.com/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> <a href="https://pubeurope.com/tags/Wissenschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wissenschaft</a> <a href="https://pubeurope.com/tags/Wissenschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wissenschaft</a>&Technik

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>

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>

Hacker NewsThe chroot Technique – a Swiss army multitool for Linux systems<a href="https://livesys.se/posts/the-chroot-technique/" rel="nofollow noopener" translate="no" target="_blank">https://livesys.se/posts/the-chroot-technique/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/multitool" class="mention hashtag" rel="nofollow noopener" target="_blank">#multitool</a> <a href="https://mastodon.social/tags/system" class="mention hashtag" rel="nofollow noopener" target="_blank">#system</a> <a href="https://mastodon.social/tags/administration" class="mention hashtag" rel="nofollow noopener" target="_blank">#administration</a> <a href="https://mastodon.social/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#open</a>-source <a href="https://mastodon.social/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://mastodon.social/tags/tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#tips</a>

r1w1s1Clear explanation on how FreeBSD jails compare to containers. I have used in the past <a href="https://snac.bsd.cafe?t=docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> and <a href="https://snac.bsd.cafe?t=lxc" class="mention hashtag" rel="nofollow noopener" target="_blank">#lxc</a>. For my <a href="https://snac.bsd.cafe?t=slackbuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#slackbuilds</a> I'm still using <a href="https://snac.bsd.cafe?t=chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> works great.

nico[lien] <a href="https://github.com/mlocati/docker-php-extension-installer" rel="nofollow noopener" target="_blank">mlocati/docker-php-extension-installer: Easily install PHP extensions in Docker containers</a> <a class="hashtag" href="https://social.tourmentine.com/tag/chroot" rel="nofollow noopener" target="_blank">#chroot</a> <a class="hashtag" href="https://social.tourmentine.com/tag/gik" rel="nofollow noopener" target="_blank">#gik</a> <a class="hashtag" href="https://social.tourmentine.com/tag/php" rel="nofollow noopener" target="_blank">#php</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>

jjj333_p (Official Cat of ari.lt)<a class="u-url mention" href="https://mk.cpluspatch.com/@jessew" rel="nofollow noopener" target="_blank">@jessew</a> chaos is still alive, less active probably but today is one of its more active days and i know ari from <a class="hashtag" href="https://ak.ari.lt/tag/lounge" rel="nofollow noopener" target="_blank">#lounge</a>:envs.net then we branched off into root (general room for her hs) and then i became mod because rare sane braincell, and then shit happened and now i have <a class="hashtag" href="https://ak.ari.lt/tag/chroot" rel="nofollow noopener" target="_blank">#chroot</a>:envs.net which just kinda exists

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>

nico[lien] <a href="https://github.com/workadventure/workadventure" rel="nofollow noopener" target="_blank">workadventure/workadventure: A collaborative web application (virtual office) presented as a 16-bit RPG video game</a> <a class="hashtag" href="https://social.tourmentine.com/tag/chroot" rel="nofollow noopener" target="_blank">#chroot</a> <a class="hashtag" href="https://social.tourmentine.com/tag/games" rel="nofollow noopener" target="_blank">#games</a> <a class="hashtag" href="https://social.tourmentine.com/tag/16bit" rel="nofollow noopener" target="_blank">#16bit</a> <a class="hashtag" href="https://social.tourmentine.com/tag/gik" rel="nofollow noopener" target="_blank">#gik</a> <a class="hashtag" href="https://social.tourmentine.com/tag/taf" rel="nofollow noopener" target="_blank">#taf</a>

Linux TLDRAtoms is a Linux Chroot Management Tool with a User-Friendly GUI <a href="https://noc.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://noc.social/tags/Atoms" class="mention hashtag" rel="nofollow noopener" target="_blank">#Atoms</a> <a href="https://noc.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a> <a href="https://noc.social/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a> <a href="https://noc.social/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> <a href="https://linuxtldr.com/atoms-tool/" rel="nofollow noopener" target="_blank">https://linuxtldr.com/atoms-tool/</a>

Wintermute_BBStinkering with the Linux Binary Compatibility of <a href="https://oldbytes.space/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> - I just set up an <a href="https://oldbytes.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> environment under /compat/ubuntu and did a <a href="https://oldbytes.space/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> into it. Then I've added a few more packages like xa65 , build-essential etc. and then cloned and successfully built <a href="https://oldbytes.space/tags/RomWBW" class="mention hashtag" rel="nofollow noopener" target="_blank">#RomWBW</a> with this setup.Another problem solved, well at least I can build RomWBW images on my FreeBSD system.As for actually burning the resulting ROM image to a real <a href="https://oldbytes.space/tags/chip" class="mention hashtag" rel="nofollow noopener" target="_blank">#chip</a> ... let's just say that support for <a href="https://oldbytes.space/tags/Batronix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Batronix</a> usb devices is still ... err ... non-existent ... (I knew about this, so not surprised)

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>

Pascal LeinertIhr wollt wissen wie gut es läuft? Ich habe es geschafft mich aus dem Root und User Account auszusperren und komme trotz dem Ändern der Passwörter in <a href="https://mastodon.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a> nicht mehr ins System rein. Ein Rebuild in Chroot geht leider auch nicht.Ich darf wohl von vorne anfangen. :BlobhajSadReach: <a href="https://mastodon.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

scyTIL about <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>'s TemporaryFileSystem, ProtectSystem, ProtectHome, InaccessiblePaths, ReadOnlyPaths and a bunch more related options, which allow you to easily set up a <a href="https://chaos.social/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> style environment for a service, simply by defining what directories it should have access to right there in the unit file.Depending on what you need, you can use an allowlist-based approach using TemporaryFileSystem & ReadWritePaths, or a blocklist-based one with InaccessiblePaths.<a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html" rel="nofollow noopener" translate="no" target="_blank">https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html</a><a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

ricardo :mastodon:<a href="https://fosstodon.org/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chroot</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> command with examples <a href="https://www.rosehosting.com/blog/chroot-linux-commands/" rel="nofollow noopener" translate="no" target="_blank">https://www.rosehosting.com/blog/chroot-linux-commands/</a>

eshep<a href="https://mast.linuxgamecast.com/users/Venn" class="u-url mention" rel="nofollow noopener" target="_blank">@Venn</a> I really hope <a href="https://social.trom.tf/search?tag=Volla" class="mention hashtag" rel="nofollow noopener" target="_blank">#Volla</a> can pull it off. They're surely in a better position for it than most. It'd be even better if they could ship their stuff to US or JP.These days I've all but given up on dedicated <a href="https://social.trom.tf/search?tag=linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> tablets/phones. Even though we have loads of em that are capable of running <a href="https://social.trom.tf/search?tag=postmarketOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#postmarketOS</a>, most of em still fall short of usable most of the time. The only folks who seem to have nailed the linux handheld experience is the <a href="https://social.trom.tf/search?tag=SailfishOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SailfishOS</a> team. But of course there's a problem with that'n as well; if you're outside the EU, you'll have to suffer the trimmed-down DIY version of it.These days I've found it much more practical to run something in a <a href="https://social.trom.tf/search?tag=chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> environment within <a href="https://social.trom.tf/search?tag=termux" class="mention hashtag" rel="nofollow noopener" target="_blank">#termux</a>. I runs quite well on nearly any <a href="https://social.trom.tf/search?tag=android" class="mention hashtag" rel="nofollow noopener" target="_blank">#android</a> capable device via <a href="https://social.trom.tf/search?tag=proot" class="mention hashtag" rel="nofollow noopener" target="_blank">#proot</a>, or even better in a proper chroot on a rooted one.

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#chroot