News for hackers. Stuff that matters.
Re:How Dark Deploys Code in 50ms by kccqzy on Thursday July 11, 2019 @06:59AM (#20410604)
Twenty years ago, deployment of a new version of a web app means FTP'ing a new php file to the server.
Re:How Dark Deploys Code in 50ms by pikzel on Thursday July 11, 2019 @07:22AM (#20410691)
Which wasn't a bad thing after all. I've had more incidents with deployment pipelines than with the actual code.
Re:How Dark Deploys Code in 50ms by dharmab on Thursday July 11, 2019 @09:16AM (#20411252)
Mostly because people forget that pipelines are code and need documentation, tests and software engineering practices just like any code.
Re:How Dark Deploys Code in 50ms by eloisant on Thursday July 11, 2019 @07:20AM (#20410682)
Well, you're free to deploy like this (but you probably know why it's a very bad idea).
Re:How Dark Deploys Code in 50ms by somehnguy on Thursday July 11, 2019 @09:12AM (#20411224)
Feel free to explain why
Re:How Dark Deploys Code in 50ms by adrianN on Thursday July 11, 2019 @09:52AM (#20411487)
Auditing what was changed and which version is currently in production is a bit harder than it has to be.
Re:How Dark Deploys Code in 50ms by viraptor on Thursday July 11, 2019 @05:11PM (#20415891)
Copying of multiple files is not atomic. You need to ensure a file with func1 exists before another file calling func1 gets copied. You can do it atomically by having 2 directories and swapping a symlink, but... that's a scriptable pipeline at that point.
Re:How Dark Deploys Code in 50ms by stabbles on Thursday July 11, 2019 @11:38AM (#20412372)
Yet another reason is FTP turned out to be inherently unsafe.
Re:How Dark Deploys Code in 50ms by jszymborski on Thursday July 11, 2019 @12:30PM (#20412912)
SFTP, however, has FTP feature parity and is secure as SSH (since it is ostensibly SSH).