CMS_final(3SSL) OpenSSL CMS_final(3SSL)NAME
CMS_final - finalise a CMS_ContentInfo structure
SYNOPSIS
#include <openssl/cms.h>
int CMS_final(CMS_ContentInfo *cms, BIO *data, BIO *dcont, unsigned int flags);
DESCRIPTION
CMS_final() finalises the structure cms. It's purpose is to perform any operations necessary on cms (digest computation for example) and
set the appropriate fields. The parameter data contains the content to be processed. The dcont parameter contains a BIO to write content to
after processing: this is only used with detached data and will usually be set to NULL.
NOTES
This function will normally be called when the CMS_PARTIAL flag is used. It should only be used when streaming is not performed because the
streaming I/O functions perform finalisation operations internally.
RETURN VALUES
CMS_final() returns 1 for success or 0 for failure.
SEE ALSO ERR_get_error(3), CMS_sign(3), CMS_encrypt(3)HISTORY
CMS_final() was added to OpenSSL 0.9.8
1.0.0e 2008-04-10 CMS_final(3SSL)
Check Out this Related Man Page
CMS_uncompress(3SSL) OpenSSL CMS_uncompress(3SSL)NAME
CMS_uncompress - uncompress a CMS CompressedData structure
SYNOPSIS
#include <openssl/cms.h>
int CMS_uncompress(CMS_ContentInfo *cms, BIO *dcont, BIO *out, unsigned int flags);
DESCRIPTION
CMS_uncompress() extracts and uncompresses the content from a CMS CompressedData structure cms. data is a BIO to write the content to and
flags is an optional set of flags.
The dcont parameter is used in the rare case where the compressed content is detached. It will normally be set to NULL.
NOTES
The only currently supported compression algorithm is zlib: if the structure indicates the use of any other algorithm an error is returned.
If zlib support is not compiled into OpenSSL then CMS_uncompress() will always return an error.
The following flags can be passed in the flags parameter.
If the CMS_TEXT flag is set MIME headers for type text/plain are deleted from the content. If the content is not of type text/plain then an
error is returned.
RETURN VALUES
CMS_uncompress() returns either 1 for success or 0 for failure. The error can be obtained from ERR_get_error(3)BUGS
The lack of single pass processing and the need to hold all data in memory as mentioned in CMS_verify() also applies to CMS_decompress().
SEE ALSO ERR_get_error(3), CMS_compress(3)HISTORY
CMS_uncompress() was added to OpenSSL 0.9.8
1.0.1e 2013-02-11 CMS_uncompress(3SSL)
The UNIX and Linux Forums have a number of active members that have published books or papers related to shell programming and scripting. You can check out their publications here:
Link Removed
Please note, as you can imagine, our forum experts can be quite busy! You will get a response... (0 Replies)
Emergency UNIX and Linux Support !! Help Me! Forum (Request Urgent Help)
README FIRST: How to Request Emergency or Urgent Help:
You may post emergency work-related questions in the emergency forum. To post in this forum you will need to use your Bits. All questions answered on a "best... (0 Replies)
Homework Help:
On Posting Questions:
Any and all high school and undergraduate homework assignments or textbook style exercises for which you are seeking assistance are to be posted only in our Homework & Coursework Questions area--not in blogs, visitor messages, PMs, or the main technical... (0 Replies)
Dear Forum Members,
The UNIX and Linux Forums are working directly with the Red Cross to provide ad banners on our site to support Earthquake and Tsunami Relief in Japan. Registered users do not see these banners. However, if you wish to contribute directly on behalf of yourself and the... (8 Replies)
How to Use Code Tags in The UNIX and Linux Forums
Developer: This video tutorial was created by scott for forum users. Everyone should use code tags when posting code and command line logic in the forums.
cPF45jjWe7Q
A full list of BB codes is available here. (8 Replies)
RULES OF THE UNIX AND LINUX FORUMS
For the latest version of the community rules (the official community rules page), please visit here.
No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
No negative comments about others or impolite remarks. Be patient. No... (1 Reply)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Having spent a lot of time over the past year taking a legacy vBulletin site (this forum) and making the site responsive on mobile; I've happy with the results; but it will soon be time to move on.
Basically, at our core, we are a LAMP (Linux, Apache2, MySQL and PHP) site, and vBulletin was... (6 Replies)
Here are some answers to some of the recent questions I have received about UNIX.COM. So, I thought I would take time to answer them here in this post:
Is it expected that the original poster "thank" everyone who responds to his / her discussion thread?
It is always a good practice in all... (7 Replies)
By special request, and long overdue, I have updated our "code tags" video and so now we have:
How to Use Code Tags and Format Posts @UNIX.com in 4K
https://youtu.be/4BuPvWJV__k (3 Replies)
Here is a quick EOY report for 2019.
2019 has been a year of "downward trend reversal" for UNIX.com. In fact, if we compare total Google search impressions from the peak days in December 2019 to the peak days in mid December 2018, traffic is up 43% percent. That is a very respectable growth... (0 Replies)