Are the any interfaces specified in CORBASEC for
controlling security context by security-aware
applications?
Extended Question:
Examples of controlling security context could be the
following:
* Switch context, a possibility of "switching
context service" between already established contexts
* Hold-on context in case of mobility
* Close/take-down context
* Re-establish context after hold-on context service
* Refresh context in case of revocation or as the
same operation as Refresh() in SecurityContext
| Is This Answer Correct ? | 0 Yes | 0 No |
What are the protocols used by CSI?
What is available in CORBASEC for strong (writer-to-reader) authentication?
Can we modify an object in CORBA?
Explain are there important forms of asynchronous communication that are not supported directly by corba?
What are the semantic connotations for rights in CORBA rights family?
Explain do different corba implementations perform at significantly different levels?
How does CORBA security affect application writers?
Are CORBAsec implementations from the US generally subjected to export control?
What are the reason to implement a corba application with multi-threading?
Explain high-level technical overview of corba?
What is the reason to implement corba in client application application?
What's the difference between CORBA Security Service and CORBASEC?