<commit_before>
MAKE_TA (1)                 ROA-PKI                                   MAKE_TA(1)


NAME
        make_TA - constructs a CMS structure to hold an EE certificate and a
              self-signed RTA certificate, and signs it.

SYNOPSIS   

        make_TA ETAcertificate EEcertificate RTAcertificate EEkeyfile outfile

DESCRIPTION
    
        The files specified in the first four parameters are read, checked,
        assembled into the CMS structure, and signed.  The parameters are as 
        follows: ETAcertificate is the name of the file containing the ETA's 
        certificate, EEcertificate is the name of the file containing the EE 
        certificate, RTAcertificate is the name of the file containing the RTA 
        certificate, EEkeyfile is the name of ".p15" file containing the key 
        material for the EE, and outfile is the name of the file where the 
        resulting CMS structure will be put.  In addition, the program produces
        a more readable version of the contents of outfile in a file of the 
        same name but suffixed with ".raw".

        Response messages:

          Usage: file names: ETA cert, EE cert, RTA cert, EE key, outfile
          Finished OK
          Usage: nanes of .cms file, ETA certificate file, RTA destination file
          Couldn't get ...
          Error inserting ...
          EE ... cert doesn't match ETA cert's
          Error signing in ...

       where the ellipsis is replaced with specific information.
                             <commit_msg>Added a little bit.<commit_after>
MAKE_TA (1)                 ROA-PKI                                   MAKE_TA(1)


NAME
        make_TA - constructs a CMS structure to hold an EE certificate and a
              self-signed RTA certificate, and signs it.

SYNOPSIS   

        make_TA ETAcertificate EEcertificate RTAcertificate EEkeyfile outfile

DESCRIPTION
    
        The files specified in the first four parameters are read, checked,
        assembled into the CMS structure, and signed.  The parameters are as 
        follows: ETAcertificate is the name of the file containing the ETA's 
        certificate, EEcertificate is the name of the file containing the EE 
        certificate, RTAcertificate is the name of the file containing the RTA 
        certificate, EEkeyfile is the name of ".p15" file containing the key 
        material for the EE, and outfile is the name of the file where the 
        resulting CMS structure will be put.  In addition, the program produces
        a more readable version of the contents of outfile in a file of the 
        same name but suffixed with ".raw".  The label and password used for
        the EEkeyfile are hard-coded as "label" and "password".

        Response messages:

          Usage: file names: ETA cert, EE cert, RTA cert, EE key, outfile
          Finished OK
          Usage: nanes of .cms file, ETA certificate file, RTA destination file
          Couldn't get ...
          Error inserting ...
          EE ... cert doesn't match ETA cert's
          Error signing in ...

       where the ellipsis is replaced with specific information.
                             
{'fraction_non_alphanumeric': 0.03864278982092366, 'fraction_numerical': 0.0025133521834747093, 'mean_word_length': 1.9868667917448406, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6384571', 'n_tokens_mistral': 829, 'n_tokens_neox': 758, 'n_words': 399}