toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

276
active users

#chroot

0 posts0 participants0 posts today
Verfassungklage@troet.cafe<p><a href="https://troet.cafe/tags/Root" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Root</span></a>-Zugriff für alle: </p><p><a href="https://troet.cafe/tags/Kritische" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kritische</span></a> <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sudo</span></a>-Lücke gefährdet unzählige <a href="https://troet.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>-Systeme</p><p><a href="https://troet.cafe/tags/Forscher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forscher</span></a> haben eine gefährliche <a href="https://troet.cafe/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sicherheitslücke</span></a> im <a href="https://troet.cafe/tags/Kommandozeilentool" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kommandozeilentool</span></a> <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sudo</span></a> entdeckt. Angreifer können mit wenig Aufwand Root-Rechte erlangen.</p><p>Die <a href="https://troet.cafe/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sicherheitslücke</span></a> besteht laut Blogbeitrag der <a href="https://troet.cafe/tags/Forscher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forscher</span></a> seit der im Juni 2023 veröffentlichten <a href="https://troet.cafe/tags/Sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sudo</span></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">#<span>Chroot</span></a>- <a href="https://troet.cafe/tags/Implementierung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Implementierung</span></a>. </p><p><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"><span class="invisible">https://www.</span><span class="ellipsis">golem.de/news/root-zugriff-fue</span><span class="invisible">r-alle-kritische-sudo-luecke-gefaehrdet-unzaehlige-linux-systeme-2507-197635.html</span></a></p>
r1w1s1I wrote a simple shell script to manage a Slackware chroot environment for building packages.<br><br>Tested with Slackware-current. You can create and access the chroot easily with just a few commands.<br><br>Source:<br><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><br><br><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><br>
Victoria Stuart 🇨🇦 🏳️‍⚧️<p>Linux superusers: chroot Technique - Linux Swiss army multi-tool<br><a href="https://livesys.se/posts/the-chroot-technique/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">livesys.se/posts/the-chroot-te</span><span class="invisible">chnique/</span></a><br><a href="https://news.ycombinator.com/item?id=43632379" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">3632379</span></a></p><p><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> <a href="https://mastodon.social/tags/BootProcess" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BootProcess</span></a> <a href="https://mastodon.social/tags/RescueDisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RescueDisk</span></a> <a href="https://mastodon.social/tags/SystemRecovery" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SystemRecovery</span></a></p>
mirabilos<p><span class="h-card"><a href="https://mastodon.infra.de/@galaxis" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>galaxis</span></a></span> you might like <a href="https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/sysadmin/debchroot.sh;hb=HEAD" rel="nofollow noopener" target="_blank">https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/sysadmin/debchroot.sh;hb=HEAD</a> to take care of the <a href="https://toot.mirbsd.org/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> mount dance and perhaps even the <a href="https://toot.mirbsd.org/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> support for <a href="https://toot.mirbsd.org/tags/initramfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>initramfs</span></a> unlocking from <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164#14" rel="nofollow noopener" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164#14</a> (which gets around issues with some IPv4 configs where the gateway is out of the subnet). HTH &amp; HAND</p>
Linux TLDR<p>Atoms is a Linux Chroot Management Tool with a User-Friendly GUI<br><a href="https://noc.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://noc.social/tags/Atoms" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Atoms</span></a> <a href="https://noc.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chroot</span></a> <a href="https://noc.social/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SysAdmin</span></a> <a href="https://noc.social/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a><br><a href="https://linuxtldr.com/atoms-tool/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">linuxtldr.com/atoms-tool/</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hackers.town/@calcifer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>calcifer</span></a></span> personally, I want really simple applications that have all their dependencies statically.compiled into them <em>and</em> run under their own <em>"username"</em> to enshure encapsulation and isolation...</p><ul><li>is that <a href="https://infosec.space/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> <a href="https://infosec.space/tags/jails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jails</span></a> / <a href="https://infosec.space/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bhyve</span></a> <em>but worse</em>?</li></ul>
Josh Braun<p><span class="h-card" translate="no"><a href="https://toot.liw.fi/@liw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>liw</span></a></span> <span class="h-card" translate="no"><a href="https://fediscience.org/@martinvermeer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>martinvermeer</span></a></span> 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">#<span>chroot</span></a></p>
scy<p>TIL about <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></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">#<span>chroot</span></a> style environment for a service, simply by defining what directories it should have access to right there in the unit file.</p><p>Depending on what you need, you can use an allowlist-based approach using TemporaryFileSystem &amp; ReadWritePaths, or a blocklist-based one with InaccessiblePaths.</p><p><a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">freedesktop.org/software/syste</span><span class="invisible">md/man/latest/systemd.exec.html</span></a></p><p><a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p>
ricardo :mastodon:<p><a href="https://fosstodon.org/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chroot</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> command with examples </p><p><a href="https://www.rosehosting.com/blog/chroot-linux-commands/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">rosehosting.com/blog/chroot-li</span><span class="invisible">nux-commands/</span></a></p>
gyptazyYou can find some newer packages for <a href="https://gyptazy.ch/snac?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://gyptazy.ch/snac?t=bookworm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bookworm</a> (which is used by the <a href="https://gyptazy.ch/snac?t=visionfive" class="mention hashtag" rel="nofollow noopener" target="_blank">#VisionFive</a> <a href="https://gyptazy.ch/snac?t=visionfive2" class="mention hashtag" rel="nofollow noopener" target="_blank">#VisionFive2</a> board) than the 2022 snapshot old ones for <a href="https://gyptazy.ch/snac?t=riscv" class="mention hashtag" rel="nofollow noopener" target="_blank">#RISCV</a> on <a href="https://gyptazty.ch" rel="nofollow noopener" target="_blank">https://gyptazty.ch.</a> But you can also grab my whole QEMU image to build it yourself or just spawn up a <a href="https://gyptazy.ch/snac?t=chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#chroot</a> with <a href="https://gyptazy.ch/snac?t=qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> static (qemu-riscv64-static) by running:<br><br>mmdebstrap --architectures=riscv64 --aptopt='Acquire::Check-Valid-Until "false"' --include="debian-ports-archive-keyring" sid /srv/riscv64-chroot "deb [trusted=yes] <a href="https://snapshot.debian.org/archive/debian-ports/20220616T194833Z" rel="nofollow noopener" target="_blank">https://snapshot.debian.org/archive/debian-ports/20220616T194833Z</a> unstable main"<br><br>cp /usr/bin/qemu-riscv64-static /srv/riscv64-chroot/usr/bin/<br><br>chroot /srv/riscv64-chroot/ qemu-riscv64-static /bin/bash<br><br><a href="https://gyptazy.ch/snac?t=risc" class="mention hashtag" rel="nofollow noopener" target="_blank">#risc</a> <a href="https://gyptazy.ch/snac?t=riscv" class="mention hashtag" rel="nofollow noopener" target="_blank">#riscv</a> <a href="https://gyptazy.ch/snac?t=risc64" class="mention hashtag" rel="nofollow noopener" target="_blank">#risc64</a> <a href="https://gyptazy.ch/snac?t=riscv64" class="mention hashtag" rel="nofollow noopener" target="_blank">#riscv64</a> <a href="https://gyptazy.ch/snac?t=starfive" class="mention hashtag" rel="nofollow noopener" target="_blank">#starfive</a> <a href="https://gyptazy.ch/snac?t=vision" class="mention hashtag" rel="nofollow noopener" target="_blank">#vision</a> <a href="https://gyptazy.ch/snac?t=packages" class="mention hashtag" rel="nofollow noopener" target="_blank">#packages</a> <a href="https://gyptazy.ch/snac?t=crosscompile" class="mention hashtag" rel="nofollow noopener" target="_blank">#crosscompile</a> <a href="https://gyptazy.ch/snac?t=foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a><br>
Linux TLDR<p>Atoms is a Linux Chroot Management Tool with a User-Friendly GUI<br><a href="https://noc.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://noc.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://noc.social/tags/Chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chroot</span></a> <a href="https://noc.social/tags/Atoms" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Atoms</span></a> <a href="https://noc.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://noc.social/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a> <a href="https://noc.social/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a><br><a href="https://linuxtldr.com/atoms-tool/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">linuxtldr.com/atoms-tool/</span><span class="invisible"></span></a></p>
V_S<p>AND WE ARE LIVE!!!</p><p>STEP ONE COMPLETE!! Now to learn how to use the darn thing.</p><p>Also the <a href="https://furry.engineer/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></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 _</p><p><a href="https://furry.engineer/tags/voidlinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>voidlinux</span></a> <a href="https://furry.engineer/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://furry.engineer/tags/hardwarehacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardwarehacking</span></a> <a href="https://furry.engineer/tags/logicanalyzer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>logicanalyzer</span></a> <a href="https://furry.engineer/tags/HYPED" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HYPED</span></a> <a href="https://furry.engineer/tags/EXCITED" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EXCITED</span></a></p>
V_S<p><span class="h-card" translate="no"><a href="https://hackers.town/@thegibson" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thegibson</span></a></span> Setting up <a href="https://furry.engineer/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> on <a href="https://furry.engineer/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> <a href="https://furry.engineer/tags/voidlinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>voidlinux</span></a> to <a href="https://furry.engineer/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> into for installing <a href="https://furry.engineer/tags/leapmotion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>leapmotion</span></a> software to control my new hand/motion tracker/controller, only for the software to spit out this:</p><p>Error: Missing Dependency: glibc</p><p>Thought I could cheat the system. Long story short, installed the GLIBC variant of Void on a USB, booted into it, and redid the process of converting and installing (guide coming soon).</p>
Tech News Worldwide<p>How to Use chroot to Restrict SSH User Access to Certain Directory <br> <br> <a href="https://www.linuxtoday.com/developer/how-to-restrict-ssh-user-access-using-chrooted-jail/" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linuxtoday.com/developer/how-t</span><span class="invisible">o-restrict-ssh-user-access-using-chrooted-jail/</span></a> <br> <br> <a href="https://aspiechattr.me/tags/useraccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>useraccess</span></a> <a href="https://aspiechattr.me/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Developer</span></a> <a href="https://aspiechattr.me/tags/tutorial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tutorial</span></a> <a href="https://aspiechattr.me/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> <a href="https://aspiechattr.me/tags/Jail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Jail</span></a> <a href="https://aspiechattr.me/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a></p>
Yann Büchau :nixos:<p>How future-proof are <a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> images? Will it always be possible in the future to launch a container from an ancient docker image?</p><p>A <a href="https://fosstodon.org/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a>-able directory tree is extremely future-proof, isn't it? No extra software needed, right?</p><p>The whole <a href="https://fosstodon.org/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NixOS</span></a> / <a href="https://fosstodon.org/tags/GUIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GUIX</span></a> approach looks nice and you would just need <a href="https://fosstodon.org/tags/plaintext" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>plaintext</span></a> files to share an environment, but it seems fragile in terms of future source code availability of all dependencies.</p><p><a href="https://fosstodon.org/tags/reproducibleResearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reproducibleResearch</span></a> <a href="https://fosstodon.org/tags/reproducibleBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reproducibleBuilds</span></a> <a href="https://fosstodon.org/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>askfedi</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/research" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>research</span></a></p>
Tech News Worldwide<p>CShell/SNX chrooted Wrapper Automated Setup for Linux <br> <br> <a href="https://www.linuxtoday.com/developer/cshell-snx-chrooted-wrapper-automated-setup-linux/" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linuxtoday.com/developer/cshel</span><span class="invisible">l-snx-chrooted-wrapper-automated-setup-linux/</span></a> <br> <br> <a href="https://aspiechattr.me/tags/CShellCheckpoint" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CShellCheckpoint</span></a> <a href="https://aspiechattr.me/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Developer</span></a> <a href="https://aspiechattr.me/tags/chroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chroot</span></a> <a href="https://aspiechattr.me/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> <a href="https://aspiechattr.me/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://aspiechattr.me/tags/SNX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SNX</span></a></p>