cablespaghetti.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Site description
Cablespaghetti's personal snac instance
Admin email
sam@cablespaghetti.dev
Admin account
@sam@cablespaghetti.dev

Search results for tag #security

[?]gyptazy » 🌐
@gyptazy@gyptazy.com

AI assisted pen testing, coding and arising secvulns. Are we humans still good enough?

the last weeks we saw more and more security issues coming up. Let's talk!

Sorry, a pretty long blog post about this...

https://gyptazy.com/blog/coding-after-ai-are-humans-still-good-enough/


Let's talk about AI slops - like this image!

Alt...Let's talk about AI slops - like this image!

    [?]h3artbl33d :openbsd: :antifa: [Try/Me] » 🌐
    @h3artbl33d@exquisite.social

    About that... We now have a fourth vulnerability: ssh-keysign-pwn. Despite the first three letters, this is a Linux kernel vuln. PoC already available.

      [?]Trezzer (aka Helvedeshunden) [He/him/they] » 🌐
      @trezzer@social.linux.pizza

      OK. With Bitwarden acting every bit the American company it is, are there any drop-in replacements out there? Preferably standalone rather than part of a package. fastcompany.com/91542655/bitwa

        [?]LWN.net » 🌐
        @lwn@fedi.lwn.net

        [?]Python Software Foundation » 🌐
        @ThePSF@fosstodon.org

        🔐 Catch PSF's PyPI Safety and Security Engineer, @miketheman, talking Trusted Publishing at next week! Learn how to eliminate long-lived credentials from your release workflow: no tokens, no secrets, just secure deploys. Tue May 19 @ 11am CDT
        osselcna2026.sched.com/event/2

          [?]Liam @ GamingOnLinux 🐧🎮 » 🌐
          @gamingonlinux@mastodon.social

          [?]LWN.net » 🌐
          @lwn@fedi.lwn.net

          WTL boosted

          [?]Rob🫟 » 🌐
          @robchapman@ohai.social

          Benn Jordan at his tech best, again - this time hunting & hacking robot dogs

          Robot Dogs Are A Security Nightmare

          youtube.com/watch?v=lA8WuXDXfcI

            feld boosted

            [?]h3artbl33d :openbsd: :antifa: [Try/Me] » 🌐
            @h3artbl33d@exquisite.social

            Oh right. Ofcourse Bitlocker encryption can be bypassed with a mere thumbdrive.

            If you MUST use Windows, then at least Veracrypt that shit.

              [?]h3artbl33d :openbsd: :antifa: [Try/Me] » 🌐
              @h3artbl33d@exquisite.social

              Copy Fail, Dirty Frag and now Fragnesia...

              Upside: if you have already ripped out esp4, esp6 and rxrpc for Dirty Frag, you already have the mitigation in place for Fragnesia.

                [?]LWN.net » 🌐
                @lwn@fedi.lwn.net

                [?]Liam @ GamingOnLinux 🐧🎮 » 🌐
                @gamingonlinux@mastodon.social

                [?]TelH90 » 🌐
                @kkarhan@c.im

                @GossiTheDog I never trusted with it's - anyway!

                - Cuz now people put that trust into some IC () that is usually soldered down on the board that may or may not be from the factory (whether due to , or "Export Restrictions " is irrelevant for the affected End-Users!)…

                - If (for some horrible reason that I refuse to acknowledge as legitimate!) someone needs a machine BUT with , they should use the only REAL : !

                never was about

                - Calling it "" is adopting the enemy's -Speak!

                  It's Just Me boosted

                  [?]Stefano Marinelli » 🌐
                  @stefano@mastodon.bsd.cafe

                  Today I spoke with someone I've known for a very long time. We have a relationship of mutual trust, and when I can, I answer his questions about technology. Today he managed to put me in a difficult position.

                  He is going through a hard time and would like to do something, but doing it would require him to join a club. This club, although legitimate, legal, and in my eyes perfectly acceptable, could cause him some trouble at work if that information ever came out. Not so much in today's world, but in the world tomorrow may turn into.

                  Five years ago I would have told him to go ahead, without hesitation. Today, I truly could not reassure him. On the one hand, there is nothing bad or wrong about it. On the other, I no longer trust those who manage our personal data.

                  A provider has already notified me three times in the past year that my data was involved in a breach. Because of a particular relationship I have with them, I asked for clarification, and they explained that development, which is not managed by them, has become lower quality and that changing company is difficult. At the same time, they are worried about the repercussions.

                  Now: the fact that I am a customer of that company is not a problem. Even less so my email address, or the hash of my unique password. But if this acquaintance of mine were to be affected by a data breach in that context, he would be taking a serious risk. Much greater than he suspects.

                  So tonight I'm in limbo. He thanked me and decided not to sign up. I feel guilty, perhaps, for having been overly cautious.

                    [?]LWN.net » 🌐
                    @lwn@fedi.lwn.net

                    [?]LWN.net » 🌐
                    @lwn@fedi.lwn.net

                    Stenberg: Mythos finds a curl vulnerability

                    lwn.net/Articles/1072325/

                      [?]LWN.net » 🌐
                      @lwn@fedi.lwn.net

                      [?]Jeri Dansky [She/her] » 🌐
                      @jeridansky@sfba.social

                      One of the first things I saw upon returning home, staring me in the face at San Francisco airport.

                      My immediate reaction: Fuck you, Cisco. (Which I guess could be unfair, since I have zero knowledge about what's going on at Cisco specifically. This was just a gut reaction at seeing AI yet again.)

                      A big banner handing from the ceiling which says:
The infrastructure AI demands.
The security IT requires.

That's followed by the Cisco logo (which includes the company name)  in the lower right-hand corner.

                      Alt...A big banner handing from the ceiling which says: The infrastructure AI demands. The security IT requires. That's followed by the Cisco logo (which includes the company name) in the lower right-hand corner.

                        WTL boosted

                        [?]James Endres Howell » 🌐
                        @jameshowell@fediscience.org

                        MY FUCKING FAVORITE IS THE WEB FORM PASSWORD FIELD THAT WILL NOT LET YOU PASTE YOUR PASSWORD YOU GUYS ARE SO GODDAM SMART WHAT A SNEAKY MOVE TO FOIL THE BAD GUYS I FEEL SO SECURE YOU FUCKING MORONS

                          [?]WTL » 🌐
                          @WTL@mastodon.social

                          My four-month-late :
                          Work: & , , / ,

                          Life: movies, music, , curious and loves to learn, social justice, and to my surprise, a who has 15,477 KM Jan 2020 - Dec 2022.

                          If you stop and look at something the more closely you examine it, the more amazing it becomes.

                          Married to the wonderful @TAV for over 25 years, furdad to Sprocket the , (he/him) ,

                            mc.fly boosted

                            [?]mc.fly [he/him] » 🌐
                            @mcfly@milliways.social

                            Automated scanning.

                            What tools do you use to scan your enviroments for security issues? Why?

                            Not looking for virusscanners here, more for a bit more enterprisy enviroment?

                            Are there things i should have a look at?

                            What is your experience in general?

                            RT welcome for reach.

                              Tom :damnified: boosted

                              [?]Larvitz :fedora: » 🌐
                              @Larvitz@burningboard.net

                              Let's Encrypt just stopped the issuance of certificates after an (so far not publicly disclosed) incident:

                              letsencrypt.status.io/pages/in

                              If anyone encounters issues today with failed certificate renewals: It's probably not your setup.

                                [?]LWN.net » 🌐
                                @lwn@fedi.lwn.net

                                [$] Forgejo "carrot disclosure" raises security questions

                                An unusual, some might say hostile, approach to disclosing an alleged remote-code-execution (RCE) flaw in the Forgejo software-collaboration platform has sparked a multifaceted con [...]

                                lwn.net/Articles/1071499/

                                  [?]LWN.net » 🌐
                                  @lwn@fedi.lwn.net

                                  killswitch for short-term emergency vulnerability mitigation

                                  lwn.net/Articles/1071861/

                                    [?]LWN.net » 🌐
                                    @lwn@fedi.lwn.net

                                    [?]Liam @ GamingOnLinux 🐧🎮 » 🌐
                                    @gamingonlinux@mastodon.social

                                    [?]ARGVMI~1.PIF » 🌐
                                    @argv_minus_one@mastodon.sdf.org

                                    Oh good, another high-severity vulnerability that somebody botched the disclosure of, turning it into a high-severity zero-day.

                                    Because wasn't bad enough. Now we've got too.

                                    Can people please stop botching vulnerability disclosure? Thanks.

                                    github.com/V4bel/dirtyfrag/blo

                                      [?]nixCraft 🐧 » 🌐
                                      @nixCraft@mastodon.social

                                      Dirty Frag: Universal Linux LPE openwall.com/lists/oss-securit

                                      This is a report on "Dirty Frag", a universal LPE that allows obtaining root privileges on all major distributions. This vulnerability has a similar impact to the previous Copy Fail.

                                        [?]Aaron Toponce ⚛️:debian: » 🌐
                                        @atoponce@fosstodon.org

                                        Looks like Instructure got pwned by ShunyHunters. I went to the onion address and it's legit. They've got until May 12, 2026 to pay the ransom or the data gets leaked.

                                        Shown is the screen when logging into Canvas for students to do their homework.

                                        Screenshot from a hacked Canvas page showing the ransom message from ShinyHunters

                                        Alt...Screenshot from a hacked Canvas page showing the ransom message from ShinyHunters

                                          [?]LWN.net » 🌐
                                          @lwn@fedi.lwn.net

                                          Dirty Frag: a zero-day universal Linux LPE

                                          lwn.net/Articles/1071719/

                                            [?]Tailscale » 🌐
                                            @tailscale@hachyderm.io

                                            Day 1 at DEVWorld Amsterdam is a wrap 🇳🇱

                                            Back again tomorrow and we’re also sponsoring the photo booth. Stop by, say hi, and build yourself a keycap fidget toy.

                                              [?]LWN.net » 🌐
                                              @lwn@fedi.lwn.net

                                              [?]IT Notes - https://it-notes.dragas.net » 🤖 🌐
                                              @itnotes@snac.it-notes.dragas.net

                                              Monitor your devices with LibreNMS on FreeBSD

                                              LibreNMS (https://www.librenms.org) has been a faithful companion for years now. It quietly handles the monitoring of my servers, devices, and services without demanding much in return - exactly what you want from a tool whose job is to watch over everything else. It's a solid alternative to heavier solutions like Zabbix, and it gives you alerts, data, and graphs on virtually anything reachable over SNMP.

                                              I usually install it on a host that is not reachable from the outside, then let it poll all the devices through a VPN: a single observation point, clean perimeter. The ability to create multiple dashboards - and to filter them by user - has also let me give clients a transparent window onto their own servers. Transparency, in my experience, is always the better long-term bet.

                                              Together with Uptime-Kuma (https://it-notes.dragas.net/2024/07/22/install-uptime-kuma-freebsd-jail/) (and the good old Nagios/Munin pair), LibreNMS lives in a FreeBSD jail on my monitoring servers and just does its job.

                                              This post walks through a plain installation of LibreNMS on FreeBSD: package-based, no reverse proxy, no HTTPS, no fancy hardening. The goal is to get to a working setup you can build on top of.

                                              Assumptions

                                              • FreeBSD 15.0-RELEASE, in a jail or on a dedicated VM/host
                                              • nginx + php-fpm + MySQL 8.4
                                              • LibreNMS installed from the official package — not via git clone
                                              One note before we start: in this guide I use plain HTTP just to reach the first-time setup. If your LibreNMS instance won't stay confined to a private network or behind a VPN, configuring HTTPS is mandatory, not optional.

                                              Installation

                                              pkg install librenms mysql84-server python3 nginx
                                              LibreNMS currently depends on PHP 8.4. If you want to speed PHP up, install OPcache too:

                                              pkg install php84-opcache

                                              MySQL

                                              Two settings need to be in place before MySQL starts for the first time. After the first start they cannot be changed without reinitializing the data directory, so it's worth getting them right now.

                                              cd /usr/local/etc/mysql
                                              cp my.cnf.sample my.cnf
                                              In the [mysqld] section, add:

                                              innodb_file_per_table=1
                                              lower_case_table_names=0
                                              Now start MySQL:

                                              service mysql-server enable
                                              service mysql-server start
                                              On a fresh FreeBSD install, the local root user can connect to MySQL without a password from the command line. Connect and create the database and user. I'm using password here as a placeholder - don't.

                                              mysql
                                              CREATE DATABASE librenms CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
                                              CREATE USER 'librenms'@'localhost' IDENTIFIED BY 'password';
                                              GRANT ALL PRIVILEGES ON librenms.* TO 'librenms'@'localhost';
                                              exit

                                              php-fpm

                                              Edit /usr/local/etc/php-fpm.d/www.conf and adjust the listen directives:

                                              listen = /var/run/php-fpm-librenms.sock
                                              listen.owner = www
                                              listen.group = www
                                              listen.mode = 0660
                                              Then create php.ini from the production sample:

                                              cd /usr/local/etc
                                              cp php.ini-production php.ini
                                              And set the timezone in php.ini:

                                              date.timezone = Europe/Rome

                                              nginx

                                              Since this jail (or host) is dedicated to LibreNMS, we can rewrite the server block in /usr/local/etc/nginx/nginx.conf directly:

                                              server {
                                              listen 80;
                                              yourServerName
                                              root /usr/local/www/librenms/html;
                                              index index.php;

                                              charset utf-8;
                                              gzip on;
                                              gzip_types text/css application/javascript text/javascript application/x-javascript image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon;

                                              location / {
                                              try_files $uri $uri/ /index.php?$query_string;
                                              }

                                              location /api/v0 {
                                              try_files $uri $uri/ /api_v0.php?$query_string;
                                              }

                                              location ~ \.php$ {
                                              fastcgi_split_path_info ^(.+\.php)(/.*)$;
                                              set $path_info $fastcgi_path_info;
                                              try_files $fastcgi_script_name =404;
                                              include fastcgi_params;
                                              fastcgi_param SERVER_SOFTWARE "";
                                              fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                                              fastcgi_param PATH_INFO $path_info;
                                              fastcgi_index index.php;
                                              fastcgi_pass unix:/var/run/php-fpm-librenms.sock;
                                              fastcgi_buffers 256 4k;
                                              fastcgi_intercept_errors on;
                                              fastcgi_read_timeout 14400;
                                              }

                                              location ~ /\.(?!well-known).* {
                                              deny all;
                                              }
                                              }

                                              Now start nginx and php-fpm:

                                              service nginx enable
                                              service nginx start

                                              service php_fpm enable
                                              service php_fpm start

                                              LibreNMS configuration

                                              Copy the default config:

                                              cp /usr/local/www/librenms/config.php.default /usr/local/www/librenms/config.php
                                              Because we installed from the package, this file already has the right commands and paths for FreeBSD - no need to hunt down mtr, fping, snmpwalk and friends one by one.

                                              Create the directory for RRD graphs and set ownership:

                                              mkdir -p /var/db/librenms/rrd
                                              chown -R www:www /var/db/librenms
                                              chmod 775 /var/db/librenms/rrd
                                              Then the .env file:

                                              cd /usr/local/www/librenms
                                              cp .env.example .env
                                              chown www .env
                                              Edit .env and set at least:

                                              • DB_DATABASE - librenms
                                              • DB_USERNAME - librenms
                                              • DB_PASSWORD - the one you actually used (not password, please)
                                              Then add this line, which tells LibreNMS we still need to run the web installer:

                                              INSTALL=true
                                              A note on permissions. The official LibreNMS documentation suggests chown -R www:www over the entire application tree, but on FreeBSD the package already lays down sane ownership, with storage/ and bootstrap/cache/ writable by www. There's no reason to widen the rest of the codebase. If validate.php complains later about something write-related, the first place to check is:

                                              ls -la /usr/local/www/librenms/storage /usr/local/www/librenms/bootstrap/cache
                                              Now generate the app key as www, since the file is owned by www:

                                              su -m www -c "php artisan key:generate"
                                              And tighten .env:

                                              chmod 600 .env
                                              Refresh the configuration cache:

                                              su -m www -c "lnms config:clear"
                                              su -m www -c "lnms config:cache"

                                              Web installer

                                              Open http://host/install and follow the steps. The validation process may fail. Refreshing the cache picks up the values written to config.php during the install:

                                              su -m www -c "lnms config:clear"
                                              su -m www -c "lnms config:cache"
                                              When the web installer is done, edit .env again and remove the INSTALL=true line if it's still there. Leaving it in place re-exposes the installer to anyone who can reach the URL.

                                              Polling service

                                              LibreNMS needs something to actually run the polls. On FreeBSD, the package ships an rc service that runs the LibreNMS dispatcher, so there's no need to manage cron entries by hand the way most Linux guides assume.

                                              service librenms enable
                                              service librenms start

                                              Validate

                                              cd /usr/local/www/librenms
                                              su -m www -c './validate.php'
                                              You may see a couple of complaints right after starting the service - usually scheduler-related and self-resolving within a few minutes. Re-run validate.php once the dispatcher has had time to settle. Anything still red after that is worth investigating.

                                              Next steps

                                              At this point you can log into the web interface and start adding devices, configuring SNMP, and building dashboards. For that, the official LibreNMS documentation (https://docs.librenms.org/) is excellent, and there's no point in me paraphrasing it here.

                                              https://it-notes.dragas.net/2026/05/07/monitor-your-services-with-librenms-on-freebsd/


                                                [?]LWN.net » 🌐
                                                @lwn@fedi.lwn.net

                                                [$] LLM-driven security reports disrupt coordinated disclosure

                                                Predictions that LLM tools would cause a surge in reports of security vulnerabilities have, unquestionably, borne out. As expected, maintainers are having to wade through more secu [...]

                                                lwn.net/Articles/1070698/

                                                  [?]LWN.net » 🌐
                                                  @lwn@fedi.lwn.net

                                                  [?]KDE » 🌐
                                                  @kde@floss.social

                                                  Time to get a new wallet? Marco Martin releases KeepSecret 1.1, KDE's new password manager.

                                                  notmart.org/blog/2026/05/keeps

                                                  KeepSecret main windows, showing two wallets labelled "Login" and "kdewallet". Login is highlighted and shows two test entries for website logins.

                                                  Alt...KeepSecret main windows, showing two wallets labelled "Login" and "kdewallet". Login is highlighted and shows two test entries for website logins.

                                                    Back to top - More...