Marcin
My feedback
17 results found
-
1 vote
Marcin
shared this idea
·
-
1 vote
Marcin
shared this idea
·
-
93 votes
An error occurred while saving the comment
Marcin
shared this idea
·
-
34 votes
Marcin
supported this idea
·
-
187 votes
Marcin
supported this idea
·
-
150 votes
Marcin
supported this idea
·
-
340 votes
Marcin
supported this idea
·
-
411 votesunder review · 108 comments · Product Improvements: Flexible » Server Configuration Improvements · Admin →
-
48 votes
-
136 votes
Marcin
supported this idea
·
-
8 votes
-
13 votes
-
35 votes
Marcin
supported this idea
·
-
19 votes
Marcin
supported this idea
·
-
23 votes
Marcin
supported this idea
·
-
209 votes
Marcin
supported this idea
·
-
88 votes
Marcin
supported this idea
·
Ron, I have read most of the articles you shared.
The main point that I see of the article is that changing the database prefix doesn't improve the security as there is a way for hackers to identify the changed database prefix, and changing it on a live site might cause issues.
However, if the hacker or a bot does not know the way to detect the new database prefix, changing it improves makes it more work for them to hack your site.
The idea is to auto-generating a random WordPress database prefix when the new application is created so that people do not need to try to change it on a live site.
In my opinion, there is still a benefit to changing the database prefix.