Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330929

Summary:	Signing eclipse.exe
Product:	[Eclipse Project] Platform	Reporter:	John Arthorne <john.arthorne>
Component:	Releng	Assignee:	Kim Moir <kim.moir>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	kim.moir, pascal, pwebster
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:
Bug Blocks:	325997

Description John Arthorne

2010-11-23 10:26:48 EST

It looks like the Foundation has support in place to sign executables (See bug 319605). We can now use this support to sign the eclipse.exe in our build.

Comment 1 Pascal Rapicault

2010-11-23 10:34:56 EST

We have to be careful to what this means for RCP app creators since on windows the branding of the RCP app means bashing icons into the exe, which likely change the signature.

Comment 2 John Arthorne

2010-11-23 12:53:10 EST

Yes, anyone branding the executable will need to sign it again themselves after they bash it. The purpose of eclipse.org signing eclipse.exe, is so that users of the open source packages like EPP packages, Eclipse SDK, etc, don't get the goofy prompt every time they start eclipse on Windows Vista/7.

Comment 3 Kim Moir

2010-11-23 13:16:24 EST

Since this runs on the windows slave, this will have to be something that we implement after bug 325997 (build at eclipse.org) is resolved.  I don't think there is a way to directly access the windows slave from outside eclipse.org.

Comment 4 John Arthorne

2010-11-23 14:30:29 EST

I realized we already have a bug for this.

*** This bug has been marked as a duplicate of bug 319419 ***