Marcin
My feedback
-
1 voteMarcin
shared this idea
·
-
107 votesMarcin
supported this idea
·
-
112 votesMarcin
supported this idea
·
-
1 voteMarcin
shared this idea
·
-
66 votes
An error occurred while saving the comment Marcin
shared this idea
·
-
26 votes0 comments · Service Improvement » Server Configuration Improvements · Flag idea as inappropriate… · Admin →Marcin
supported this idea
·
-
40 votesMarcin
supported this idea
·
-
32 votesMarcin
supported this idea
·
-
80 votesMarcin
supported this idea
·
-
135 votesMarcin
supported this idea
·
-
121 votesMarcin
supported this idea
·
-
252 votesMarcin
supported this idea
·
-
26 votes
-
5 votes
-
141 votes
-
23 votes
-
12 votes
-
83 votesMarcin
supported this idea
·
-
7 votes
-
18 votesMarcin
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.