paigeadelethompson

#!/usr/bin/env bash

set -e

# Function to handle cleanup on exit
cleanup() {
    local exit_code=$?
    echo "Cleaning up..."
    
    # First try to exit chroot if we're in it

paigeadelethompson

❯ sudo ifconfig
ix0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
        ether 98:b7:85:1e:de:4d
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
ix1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        options=4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
        ether 98:b7:85:1e:de:4e

paigeadelethompson

chronyd_enable=YES
dnsmasq_enable=YES 
sshd_enable=YES
hostname=stelleri.netcrave.network 
powerd_enable=YES
moused_nondefault_enable=NO
dumpdev=NO
zfs_enable=YES
gateway_enable=YES
ipv6_gateway_enable=YES

paigeadelethompson

#!/usr/bin/env bash

set -e

# Function to handle cleanup on exit
cleanup() {
    local exit_code=$?
    echo "Cleaning up..."
    
    # First try to exit chroot if we're in it

paigeadelethompson

I would like to understand a few things:

    What actually precipitated this?
    Why did it take so long for the problem to be addressed?
    What will be done (if anything) to avoid making such an impactful mistake again?

Among the things that I've been letting slide that I would like to understand are:

    Who are the people who actually have write access to this repository; what actually endorses their trustworthiness and sets them apart from for example a state sponsored actor who's intention is to distribute malware? To be perfectly fair, I've made pull requests myself but who I am is pretty up front and I've been nothing short of generous in making available a means to reach me for professional inquiries. I don't really see that in the accounts that actually maintain Void. I suppose I'd just take somebody at their word that there's some level of discretion but who's word would that be? Who is actually willing to endorse this?

paigeadelethompson

#!/usr/bin/env bash

set -e

# Function to handle cleanup on exit
cleanup() {
    local exit_code=$?
    echo "Cleaning up..."
    
    # First try to exit chroot if we're in it

paigeadelethompson

{
    "output": {
        "blocklist": [],
        "compressor#0": {
            "attack": 20.0,
            "boost-amount": 6.0,
            "boost-threshold": -72.0,
            "bypass": false,
            "dry": -100.0,
            "hpf-frequency": 10.0,

paigeadelethompson

{
    "output": {
        "blocklist": [],
        "compressor#0": {
            "attack": 15.0,
            "boost-amount": 8.0,
            "boost-threshold": -72.0,
            "bypass": false,
            "dry": -100.0,
            "hpf-frequency": 10.0,

paigeadelethompson

{
    "output": {
        "blocklist": [],
        "equalizer#0": {
            "balance": 0.0,
            "bypass": false,
            "input-gain": 0.0,
            "left": {
                "band0": {
                    "frequency": 22.409377607517197,

paigeadelethompson

(nrf) ➜  hci_usb rm -rf build
(nrf) ➜  hci_usb west build --board=nrf52840dk/nrf52840 --no-sysbuild

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/netcraveos/hci_usb
-- CMake version: 3.31.6
-- Found Python3: /usr/bin/python3 (found suitable version "3.13.2", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /home/netcraveos/.cache/zephyr
-- Zephyr version: 4.0.99 (/home/netcraveos/.oh-my-sdk/dist/nrf/zephyr)