Marcin
My feedback
-
1 voteMarcin
shared this idea
·
-
125 votesMarcin
supported this idea
·
-
137 votesMarcin
supported this idea
·
-
1 voteMarcin
shared this idea
·
-
82 votes
An error occurred while saving the comment Marcin
shared this idea
·
-
30 votes0 comments · Service Improvement » Server Configuration Improvements · Flag idea as inappropriate… · Admin →Marcin
supported this idea
·
-
49 votesMarcin
supported this idea
·
-
114 votesMarcin
supported this idea
·
-
161 votesMarcin
supported this idea
·
-
140 votesMarcin
supported this idea
·
-
303 votesMarcin
supported this idea
·
-
35 votes
-
5 votes
-
261 votes63 comments · Service Improvement » Server Configuration Improvements · Flag idea as inappropriate… · Admin →
-
38 votes
-
13 votes
-
111 votesMarcin
supported this idea
·
-
7 votes
-
12 votes
-
33 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.