YouTube video by Shai Isenberg

Twenty router models sold on Amazon, AliExpress, and Alibaba ship with a remote-control implant enabled by default. It runs as root, it uses no encryption, and it authenticates nobody. Whoever answers the phone owns the device.

The Reddit post highlights that Zbtlink routers contain a backdoor named rctl. The linked VulnCheck blog provides details about this security vulnerability. The backdoor allows unauthorized access to the affected routers.

Le rapport VulnCheck cible le composant rctl, décrit par Zbtlink comme un outil de support technique après-vente destiné à aider les clients dans le dépannage et la configuration de leurs appareils, uniquement sur demande explicite et autorisation du client. Zbtlink affirme que ce composant n'a jamais été utilisé pour des accès non autorisés.

Chinese router manufacturer Zbtlink has become the focus of a significant dispute following the discovery of a concealed remote management mechanism embedded in its proprietary firmware. Researchers at VulnCheck assert that affected devices autonomously establish connections to external servers and permit the remote execution of system-level commands. The company has denied that the component constitutes a backdoor - while simultaneously suspending firmware downloads citing unspecified security vulnerabilities.

VulnCheck disclosed ENDLESSDOORS, a factory-shipped backdoor embedded in at least 20 Zbtlink router models and present across all 21 available firmware images. The implant runs at boot, phones home to multiple command-and-control endpoints, and can be hijacked to grant attackers a live root shell on affected devices. #ENDLESSDOORS #Zbtlink #rctl...

YouTube video by Yale Interventional Cardiology

Mindfulness interventions may provide medical practitione...

<img src="https://it-notes.dragas.net/featured/lock_jail.webp" alt="featured image" referrerpolicy="no-referrer"><p>FreeBSD allows for quite comprehensive resource limitation for one or more jails. Beyond the official documentation, there is a good description <a href="https://mwl.io/nonfiction/os#fmjail"target="_blank" rel="external nofollow noopener noreferrer">in MWL’s book</a>. There’s also <a href="https://klarasystems.com/articles/controlling-resource-limits-with-rctl-in-freebsd/"target="_blank" rel="external nofollow noopener noreferrer">an interesting article from Klara Systems</a> that describes some functionalities.</p> <p>Sometimes, however, we only need the processes running within a specific jail to have a specific priority - higher or lower than others.</p> <p>There are many methods to achieve this, but the simplest one, in my opinion, is to leverage the properties of the <code>nice(1)</code> command. The main property, in fact, is to transmit the set priority to child processes, so all processes launched by the command that received a different level of “niceness” will inherit its priority.</p> <p>For example, to give the minimum priority to the services launched within a jail, just modify the <code>.conf</code> file of the jail (in the case of a standard BastilleBSD installation, the file will be <code>/usr/local/bastille/jails/jailname/jail.conf</code>) and change the command</p> <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code><span class="lnt">1 </span></code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">exec.start = '/bin/sh /etc/rc';</span></span></code></pre></td></tr></table> </div> </div><p>to:</p> <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code><span class="lnt">1 </span></code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">exec.start = '/usr/bin/nice -n 20 /bin/sh /etc/rc';</span></span></code></pre></td></tr></table> </div> </div><p>In this way, when <code>rc</code> starts at the jail’s boot, it will have a niceness of 20 and will transmit it to all the processes that <code>rc</code> itself launches (thus all the services of the jail).</p> <p><strong>Note</strong>: This will only apply to child processes of <code>rc</code>, not to:</p> <ul> <li>Commands manually launched from the jail console</li> <li>Services launched by running <code>service servicename start</code> (or restart) from the jail shell. This is because, in this case, the process will not be a child of <code>rc</code> but will derive directly from the console in use.</li> </ul> <p>Using the <code>nice</code> command to set the priority of processes within a FreeBSD jail is a simple and effective method. However, it is important to be aware of the limitations of this approach and ensure that manually executed commands are managed accordingly.</p>

Malam puncak perayaan HUT ke-33 MNCTV Road To Kilau Raya K33setiaan digelar spektakuler. Acara disiarkan langsung MNCTV dari Studio RCTl+, Kebon Jeruk, Jakarta.

A small program to help systemd users switch to openrc

AppJail is an open source framework entirely written in sh(1) and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Features: * Easy to use. * Parallel startup (Jails & NAT). * UFS and ZFS support. * RACCT/RCTL support. * NAT support. * Port expose - network port forwarding into jail. * IPv4 and IPv6 support. * DHCP and SLAAC support. * Virtual networks - A jail can be on several virtual networks at the same time. * Bridge support. * VNET support * Deploy your applications much easier using Makejail! * Netgraph support. * LinuxJails support. * Supports thin and thick jails. * TinyJails - Experimental feature to create a very stripped down jail that is very useful to distribute. * Startup order control - Using priorities and the boot flag makes management much easier. * Jail dependency support. * Initscripts - Make your jails interactive! * Backup your jails using tarballs or raw images (ZFS only) with a single command. * Modular structure - each command is a unique file that has its own responsability in AppJail. This makes AppJail maintenance much easier. * Table interface - many commands have a table-like interface, which is very familiar to many sysadmin tools. * No databases - each configuration is separated in each entity (networks, jails, etc.) which makes maintenance much easier. * Supervisor - Coming soon ... * ... Project: https://github.com/DtxdF/AppJail Notes: Hi! I want to share a tool I created to test my ports, to learn more about jails and just as a hobby. My main motivation is a tool for system administrators and developers. AppJail has a useful feature called Makejail, which is somewhat similar to Dockerfile. The idea is to use a file that contains the steps to create a jail with its configured packages. I have created a _`PR 269631`_ to port it to the ports collection.

AppJail is an open source framework entirely written in sh(1) and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Features: * Easy to use. * Parallel startup (Jails & NAT). * UFS and ZFS support. * RACCT/RCTL support. * NAT support. * Port expose - network port forwarding into jail. * IPv4 and IPv6 support. * DHCP and SLAAC support. * Virtual networks - A jail can be on several virtual networks at the same time. * Bridge support. * VNET support * Deploy your applications much easier using Makejail! * Netgraph support. * LinuxJails support. * Supports thin and thick jails. * TinyJails - Experimental feature to create a very stripped down jail that is very useful to distribute. * Startup order control - Using priorities and the boot flag makes management much easier. * Jail dependency support. * Initscripts - Make your jails interactive! * Backup your jails using tarballs or raw images (ZFS only) with a single command. * Modular structure - each command is a unique file that has its own responsability in AppJail. This makes AppJail maintenance much easier. * Table interface - many commands have a table-like interface, which is very familiar to many sysadmin tools. * No databases - each configuration is separated in each entity (networks, jails, etc.) which makes maintenance much easier. * Supervisor - Coming soon ... * ... Project: https://github.com/DtxdF/AppJail Notes: Hi! I want to share a tool I created to test my ports, to learn more about jails and just as a hobby. My main motivation is a tool for system administrators and developers. AppJail has a useful feature called Makejail, which is somewhat similar to Dockerfile. The idea is to use a file that contains the steps to create a jail with its configured packages. I have created a _`PR 269631`_ to port it to the ports collection.

This link will take you to a page that’s not on LinkedIn