Debugpaste: needs to be entirely transparent to end user. #24

New issue

Closed

opened 2018-10-17 00:46:00 +02:00 by Leopere · 1 comment

Leopere commented

2018-10-17 00:46:00 +02:00

(Migrated from github.com)

I was thinking that perhaps I could automate the entire debugpaste compile process on a fully transparent GitLab CI/CD build process with static hashes so that people can monitor the supply-chain.

As brought up by @BrannonKing in a slack DM we don't want to introduce a vector for virus injection. So what we're going to do is potentially have our own fork of debugpaste for lbry or consider other options not currently in this issue. I was thinking that perhaps I could automate the entire debugpaste compile process on a fully transparent GitLab CI/CD build process with static hashes so that people can monitor the supply-chain.

Leopere commented

2019-04-26 01:13:24 +02:00

(Migrated from github.com)

Abandoning this for now.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-docker#24

No description provided.