home.social

#webmin — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webmin, aggregated by home.social.

  1. Как наказать цифрового воробья или как я проходил таск PigeonsRevenge от платформы ACLabs.pro

    Данный таск был частью 5 сезона CTF, который проходил на площадке ACLabs. Машина необычная с увлекательным сюжетом и интересными уязвимостями. Условие задачи: Борис — старый почтовый голубь. Катя, его голубка, улетела к наглому Воробью. Три дня Борис пил дешёвое пойло и строчил план мести. Теперь этот план у тебя. Помоги Борису пробраться в цифровое гнездо Воробья, украсть его аккаунт и стать рутом. Следуй за пьяными записками — там всё сказано и даже больше. Внимание, стенд будет полностью готов только по истечении обратного времени отсчета, даже если адрес появился раньше! Цепочка атаки Атакующая цепочка «PigeonsRevenge» комбинирует одну реальную критическую CVE (Webmin 1.910 — CVE-2019-15107, 9.8 CRITICAL) с набором классических техник ATT&CK : активная разведка → port knocking → эксплуатация публичного приложения → Metasploit reverse-shell → туннелирование Ligolo-ng → инъекция через переменную окружения в кастомный бинарник → обход фильтра табуляцией → закрепление с root -привилегиями.

    habr.com/ru/articles/1024360/

    #nmap #bash #docker #ssh #ghidra #cve #webmin #metasploit #privelege_escalation #pivoting

  2. Nice, someone has written an updated #ZFS management module for #Webmin for #FreeBSD which really looks helpful. Its not only offering #ZFS managment, there is also #Samba, #PF #NFS and various other types configuration like #ACL management included, too. Wow!

    With this, #Webmin is nearly feature complete. I'm only missing #Bastille or #Bhyve modules.

    github.com/karmantyu/ZFSgame

  3. Nice, someone has written an updated #ZFS management module for #Webmin for #FreeBSD which really looks helpful. Its not only offering #ZFS managment, there is also #Samba, #PF #NFS and various other types configuration like #ACL management included, too. Wow!

    With this, #Webmin is nearly feature complete. I'm only missing #Bastille or #Bhyve modules.

    github.com/karmantyu/ZFSgame

  4. Nice, someone has written an updated #ZFS management module for #Webmin for #FreeBSD which really looks helpful. Its not only offering #ZFS managment, there is also #Samba, #PF #NFS and various other types configuration like #ACL management included, too. Wow!

    With this, #Webmin is nearly feature complete. I'm only missing #Bastille or #Bhyve modules.

    github.com/karmantyu/ZFSgame

  5. Nice, someone has written an updated #ZFS management module for #Webmin for #FreeBSD which really looks helpful. Its not only offering #ZFS managment, there is also #Samba, #PF #NFS and various other types configuration like #ACL management included, too. Wow!

    With this, #Webmin is nearly feature complete. I'm only missing #Bastille or #Bhyve modules.

    github.com/karmantyu/ZFSgame

  6. Con una recente comunicazione ufficiale, Google ha annunciato la dismissione del fetch POP3 da account esterni in Gmail. Chi utilizzava questa funzione per consolidare più caselle email in Gmail si trova ora a dover migrare verso una soluzione alternativa: l’inoltro automatico (email forwarding) direttamente dal server di posta sorgente.

    Questa guida documenta il processo completo per configurare correttamente l’inoltro da un dominio custom gestito con Postfix e Webmin verso Gmail, risolvendo i problemi di autenticazione SPF/DKIM che causano il blocco con errore 550 5.7.26.

    Il problema: Gmail rifiuta le email inoltrate

    Attivando l’inoltro automatico dal proprio server di posta verso Gmail, si riceve quasi immediatamente un bounce con questo errore:

    text550-5.7.26 Your email has been blocked because the sender is unauthenticated.

    Gmail requires all senders to authenticate with either SPF or DKIM.

    DKIM = did not pass

    SPF [dominio-originale.com] with ip: [IP-del-tuo-server] = did not pass

    La causa è strutturale: quando il server di posta inoltra un messaggio, il mittente nell’envelope (Return-Path) rimane quello originale (es. [email protected]), ma l’IP che effettua la consegna è quello del tuo server. Gmail verifica l’SPF del dominio originale contro l’IP del tuo server — e ovviamente fallisce, perché il tuo server non è autorizzato a inviare per conto di domini terzi.

    […]

    #CPostsrsd #DKIM #DMAR #dns #emailAuthentication #emailForwarding #gmail #linux #postfix #selfHosting #SPF #SRS #webmin https://www.b0sh.net/2026/02/gmail-abbandona-il-pop3-fetch-come-configurare-linoltro-email-con-spf-dkim-e-srs-su-postfix/
  7. Con una recente comunicazione ufficiale, Google ha annunciato la dismissione del fetch POP3 da account esterni in Gmail. Chi utilizzava questa funzione per consolidare più caselle email in Gmail si trova ora a dover migrare verso una soluzione alternativa: l’inoltro automatico (email forwarding) direttamente dal server di posta sorgente.

    Questa guida documenta il processo completo per configurare correttamente l’inoltro da un dominio custom gestito con Postfix e Webmin verso Gmail, risolvendo i problemi di autenticazione SPF/DKIM che causano il blocco con errore 550 5.7.26.

    Il problema: Gmail rifiuta le email inoltrate

    Attivando l’inoltro automatico dal proprio server di posta verso Gmail, si riceve quasi immediatamente un bounce con questo errore:

    text550-5.7.26 Your email has been blocked because the sender is unauthenticated.

    Gmail requires all senders to authenticate with either SPF or DKIM.

    DKIM = did not pass

    SPF [dominio-originale.com] with ip: [IP-del-tuo-server] = did not pass

    La causa è strutturale: quando il server di posta inoltra un messaggio, il mittente nell’envelope (Return-Path) rimane quello originale (es. [email protected]), ma l’IP che effettua la consegna è quello del tuo server. Gmail verifica l’SPF del dominio originale contro l’IP del tuo server — e ovviamente fallisce, perché il tuo server non è autorizzato a inviare per conto di domini terzi.

    […]

    #CPostsrsd #DKIM #DMAR #dns #emailAuthentication #emailForwarding #gmail #linux #postfix #selfHosting #SPF #SRS #webmin https://www.b0sh.net/2026/02/gmail-abbandona-il-pop3-fetch-come-configurare-linoltro-email-con-spf-dkim-e-srs-su-postfix/
  8. Con una recente comunicazione ufficiale, Google ha annunciato la dismissione del fetch POP3 da account esterni in Gmail. Chi utilizzava questa funzione per consolidare più caselle email in Gmail si trova ora a dover migrare verso una soluzione alternativa: l’inoltro automatico (email forwarding) direttamente dal server di posta sorgente.

    Questa guida documenta il processo completo per configurare correttamente l’inoltro da un dominio custom gestito con Postfix e Webmin verso Gmail, risolvendo i problemi di autenticazione SPF/DKIM che causano il blocco con errore 550 5.7.26.

    Il problema: Gmail rifiuta le email inoltrate

    Attivando l’inoltro automatico dal proprio server di posta verso Gmail, si riceve quasi immediatamente un bounce con questo errore:

    text550-5.7.26 Your email has been blocked because the sender is unauthenticated.

    Gmail requires all senders to authenticate with either SPF or DKIM.

    DKIM = did not pass

    SPF [dominio-originale.com] with ip: [IP-del-tuo-server] = did not pass

    La causa è strutturale: quando il server di posta inoltra un messaggio, il mittente nell’envelope (Return-Path) rimane quello originale (es. [email protected]), ma l’IP che effettua la consegna è quello del tuo server. Gmail verifica l’SPF del dominio originale contro l’IP del tuo server — e ovviamente fallisce, perché il tuo server non è autorizzato a inviare per conto di domini terzi.

    […]

    #CPostsrsd #DKIM #DMAR #dns #emailAuthentication #emailForwarding #gmail #linux #postfix #selfHosting #SPF #SRS #webmin https://www.b0sh.net/2026/02/gmail-abbandona-il-pop3-fetch-come-configurare-linoltro-email-con-spf-dkim-e-srs-su-postfix/
  9. Got a bit panic-scared by my website's database going down this morning, with #VirtualMin not clearly telling me that it was due to MariaDB having crashed due to an out-of-memory problem, so I filed this little UX issue: github.com/virtualmin/virtualm

    …and then filed this somewhat more important issue about needing an integrated way to detect and repair crashed #MariaDB / #MySQL tables: github.com/virtualmin/virtualm

    #sysadmin #webmin

  10. #Sysadmin #Linux #Webdev

    Was looking at upgrading and expanding our #CPanel / #WHM off an ancient version of CentOS. Currently supported distro is Ubuntu, ok, I'll spin up the latest LTS release, (released nearly 2 years ago now).

    > "We're sorry, CPanel is only compatible with Ubuntu 20.04"

    .......

    I looked at migrating this box almost 2 years ago, AFTER the release of 22.04, but they did not support the latest LTS back then, with the response of "We'll get it working shortly". 2 years later, STILL NO WORKING CODE!

    WTF is going on over at CPanel? They used to be really good and responsive at implementing new features.

    > "CPanel - a webpros brand"

    Hmm, who is webpros?

    > "Webpros - Cross-platform, multi-functional, omni-channel."

    OH...... they're another worthless investment conglomerate with nothing but marketing fluff and greedy investors. That makes sense why the product has gone to COMPLETE SHIT in recent years.

    OK.... I'll look at #Plesk, they support Linux now, right?

    > "Plesk - a webpros brand"

    FUCK!

    OK...... how 'bout #Webmin and their companion application #Virtualmin ?

    > "Virtualmin - managed by one person and a team of folks, paid commercial versions and support available"

    FUCKING FINALLY! A management product that's not owned by some shady technical grim reaper umbrella corp. Surprise to no one here, the GPL solution has better support and features than the investor-funded solution.

    I liked CPanel as a product, I really did... but they just kept increasing the prices and stopped providing new support. Guess it's finally about time to shift my monthly spend away from them and over to Jamie.

  11. @eingfoan from what I understand, #virtualmin (a #webmin add-on) supports not only webhosting functionality but includes also Mailserver features.

    I only used the webserver part so far, but if it works as good, it should work nicely.

    As it is open source, you can enable/disable any service you do not want.

  12. After successfully editing /etc/network/interfaces directly to fix #webmin + #virtualmin being confused by #systemd assigning a different unique network device ID after transplanting the #Linux server's SSD to another machine…

    Virtualmin: "Who are you?!"

    Me, as #sysadmin: "my name… is Barbarianna." 🦝 youtube.com/watch?v=AGdPlO_GYt