New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
So, demon live inside you. 😈 How about my question? Can we agree that you will start using shell without "demonizing" it? :P
Oh yes ! I agree I will not demonize shellter's systems again. I will do it only locally, on my servers, wearing a daemon mask.
Welcome back to the shellter, hope you will not wake me up any time soon :P Enjoy
@elusiVeRPG — why is weechat not connecting to any IRC network and getting connection refused?
It stays in motd. (but ip from Yours motd or vh command)
IRC outbound is IPv6-only — bind to one of your 3 addresses:
irssi -h 2a03:94e0:257e:1::1 erssi -h 2a03:94e0:257e:1::1
or inside the client: /set hostname 2a03:94e0:257e:1::1
(default unbound clients leak the host primary v6 and get dropped by pf)
So in weechat
/set irc.server_default.bind_address <IP/hostname>
Have a good chat!
Maybe you could create a script so when the user is created, the IP gets allocated automatically in some custom generated configs. Just a thought, I don't know if this is possible or if it takes lots of work.
Is totally possible and I was thinking about it yesterday also but then my adhd chose to change my goal and first I want to roll out something else and forgot about it
. Maybe tomorrow will be the day to get it done. 
still down!
anyway, i am in now on shellter... and now?
Just to let you know.
We have security incydent!
We mitigated another probe of abuse on our server. The user tried to take full control of our panel and copy it through SCP to his own server. We caught him in the middle of a job. His account was suspended, All logs collected. We rotate all credentials used in the frontend and backend. No user data was leaked from Supabase. The user didn't have enough time to use any of the data he got from us.
It's a little sad for him he loses his account :P as we plan to clean a little bit the codebase for our pubnix backend and fronted and make it open source some time soon. 🔜
We are preparing some updates for users also.
Stay tuned as soon as you will be able to use shelter also for your personal small website. 
Sorry no time as abusers keep me busy :P Truly speaking, I forgot about it. I hope I will fix it tomorrow, as today I am exhausted.
That's a very creative way to say "We got pwned, source code and credentials leaked"
Not really... is a normal transparent way. And credential was useless... And tell why your username is almost same as te shitty abuser? :> Should I email you the whole source code? :>
Really? That's getting interesting. Especially when FreeBSD is involved. Should I get popcorn? I wonder who I might offend here to make it look that way.
Dunno, nb> @luckypenguin said:
Dunno, bro but the "lucky" happy digger was cut with pants down. :> My bad as when I do chmod for shellter users I left my own with 755
to much stuff at once and obvious mistakes are real. Fixed for now 
Happy to welcome another pen tester! You all make your shellter more safe! 
At least there are no shitty LKM drivers loaded into the kernel by default. 7 local roots from unprivileged user in 1 month, poor penguin.
But it was not so bad I think? Those 755 was a my obvious mistake I just was so excited with the project that I forgot to check own backyard
.
I try to learn and improve every day.
I don't know? But anyway upgrade to 15.0-RELEASE-p9 if you haven't yet.
This looks serious enough, and quite trivial to exploit:
https://www.freebsd.org/security/advisories/FreeBSD-SA-26:22.libcasper.asc
Thanks !
It was rebooted with this update at May 26 but thanks for the memo
So 20+ years later you sit around auditing some autogenerated source. That's progress i guess.