Kristian Van Der Vliet
Kristian Van Der Vliet
The obvious (?) solution is to use some other data beyond the organization name & job ID. Perhaps ``` ruby Digest::SHA256.hexdigest "#{job_name}:#{job_version}:#{started}:#{salt}" ``` That would then require an attacker to...
For organization secrets, the sensible solution would be to add a 'secrets' section to the job, with a series of named encrypted values in it. E.g. ``` json "secrets": {...
Work started on the [feature/issue12](https://github.com/Liqwyd/Cyclid/tree/feature/issue12) branch
...and implemented. At least for secrets. Logs are a different problem.