Uses of Interface
be.fgov.ehealth.etee.crypto.utils.DataPipe

Packages that use DataPipe

be.fgov.ehealth.etee.crypto.decrypt	Classes for validation and unsealing of sealed message.
be.fgov.ehealth.etee.crypto.utils	Utilities used by CryptoLib.

Uses of DataPipe in be.fgov.ehealth.etee.crypto.decrypt

Methods in be.fgov.ehealth.etee.crypto.decrypt with parameters of type DataPipe

CryptoResult<UnsealedData>	DataSealChecker.stamp(java.io.InputStream data, java.io.OutputStream stampedData, byte[] timestamp, DataPipe pipe) Puts a timestamp on sealed data to prove that it existed in that state on a certain moment in time. The updated sealed message will be written into the given outputstream.
CryptoResult<UnsealedData>	DataSealChecker.validate(java.io.InputStream data, java.io.OutputStream verifiedData, DataPipe pipe) Verify if the sealed data is acceptable according to specified policies (ocsp, signing, encryption). Different levels of notifications can be added to the result (warning, error, fatal). Additional data from the result can be used for further verifications.
CryptoResult<UnsealedData>	DataSealChecker.validate(java.io.InputStream data, java.io.OutputStream verifiedData, DataPipe pipe, SigningCredential... signers) Verify if the sealed data is acceptable according to specified policies (ocsp, signing, encryption). Different levels of notifications can be added to the result (warning, error, fatal). Additional data from the result can be used for further verifications. If credential(s) of a signer are given, message must be signed with one of the given credentials.

Uses of DataPipe in be.fgov.ehealth.etee.crypto.utils

Classes in be.fgov.ehealth.etee.crypto.utils that implement DataPipe

class	DataPipeInFile Data pushed into the pipe is written to file. Data read from the pipe is read from that file.
class	DataPipeInMemory DataPipe using an in memory mechanism to push all the incoming data to an inputstream once the getFrom() method is called.