You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
Currently, github has neither private / hidden issues (#37) nor private / hidden attachments on public issues.
Age is a very simple and opinionated encryption tool, which as a bonus works extremely well with github: age -R <(curl -o- https://github.com/<username>.keys) < infile > outfile will encrypt "infile" using the user's github public keys (-R can be repeated for multiple recipients), allowing them to use their private github key to decrypt the file and giving nobody else access.
This means it works rather well as a way to upload attachments visible only to maintainers. Or would if age files were supported, as-is they have to be smuggled as the "cleartext" file (stripping out the .age extension), possibly confusing people.
The text was updated successfully, but these errors were encountered:
GitHub staff are eager to continue in conversations and knowledge-sharing with you. We invite you to head over to Feedback Discussions and share your product feedback and questions directly with us (noted here). Once you have added your thoughts in Feedback Discussions, we ask that you close this newly-created issue. Otherwise, we will keep this issue open for the next 7 days, then will close it.
@Levi-Lesches not exactly, I'm using encrypted attachments as a work-around-ish for #37 (hence having linked to it in the description) but private attachments on public issues is useful regardless, and so is encrypted attachments in general.
Currently, github has neither private / hidden issues (#37) nor private / hidden attachments on public issues.
Age is a very simple and opinionated encryption tool, which as a bonus works extremely well with github:
age -R <(curl -o- https://github.com/<username>.keys) < infile > outfile
will encrypt "infile" using the user's github public keys (-R
can be repeated for multiple recipients), allowing them to use their private github key to decrypt the file and giving nobody else access.This means it works rather well as a way to upload attachments visible only to maintainers. Or would if age files were supported, as-is they have to be smuggled as the "cleartext" file (stripping out the
.age
extension), possibly confusing people.The text was updated successfully, but these errors were encountered: