| Creating internal mirrors - the finer points [message #306600] |
Wed, 02 August 2006 12:18  |
Eclipse User |
|
|
|
Originally posted by: miles.daffin.morganstanely.com
Dear All,
BACKGROUND INFO:
In common with many other enterprises we must prevent our eclipse users
from accessing external update sites, even eclipse and Callisto. To ensure
this our enterprise install of eclipse is *not* configured with proxy
information, and we are in the process of internally mirroring the core
sites.
THE PROBLEM:
All features reference their 'parent' update site in
feature.xml/url/update. If installed features reference external sites and
I run the "Search for updates of the currently installed features" the
update manager errors because it cannot get out to the external sites
mentioned in the installed feature meta.
OUR SOLUTION:
We edit the feature.xml files for all features (those in the eclipse
vanilla install and those we mirror) to reference the internal mirrors (we
also comment out any url/discovery elements). This seems safer than
relying *solely* on an update policy that names all mirrored features,
because if a mirrored site released a new feature this would be directly
accessible to a user.
THE QUESTIONS:
If we added the proxy info to the enterprise install, and added a url-map
pattern="*" at the bottom of our policy, would this prevent our users
circumventing the internal mirrors? What would happen if a user tried to
install a feature not explicitly covered by such a policy? (I have not
been able to test this.)
many thanks,
Miles Daffin
|
|
|
| Re: Creating internal mirrors - the finer points [message #306602 is a reply to message #306600] |
Wed, 02 August 2006 12:21  |
| Eclipse User |
|
|
|
Originally posted by: miles.daffin.morganstanely.com
I should have mentioned that we are creating mirrors using the standalone
updater.
Miles Daffin wrote:
> Dear All,
>
> BACKGROUND INFO:
>
> In common with many other enterprises we must prevent our eclipse users
> from accessing external update sites, even eclipse and Callisto. To ensure
> this our enterprise install of eclipse is *not* configured with proxy
> information, and we are in the process of internally mirroring the core
> sites.
>
> THE PROBLEM:
>
> All features reference their 'parent' update site in
> feature.xml/url/update. If installed features reference external sites and
> I run the "Search for updates of the currently installed features" the
> update manager errors because it cannot get out to the external sites
> mentioned in the installed feature meta.
>
> OUR SOLUTION:
>
> We edit the feature.xml files for all features (those in the eclipse
> vanilla install and those we mirror) to reference the internal mirrors (we
> also comment out any url/discovery elements). This seems safer than
> relying *solely* on an update policy that names all mirrored features,
> because if a mirrored site released a new feature this would be directly
> accessible to a user.
>
> THE QUESTIONS:
>
> If we added the proxy info to the enterprise install, and added a url-map
> pattern="*" at the bottom of our policy, would this prevent our users
> circumventing the internal mirrors? What would happen if a user tried to
> install a feature not explicitly covered by such a policy? (I have not
> been able to test this.)
>
> many thanks,
>
> Miles Daffin
|
|
|
Powered by
FUDForum. Page generated in 0.03014 seconds
Home