Mon Apr 29 03:59:43 2019: Request 129312 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: PAR-Packer
     Subject: Re: [rt.cpan.org #129312] Code signing for OSX
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=129312 >


I tried it out and I have been able to create my executable, fix it and
code sign it correctly. Great job!

Welle

Am So., 28. Apr. 2019 um 14:08 Uhr schrieb Kime Philip via RT <
[email protected]>:

> Sun Apr 28 08:08:23 2019: Request 129312 was acted upon.
> Transaction: Correspondence added by [email protected]
>        Queue: PAR-Packer
>      Subject: Re: [rt.cpan.org #129312] Code signing for OSX
>    Broken in: (no value)
>     Severity: (no value)
>        Owner: Nobody
>   Requestors: [email protected]
>       Status: open
>  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=129312 >
>
>
> I believe that I now have a fix for this. See:
>
> https://github.com/rschupp/PAR-Packer/pull/14
>
> There is a contributed small program which is run on the pp exe and edits
> it in-place. This makes codesigning work. There is a also a small fix for
> par.pl required in PAR::Packer to allow unpacking of codesigned exes.
> With these two elements in place, in my tests, I can codesign and run a pp
> binary.
>
> PK
>
> > On 28 Apr 2019, at 12:37 am, Kime Philip <[email protected]> wrote:
> >
> >
> > Looking into this further, I am fairly sure that Archive::Zip::ChunkSize
> needs to be increased in par.pl and also the 128k limit for the PAR
> signature also needs to be increased. Doubling both to 256k would likely be
> appropriate. All tests for PAR::Packer pass if I do this but I still get
> the same error after codesigning so I am missing something as Archive::Zip
> still fails to find the EOCD marker for some reason, even with the
> increased window size which does (I have checked) include the EOCD marker
> once the ChunkSize has been modified.
> >
> > --
> > Dr Philip Kime
> >
>
> --
> Dr Philip Kime
>

Reply via email to