Replies: 3 comments 4 replies
|
Thanks for the issue @tpg-tahc as far as I know, my only option for fixing this would be to register an IV (individual verification) certificate and sign the code with that. Then downside is the code would say “Published by Jeremy Fowers” or similar, which wouldn’t properly credit the great community that works on this code. What do people think @Geramy @ramkrishna2910 @bitgamma @vgodsoe @danielholanda @sofiageo ? status quo or IV route? |
0 replies
|
for me the IV option sounds reasonable. However with a quick googling I found this: https://shop.certum.eu/open-source-code-signing-code.html not 100% sure if they are reliable or not, but could be what we need? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This is not a big issue, or maybe not a technical issue at all, but if we want to have more people to try out lemonade and improve their first impression, we should fix this.
All reactions