[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Eclipse CHE signing issue

Yeah, thanks we saw this, CHE is not working without guice AOP, Âbut it works with cglib 3.2.0+. Unfortunately there latestÂguiceÂtag still using 3.1. So we probably fill fork guice and rebuild it with newer cglib until they will release new version.

On Fri, Apr 1, 2016 at 11:44 AM, Dennis HÃbner <dennis.huebner@xxxxxxxxx> wrote:
If I recall it right, Âyou are using Gin in che as well?
Iâm not sure it is up to date, but here is a nice feature comparison table:


Am 01.04.2016 um 10:34 schrieb Roman Iuvshin <riuvshin@xxxxxxxxxxx>:

jarsigner -verify che-plugin-docker-machine-4.0.1.jarÂ
jar verified.

So yes jars signed properly, now we are investigating is it possible to switch ti no AOP guice.
we have feeling that some interceptors may not work without AOP


On Fri, Apr 1, 2016 at 10:06 AM, Dennis HÃbner <dennis.huebner@xxxxxxxxx> wrote:
âif all the jars are properly signed, you could try to use "guice no aopâ Âversion,
which afaik works without bytecode manipulation.


Am 01.04.2016 um 08:54 schrieb Dennis HÃbner <dennis.huebner@xxxxxxxxx>:

Hi Roman,
it doesnât seem to be a guice related issue.
You need to make sure that all the classes with package: âorg.eclipse.che.plugin.docker.machine"
loaded by the classloader are signed.Â
You can use jarsigner -verify for all your org.eclipse.che.* jars to make sure they are properly signed

Best regards,
Dennis.
Â
Am 31.03.2016 um 17:57 schrieb Roman Iuvshin <riuvshin@xxxxxxxxxxx>:


---------- Forwarded message ----------
From: Eclipse Webmaster (Denis Roy) <webmaster@xxxxxxxxxxx>
Date: Thu, Mar 31, 2016 at 6:50 PM
Subject: Re: Eclipse CHE signing issue
To: Roman Iuvshin <riuvshin@xxxxxxxxxxx>, Wayne Beaton <wayne@xxxxxxxxxxx>, MikaÃl Barbero <mikael@xxxxxxxxxxx>, Tyler Jewell <tjewell@xxxxxxxxxxx>, Stevan Le Meur <slemeur@xxxxxxxxxxx>, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx>, Gennady Azarenkov <gazarenkov@xxxxxxxxxxx>


Hi Roman,

Your best bet is to ask on the cbi-dev mailing list. Perhaps someone
else has run into that issue (either at Eclipse or within their
corporation) and can offer some guidance.

https://dev.eclipse.org/mailman/listinfo/cbi-dev

Denis

On 03/31/2016 11:43 AM, Roman Iuvshin wrote:
> Hi guys,
> We faced with issue that CHE does not work after jar signing procedure.
> The problem is that we are heavily using google guice framework which
> doing some class modification in runtime and it fails:
>
>Â Â ÂCaused by: java.lang.SecurityException: class
>Â Â Â"org.eclipse.che.plugin.docker.machine.DockerInstanceProvider$$EnhancerByGuice$$9762f377"'s
>Â Â Âsigner information does not match signer information of other
>Â Â Âclasses in the same package\
>
>
> FYI I've redeployed CHE bundles with not signed ones on eclipse download
> server until we will find any solution.
>
>

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Viele GrÃÃe,
Dennis HÃbner


Viele GrÃÃe,
Dennis HÃbner


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Viele GrÃÃe,
Dennis HÃbner


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev