Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use OpenTimestamps for Git commits #2847

Open
andrewdavidwong opened this issue Jun 4, 2017 · 4 comments
Open

Use OpenTimestamps for Git commits #2847

andrewdavidwong opened this issue Jun 4, 2017 · 4 comments
Labels
C: infrastructure P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@andrewdavidwong
Copy link
Member

At a minimum, in qubes-secpack, and eventually in most repos.

Discussion:
https://groups.google.com/d/topic/qubes-devel/b0s6ZA8fmQQ/discussion

CC @petertodd
@andrewdavidwong andrewdavidwong added C: other T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. T: task Type: task. An action item that is neither a bug nor an enhancement. labels Jun 4, 2017
@andrewdavidwong andrewdavidwong added this to the Far in the future milestone Jun 4, 2017
@petertodd
Copy link

+1

One issue that @rootkovska raised awhile back was that the easiest install process for OpenTimestamps is to install dependencies via Python's insecure pip packaging system; we should discuss further what needs to be done to securely package OpenTimestamps for use in the QubesOS development environment.

@petertodd
Copy link

Also, re: actually timestamping Git repos, this is the relevant blog post describing how that works: https://petertodd.org/2016/opentimestamps-git-integration

@andrewdavidwong
Copy link
Member Author

Another discussion thread:
https://groups.google.com/d/topic/qubes-devel/ilxC6UpkZz4/discussion

@marmarek
Copy link
Member

marmarek commented Feb 4, 2019

There is a hope: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921251

@andrewdavidwong andrewdavidwong added C: infrastructure P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. and removed C: other T: task Type: task. An action item that is neither a bug nor an enhancement. labels Feb 5, 2022
@andrewdavidwong andrewdavidwong modified the milestones: Release TBD, Non-release Feb 5, 2022
@andrewdavidwong andrewdavidwong removed this from the Non-release milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: infrastructure P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@petertodd @marmarek @andrewdavidwong