Re: [Signing] New component for code signing

> On Feb 1, 2018, at 5:28 PM, Mark Thomas wrote: > >> On 01/02/18 22:08, Emmanuel Bourg wrote: >>> Le 23/01/2018 à 07:33, Mark Thomas a écrit : >>> >>> Thoughts? Comments? >> >> +1 +1 >> >> I might even be able to contribute some elements I developed for my >> jsign

Re: [Signing] New component for code signing

On 01/02/18 22:08, Emmanuel Bourg wrote: > Le 23/01/2018 à 07:33, Mark Thomas a écrit : > >> Thoughts? Comments? > > +1 > > I might even be able to contribute some elements I developed for my > jsign project [1]. jsign is able to sign Windows executables but using a > local signing certificate

Re: [Signing] New component for code signing

Le 23/01/2018 à 07:33, Mark Thomas a écrit : > Thoughts? Comments? +1 I might even be able to contribute some elements I developed for my jsign project [1]. jsign is able to sign Windows executables but using a local signing certificate or a PKCS#11 token. It comes with an Ant task, a Maven

Re: [Signing] New component for code signing

. There can be of course plans for server-side code signing components. Thanks, Robert > > Gruss > Bernd > > Von: Robert Munteanu > Gesendet: Dienstag, 30. Januar 2018 11:21 > An: Commons Developers List > Betreff: Re: [Signing] New component for code signing > >

RE: [Signing] New component for code signing

Well, there are plans by me. I would not invest time in a project nobody else can use… Maybe there can be some consensus on a common protocol. Gruss Bernd Von: Robert Munteanu Gesendet: Dienstag, 30. Januar 2018 11:21 An: Commons Developers List Betreff: Re: [Signing] New component for code

Re: [Signing] New component for code signing

Hi Bernd, On Wed, 2018-01-24 at 22:26 +0100, Bernd Eckenfels wrote: > +1 - and I would expect we also see a Server-side component. > > BTW: Eclipse also has some infrastructure for this (we use a modified > Version with a PHP backend on-prem) > >

Re: [Signing] New component for code signing

>>> this used and used it as the basis for a Maven plug-in. >>> >>> Currently, the Ant task is hosted within the Tomcat codebase and the >>> Maven plug-in within Sling. Both communities would like to move this to >>> a better home where it can more easil

Re: [Signing] New component for code signing

oth communities would like to move this to > > a better home where it can more easily be re-used by other Apache > > projects and other organisations using Symantec's code signing service. > > > > After some thought and discussion, we (Robert Munteanu and I) would like > > to

Re: [Signing] New component for code signing

Sling. Both communities would like to move this to > a better home where it can more easily be re-used by other Apache > projects and other organisations using Symantec's code signing service. > > After some thought and discussion, we (Robert Munteanu and I) would like > to propose this code signi

Re: [Signing] New component for code signing

: Gary Gregory Gesendet: Mittwoch, 24. Januar 2018 22:05 An: Commons Developers List Betreff: Re: [Signing] New component for code signing +1 Gary On Wed, Jan 24, 2018 at 1:35 AM, Benedikt Ritter <brit...@apache.org> wrote: > Hello Mark, > > +1 In my opinion this is exactly what

Re: [Signing] New component for code signing

th communities would like to move this to > > a better home where it can more easily be re-used by other Apache > > projects and other organisations using Symantec's code signing service. > > > > After some thought and discussion, we (Robert Munteanu and I) would like > >

Re: [Signing] New component for code signing

After some thought and discussion, we (Robert Munteanu and I) would like > to propose this code signing component as a new component at Commons. > Our reasons for this are as follows: > > - The code is written in Java > - It is a relatively small component > - It is a utility likely t

[Signing] New component for code signing

organisations using Symantec's code signing service. After some thought and discussion, we (Robert Munteanu and I) would like to propose this code signing component as a new component at Commons. Our reasons for this are as follows: - The code is written in Java - It is a relatively small component