Matthias
Nope, they just assume your configuration is set up to handle it.
Mine wasn't, I had to make special advanced exceptions in my browser
for how to search local addresses, and/or make some mysterious network
routing changes, and/or limit myself to the firefox on the server.
This was in addition to the self-immolation of the dbconsole by the
patching, and various other agent issues with multiple instances, some
of which result from incorrect implicit assumptions in the metalink
notes about the subject.
This would be a feature, not a bug, according to security mavens.
jg
--
@home.com is bogus.
What's in a name? (No offense meant to anyone, just LOL when I saw
this) http://www.signonsandiego.com/uniontrib/20081008/news_1m8club.html
If you want to unsecure it ... emctl unsecure dbconsole ... reverts
back to http