grant-olson rubygems-openpgp issues

grant-olson / rubygems-openpgp

This allows you to cryptographically sign ruby gems, so that a user can later verify that they've downloaded a copy that hasn't been tampered with or hacked.

http://www.rubygems-openpgp-ca.org

Other

32 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

--get-key should be implicit

#35 grant-olson opened 10 years ago
0
Website inaccessible in Chrome, ssl cert mismatch

#34 bf4 closed 10 years ago
9
gem verify throws an error if your gem has never been on rubygems.org

#33 grant-olson opened 11 years ago
0
Stub out homedir lookup in test so we don't need to pass it around

#32 grant-olson opened 11 years ago
0
Can't dual-sign gems

#31 grant-olson opened 11 years ago
2
Error when installing a gem that's not on rubygems

#30 grant-olson opened 11 years ago
0
--trust should imply --verify

#29 grant-olson closed 11 years ago
0
Query rubygems owner info?

#28 grant-olson closed 11 years ago
1
linux users should be able to use gpg2 if they want

#27 grant-olson opened 11 years ago
1
Broken application link on website

#26 FooBarWidget closed 11 years ago
1
We show 9 characters in short-id instead of 8.

#25 grant-olson closed 11 years ago
0
`gem verify foo-0.0.0.gem --trust` doesn't work

#24 grant-olson closed 11 years ago
0
Don't ask passwords twice and allow specifying custom GPG options

#23 FooBarWidget opened 11 years ago
6
Show full path of known_gems, ~ doesn't make sense on windows.

#22 grant-olson closed 11 years ago
0
Don't add color codes on windows

#21 grant-olson closed 11 years ago
0
We shouldn't sign X509 sigs, only the real payload

#20 grant-olson closed 11 years ago
0
move run_gpg code to gpg_status_parser

#19 grant-olson closed 11 years ago
0
Show gem name before signature status

#18 grant-olson closed 11 years ago
0
Friendly error message when you don't have a key

#17 grant-olson closed 11 years ago
1
Provide gem commands to automate generating and uploading developer keys

#16 postmodern opened 11 years ago
1
Track keys used to sign gems

#15 grant-olson closed 11 years ago
0
Add --no-verify option

#14 Quintus closed 11 years ago
3
Use gpg's --status-fd or --status-file to verify

#13 grant-olson closed 11 years ago
3
Something should happen with an INSECURE UNTRUSTED key

#12 grant-olson closed 11 years ago
1
Consider storing pubkeys in ~/.gem/keyring

#11 postmodern closed 11 years ago
4
Replace 'gem sign' and 'gem sbuild' with 'gem build --sign'

#10 grant-olson closed 11 years ago
1
Replace 'gem verify' and 'gem vinstall' with 'gem install --verify'

#9 grant-olson closed 11 years ago
1
Use shellescape when embedding data into commands.

#8 postmodern closed 11 years ago
3
Automatic Gem Verification

#7 yorickpeterse closed 11 years ago
11
Support automatic verification

#6 postmodern closed 11 years ago
9
Keyring consideration

#5 zph closed 11 years ago
3
Windows can build,sign, verify and install gems, but rubygems.org barfs when you try to upload

#4 grant-olson closed 11 years ago
1
Signed windows gem doesn't install

#3 grant-olson closed 13 years ago
1
Permissions issues prevent tests from running on windows

#2 grant-olson closed 13 years ago
1
Verification of openpgp_signed_hola gem fails on windows

#1 grant-olson closed 13 years ago
2