Why CMS are not fully secured?
bunkerify.com
Why CMS are not fully secured?
1–8 of 8 posts
Re: Why CMS are not fully secured?
#2> We, at Bunkerify, have developped, thanks to our experience in IT security, algorithms to hide your secrets without modifying the behaviour and the ease of use of all these CMS.
> Our algorithms do deep obfuscation of the sensible content of configuration files, that make it unreadable by a human. A pirate have to make a very long work of reverse engineering to understand what we done, and then, try to counter it.
> Bunkerify uses deep security algorithms
Who upvotes this garbage?
Re: Why CMS are not fully secured?
#3> We, at Bunkerify, have developped, thanks to our experience in IT security, algorithms to hide your secrets without modifying the behaviour and the ease of use of all these CMS. > Our algorithms do deep obfuscation of the sensible content of configuration files, that make it unreadable by a human. A pirate have to make a very long work of reverse engineering to understand what we done, and then, try to counter it.…
>> The software used a malware technique used by the NSA to restart crashed services.
> Your click bait headline is bad and you should feel bad.
Haters gonna hate
Re: Why CMS are not fully secured?
#4I don't think that config file (or even script code) obfuscation is a sensible way of hardening a system. If the database access credentials are really the weak point of a system (I don't think so), the database authentication itself should be replaced by something more sophisticated, such as public/private keys, host based authentication, etc.
Re: Why CMS are not fully secured?
#5> We, at Bunkerify, have developped, thanks to our experience in IT security, algorithms to hide your secrets without modifying the behaviour and the ease of use of all these CMS. > Our algorithms do deep obfuscation of the sensible content of configuration files, that make it unreadable by a human. A pirate have to make a very long work of reverse engineering to understand what we done, and then, try to counter it.…
>> The software used a malware technique used by the NSA to restart crashed services. > Your click bait headline is bad and you should feel bad. Haters gonna hate
HN isn't a promotion platform for snake oil and click bait, so please refrain from misusing it as such.
Re: Why CMS are not fully secured?
#6I don't think that config file (or even script code) obfuscation is a sensible way of hardening a system. If the database access credentials are really the weak point of a system (I don't think so), the database authentication itself should be replaced by something more sophisticated, such as public/private keys, host based authentication, etc.
The main goal of pirates is to access the database configuration quickly. By hardening it, pirates will move on.
Wordpress, Drupal, Prestashop and Joomla have the same problem
Re: Why CMS are not fully secured?
#7Earlier quoted context omitted.
>> The software used a malware technique used by the NSA to restart crashed services. > Your click bait headline is bad and you should feel bad. Haters gonna hate
HN isn't a promotion platform for snake oil and click bait, so please refrain from misusing it as such.
thank you for bringing the absolute truth about what should be or not on HN
Re: Why CMS are not fully secured?
#8> We, at Bunkerify, have developped, thanks to our experience in IT security, algorithms to hide your secrets without modifying the behaviour and the ease of use of all these CMS. > Our algorithms do deep obfuscation of the sensible content of configuration files, that make it unreadable by a human. A pirate have to make a very long work of reverse engineering to understand what we done, and then, try to counter it.…
> Who upvotes this garbage?
Barely anyone, it seems. The content may not be great, but there's no need to be mean. It could be someone just trying out blogging for the first time. It also might be that English isn't their primary language.
We can just flag stuff like this and move on.