No. We were in constant contact with various folks from core, foundation and clusteradmin. So, none of this nonsense please.Meanwhile where is Foundation ? Hey , did something happened ?
Not that I could find in our situation. I took apart their injected javascript. It didn't do much besides redirecting to a github repo that hosted the "defacement" page. That defacement page also contained some javascript, but that was nothing more than a basic http/tcp/udp connection flooder. Nothing fancy and most of it didn't even work properly.I wonder if the XSS hack was combined with other methods to do more damage.
There was a Foundation post on Facebook. Showing they knew nothing. Excuse me if I sometimes over-exagerate. I only tell my feelings. And really have no idea, the good/bad they do. So for me it is something "black".No. We were in constant contact with various folks from core, foundation and clusteradmin. So, none of this nonsense please.
They managed to center the div vertically. That's impressive enoughI took a screenshot with my cell phone.
View attachment 25824
These idiots don't even know what responsiveness is.
That was funny.They managed to center the div vertically.
i guess that my proxy blocked the bg image. i simply saw a black bg.I took a screenshot with my cell phone.
View attachment 25824
These idiots don't even know what responsiveness is.
@media (max-width: 300px) {
.haha { display: block; }
}
This is literally what happened.This is about the corresponding hack on linux.org from this thread.
"Edit2: more info: https://github.com/methosiea/xenforo-2-xss
So, the attack chain is basically:
I wonder if the XSS hack was combined with other methods to do more damage.
- Attacker registers an account
- New post w/ the xss payload - it goes to the queue
- An admin views it, it fires off the xss payload stealing his session
- Attacker creates the malicious widget"
I also wonder why someone would hack a public forum.
/grandpa
Exactly. Us open source heads always brag about how both linux and freebsd are super secure, and then we have our forums pwnd like this. Its pretty embarrassing.The hack also took down linux.org's forum so I guess it's not a good look for Linux forums, too, eh?
The security of the OS isn't going to stop a parsing bug in a web application. That's how most, if not all, hacks happen nowadays. It very rarely happens because of a bug in the OS itself.how both linux and freebsd are super secure
XenForo is not open source. also, XenForo is not Linux or FreeBSD, it's a piece of third-party software.Exactly. Us open source heads always brag about how both linux and freebsd are super secure, and then we have our forums pwnd like this. Its pretty embarrassing.
Yeah, having a good, workable plan on how to get back up and running reasonably quickly after an incident IS one important aspect of administering a public service. Another important aspect is being able to communicate solid info about the status of the said service. But sometimes, it's faster to fix the situation than to fully analyze what happened and write an announcement. Besides, when a situation is solved, analysis stops being that incredibly urgent. Basically, it takes some level-headed thinking to realize that the priority should be on technically rectifying the problematic situation, rather than analysis and announcements. Especially given the fact that the Forums are basically aThis was quickly solved. When recently someone, updated package database with a bad package, inserting some bad sql into db, I think it took at least 18hours before fix. Nobody could download any package , not on quarterly ,not on "current".
For other architectures it took 3 days.
Here it is much about nothing.
& About this bad package sql. Not one word from foundation. Not one.
View attachment 25826
communication platform with no real alternative method of reaching the users. Kind of like having roads washed out by a flash flood - nothing happens until the road is fixed, and fast, and full analysis of the economic and social impact of that flood can wait.If you're referring to this (the recurrence), then you're wrong.This was quickly solved. When recently someone, updated package database with a bad package, inserting some bad sql into db, I think it took at least 18hours before fix. Nobody could download any package , not on quarterly ,not on "current".
For other architectures it took 3 days.
Here it is much about nothing.
$ doas pkg update
Updating FreeBSD-ports repository catalogue...
Fetching data.pkg: 100% 10 MiB 1.1MB/s 00:10
Processing entries: 99%
pkg: sqlite error while executing grmbl in file update.c:154: NOT NULL constraint failed: packages.path
pkg: sqlite error while executing grmbl in file update.c:154: NOT NULL constraint failed: packages.path
pkg: sqlite error while executing INSERT OR REPLACE INTO packages (origin, name, version, comment, desc, arch, maintainer, www, prefix, pkgsize, flatsize, licenselogic, cksum, path...

That's strange because the cad/cura-engine port has last been updated on
2025-11-05 so if its only a change to that port the logic bomb should've blown up
in all our faces weeks ago.
No need to lecture me about that. You are completely missing the point. The fact that it happened is what makes us all look bad. I mentioned both linux and freebsd in my posts, but im fully aware that it has nothing to do with either. Its a human factor as stated below.XenForo is not open source. also, XenForo is not Linux or FreeBSD, it's a piece of third-party software.
and anyone claiming that any OS is "super secure" is... possibly misunderstanding how security works. perhaps you could say FreeBSD is "more secure" than, say, AIX, in the sense that it has fewer security advisories (i don't know of any statistics about this off hand, so let's just stipulate that it's true), but that doesn't mean FreeBSD "is super secure". if you don't apply security updates, it's not secure. if you run EOL releases, it's not secure. if you don't attend to physical security, it's not secure. if you run an Internet-accessible sshd with weak passwords, it's not secure.
security is far more about process than it is about choice of software.
It would be perfectly understandable if this was an agricultural or cooking forum that was run by bunch of incompetent Kares. But its not.It happens, and i understand. But you cant deny the fact that it looks bad.We had a failure in keeping up with XF and that will not happen again.
Its because you are taking what im saying literally.I am confused as to how the Linux Operating System, the FreeBSD Foundation and the FreeBSD Operating system are being accused of being insecure because of a vulnerability in forum software
Note i entered bug report, after 90minutes of outage , problem was fixed only one hour later, ok needed some reminder. That was very quick/Yeah, having a good, workable plan on how to get back up and running reasonably quickly after an incident IS one important aspect of administering a public service. Another important aspect is being able to communicate solid info about the status of the said service. But sometimes, it's faster to fix the situation than to fully analyze what happened and write an announcement. Besides, when a situation is solved, analysis stops being that incredibly urgent. Basically, it takes some level-headed thinking to realize that the priority should be on technically rectifying the problematic situation, rather than analysis and announcements. Especially given the fact that the Forums are basically acommunication platformwith no real alternative method of reaching the users. Kind of like having roads washed out by a flash flood - nothing happens until the road is fixed, and fast, and full analysis of the economic and social impact of that flood can wait.