|
|
|
|
|
by lokopodium
2700 days ago
|
|
Australia requires companies to provide backdoors. It does not (and can't) require that non-companies do the same. This means every Jihadi with half a brain will be using XMPP with OTR or something like that. At the same time, it provides a requirement for EMPLOYEES to make backdoors when asked without letting their employers know. |
|
I'm very curious about how this will actually work, in practice, anywhere that uses any form of source control and even a modicum of process.
I mean, do you sneak this into an unrelated pull request and hope everyone reviewing it doesn't catch it? Do these changes by committing directly to master (assuming you even can do that), and just hope no one notices? What commit message do you use?
Even if you don't put this in source control, how do you get it deployed? Do you just tell your ops team "uh, don't use the automated deployment or the artifacts the build server produced, instead install from this zip file I made on my machine"? What happens if they are deploying a new version on a day you happen to not be there?
Even assuming you manage to do all this, what happens when you're eventually caught? For example, someone finds a remote exploit bug in the code, does a blame, sees your name next to an innocent-sounding-but-clearly-misleading commit message and injection of an apparent deliberate exploit... are you allowed to explain? I would assume, especially if you can't/won't explain, that the employer could fire you on the spot, so do you just have to go along with that?