[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] Bundle-Verification, Security, Permissions and Hooks
- From: "Pepping, Florian" <florian.pepping@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 May 2009 16:35:10 +0200
- Delivered-to: email@example.com
- Thread-index: AcnNjKkaG30ydICnRe6dy4fVsdo5wQAABzUg
- Thread-topic: [equinox-dev] Bundle-Verification, Security, Permissions and Hooks
you understood my problems
in very detail. I use the "osgi.framework.extension"-property to configure my
hook and tested a little bit with the
Both with no success
concerning my problems. The framework always starts without any
Now I look for an
alternative/technical solution, how to reach that the framework only starts,
when all hooks or bundles are found and verified.
The config.ini would be a
possibility, if it could be signed or crypted. Another possibility would be to
have a JVM-Option compiled into a startup exe. Both are no perfect solutions but
Perhaps you have some
further ideas how to solve this problem. And I wonder, if this requirement never
came up before.
> Now my question:
> How can I make sure, that my
framework-hook is recognized by the
> framework and the framework
only starts, when this hook is available? Or is there another
possibility where to execute these operations?
asking how to configure your framework extension (which contains your
framework-hook) into the framework? Or looking for some way to prevent the
framework from launching if your extension is not present?
assume you are already using the osgi.framework.extensions property to specify
your framework hook and then launching the framework with the equinox launcher
(org.eclipse.equinox.launcher). The launcher will search for the framework
extensions specified by this property but it will not fail if it cannot find a
framework extension specified in this property. The Framework does not
fail to launch if an extension is not found it just continues on with the
default set of framework-hooks. This would require an enhancement to the
framework. But I'm not sure how we would enforce it. It would have
to involve some configuration (a setting in the config.ini) to tell the
framework to fail when an extension is not present. But this setting could
easily be switched off which would open the door again. You could use a
bundle on top that verifies that your hook is present and force a shutdown
(and/or log an error) if it did not find your extension. But this bundle
could be missing also ...
> Thanks in advance for your
> Florian Pepping
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193
Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.