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 is the current version of CORBASEC official specification?
What ORBs claim to have security functionality?
Are CORBAsec implementations from the US generally subjected to export control?
What is the reason to implement corba in client application application?
Does corba supports asynchronous communication?
What is "Principal", and what is meant by "Principal authentication"?
What are the reason to implement a corba application with multi-threading?
Can we modify an object in CORBA?
Can corba application be multi-threaded?
What's the difference between CORBA Security Service and CORBASEC?
What's CORBASEC?
What are the protocols used by CSI?