-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nodeinfo exposes WordPress version? #11
Comments
This is the NodeInfo plugin repo but it seems that you use the ActivityPub endpoint, is that true? You can use a filter, to remove the Informations about WordPress, but maybe it is a better choice to remove the endpoint completely (???), because I am not sure if FediDB indexes sites that have no software identified. |
Okay. Thanks. Yes, I know this is the
Odd, but it is what it is. Thanks! |
I think this is still a relevant feature, because we could at least mask the version number and have a possibility to disable it completely. |
I at least masked the version number to show only the major version. |
I know that security through obscurity is a weak defense, if any. However, I like to remove all the version identifiers from the software that I expose to the public. The less an attacker knows about the infrastructure, the better.
Is there a way to remove the version identifiers from
nodeinfo
(and likely your other plugins)? I don't even truly mind that it still says WordPress.For instance, the ActivityPub endpoint
/wp-json/activitypub/1.0/nodeinfo2
exposessoftware
andversion
for WordPress. Additionallynodeinfo
provides a generator with information about the software and version in question via/wp-json/nodeinfo/2.1
.Perhaps I'm able to see this because I'm logged in?
The text was updated successfully, but these errors were encountered: