Hi Greg, Do we have a service for windows certifications? I remember some service with Symantec. I'd that works with MSN can you give pointers?
Thx for the support! All the best Peter Am 29. Oktober 2019 11:13:53 MEZ schrieb Pedro Lino <pedro.l...@mailbox.org>: >Hi all > >> On October 28, 2019 at 10:32 PM Dave Fisher <wave4d...@comcast.net> >wrote: >> >> There is an offer from Microsoft for Apache committers to get a free >MSDN license. If that gives access to the proper signing keys then that >would be the way to go. > >Is it possible for one of the PMC members to find out if there are >exceptions for non-profit organizations such as Apache? > >Warning: I'm not a developer so maybe some interpretations could be >wrong > >As far as I can investigate in MSDN blogs, all developers buy their >certificates from various providers (Comodo, Symantec, Thawte, etc) and >Microsoft only certifies it's own binaries (which to me is a bit >suspicious but they do own the game :) ) > >https://blogs.msdn.microsoft.com/ieinternals/2011/03/22/everything-you-need-to-know-about-authenticode-code-signing/ >https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate >https://aboutssl.org/cheap-code-signing-certificate-providers/ > >Developers can create their local certificates but only for testing > >https://docs.microsoft.com/en-us/windows/win32/appxpkg/how-to-create-a-package-signing-certificate > >Hope this helps, >Pedro > >> > On Oct 28, 2019, at 3:22 PM, Peter Kovacs <pe...@apache.org> wrote: >> > >> > I do not want to spend money on this service, without having tried >with infra or Microsoft directly. >> > I am sure the ASF has something. And if not I am sure Microsoft >gives us access at better conditions then the 3rd party offer. >> > >> > Am 28. Oktober 2019 20:59:15 MEZ schrieb Pedro Lino ><pedro.l...@mailbox.org>: >> >> Hi Peter >> >> >> >> >> >>> For Windows it would help in a first step if someone can >search >> >> the resources on MSN and post links of the validation process >described >> >> by MS. >> >>> >> >> >> >> This is what is needed for Windows Certification: a Code Signing >> >> Certificate >> >> https://www.ksoftware.net/code-signing-certificates >> >> >> >> Giving that this is a distributed project, I would say that the OV >Code >> >> Signing is the most appropriate (otherwise only one person will >have >> >> the encrypted hardware token) >> >> >> >> Hope this helps. >> >> >> >> Does Apache OpenOffice have any funds? >> >> >> >> Regards, >> >> Pedro >> >> >> >> >> >>> Am 28. Oktober 2019 17:45:35 MEZ schrieb Matthias Seidel < >> >> matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de >: >> >>>> Hi Pedro, >> >>>> >> >>>>> Am 28.10.19 um 17:40 schrieb Pedro Lino: >> >>>>>>>>> >> >>>>>>>>> Do you volunteer? Remember, we all are only volunteers... >> >>>>> ;-) >> >>>>>>>>> I believe these two issues should be enough >> >>>>> reason for a 4.1.8 release. >> >>>>>>>>> Welcome to the team! >> >>>>>> I don't understand the cynicism. >> >>>>>> I believe I have contributed quite a bit with translation, bug >> >>>>> reporting and build testing. Apparently that is not enough for >> >>> this >> >>>>> project? >> >>>>>> >> >>>>>> Too bad! >> >>>>> >> >>>>> Well, someone has to deliver... >> >>>>> >> >>>>> No cynicism, it was just an invitation. >> >>>>> >> >>>>>> >> >>>>>> Regards, >> >>>>>> Pedro >> >>>>>> >> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org
