Remix.run Logo
▲ benoau 2 hours ago

> Even if it's a token that was copied and pasted temporarily, the systems in place should not have to require this type of 1. copy 2. paste 3. remember-to-delete the token from my PC.

One of the first things I did in my last job was shift processes like this off my team's computers, aside from the security ramifications all it takes is one dumb mistake, one up-arrow too many, one didn't-read-the-whole-line, and now you're doing something to production by accident!

▲hirako2000 an hour ago | parent | next [-]

I also did that, for a team deploying smart contract on chain from local.

It took a couple months to get the pipeline out of their laptop.

Worth it, yes, as we found interesting things in there which explained why they were so reluctant to deploy upgrades.

▲pjc50 an hour ago | parent [-]

> as we found interesting things in there which explained why they were so reluctant to deploy upgrades

.. backdoors which enabled the dev to deploy exploits of their own which wouldn't be visible through CI?

▲jacekm 33 minutes ago | parent | prev [-]

TBH CI does not prevent this kind of mistakes. I've seen people triggering the wrong CI pipeline.

▲steve1977 3 minutes ago | parent [-]

I guess people triggering the pipeline is already part of the problem