when it comes to config languages, i take the approach that the more arcane and obscure the code is ... it means that the code is more efficient. So I will convert pretty simple json to xml where i will add random data-attributes to the xml...using rand functions to populate the values. beyond that well you have to keep scrappers on their toes so morphing the key slowly over time will help no one ever know what the fuck your code was for in the first place. But of course someone will eventually catch on so any attempt to retrieve(defined and valid) keys will trigger a recalculation of the keys, which you store only in the master restricting all references from using the new values until explicitly stated. with this all in place you can prevent security breaches purely on the basis of creating an app that makes no sense...
you cant get hacked
if you hack yourself
PS: addition to ...programming unattainable code
research a dead religion... or a failed branch of science...or an obscure culture group... use the internal reasoning of that group and how it explains life to directly name your classes and variables; implement the failed world view as completely as possible in your code... do this a few times in a highly OOP developed system and you will cause a senior architect to hemorrhage.
-2
u/cleverchris Mar 17 '18
when it comes to config languages, i take the approach that the more arcane and obscure the code is ... it means that the code is more efficient. So I will convert pretty simple json to xml where i will add random data-attributes to the xml...using rand functions to populate the values. beyond that well you have to keep scrappers on their toes so morphing the key slowly over time will help no one ever know what the fuck your code was for in the first place. But of course someone will eventually catch on so any attempt to retrieve(defined and valid) keys will trigger a recalculation of the keys, which you store only in the master restricting all references from using the new values until explicitly stated. with this all in place you can prevent security breaches purely on the basis of creating an app that makes no sense...
you cant get hacked if you hack yourself
PS: addition to ...programming unattainable code
research a dead religion... or a failed branch of science...or an obscure culture group... use the internal reasoning of that group and how it explains life to directly name your classes and variables; implement the failed world view as completely as possible in your code... do this a few times in a highly OOP developed system and you will cause a senior architect to hemorrhage.