How are privacy and non-repudiation addressed by CORBASEC?
David Chizmadia
(September, 1998)14 : CORBASEC currently includes an
optional Non-Repudiation Security service. The SecSIG
currently expects to issue an RFP (Request for Proposal) for
a Data Protection service that would allow for applications
to request that a block of data be "wrapped" to protect both
its integrity and confidentiality. In both cases, the
services are easily implemented using (IDUP15 )-GSS as their
foundation. This is in addition to the message-level privacy
and integrity services already provided as part of the
current CORBASEC.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain some reason to avoid the development of multi-threaded corba application?
Is there a set of UML diagrams for the CORBASEC Specification?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
What ORBs claim to have security functionality?
Explain what is corba good for?
What would be the most suitable ORB products when buliding a small lab for evaluating, testing and implementing security functions in a CORBA system?
What is the reason to implement corba in client application application?
What is corba? What does it do?
What is CORBA?
Can corba allow servers to cause client side events or notifications?
Does CORBA security guarantee that the request and reply are not tampered and not intercepted on their way between the client and the target?
What's the difference between CORBA Security Service and CORBASEC?