<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://old.andunix.net/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://old.andunix.net/feed.php">
        <title>andunix.net</title>
        <description></description>
        <link>https://old.andunix.net/</link>
        <image rdf:resource="https://old.andunix.net/_media/favicon.ico" />
       <dc:date>2026-06-03T22:04:13+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://old.andunix.net/info/cryptography/plaintext"/>
                <rdf:li rdf:resource="https://old.andunix.net/info/cryptography/openssl/print_key"/>
                <rdf:li rdf:resource="https://old.andunix.net/info/cryptography/openssl/print_certificate"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://old.andunix.net/_media/favicon.ico">
        <title>andunix.net</title>
        <link>https://old.andunix.net/</link>
        <url>https://old.andunix.net/_media/favicon.ico</url>
    </image>
    <item rdf:about="https://old.andunix.net/info/cryptography/plaintext">
        <dc:format>text/html</dc:format>
        <dc:date>2013-02-04T22:17:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Plaintext</title>
        <link>https://old.andunix.net/info/cryptography/plaintext</link>
        <description>Plaintext

The plaintext is unencrypted and unsigned text.
It's the payload which then get's signed and/or encrypted.

Wikipedia defines plaintext as:

	&quot; In cryptography, plaintext is information a sender wishes to transmit to a receiver. Cleartext is often used as a synonym. Before the computer era, plaintext most commonly meant message text in the language of the communicating parties. Plaintext has reference to the operation of cryptographic algorithms, usually encryption algorithms, and is …</description>
    </item>
    <item rdf:about="https://old.andunix.net/info/cryptography/openssl/print_key">
        <dc:format>text/html</dc:format>
        <dc:date>2015-01-29T09:15:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Print Information about a Key</title>
        <link>https://old.andunix.net/info/cryptography/openssl/print_key</link>
        <description>Print Information about a Key
openssl x509 -inform DER -in testkey.cer -noout -text
Informations about the used arguments from the OpenSSL man page:

	*  x509: Certificate display and signing utility.
	*  -inform DER: This specifies the input format normally the command will expect an X509 certificate but this can change if other options such as -req are present. The DER format is the DER encoding of the certificate and PEM is the base64 encoding of the DER encoding with header and footer lines …</description>
    </item>
    <item rdf:about="https://old.andunix.net/info/cryptography/openssl/print_certificate">
        <dc:format>text/html</dc:format>
        <dc:date>2015-12-09T07:36:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Print Information about a Certificate</title>
        <link>https://old.andunix.net/info/cryptography/openssl/print_certificate</link>
        <description>Print Information about a Certificate
openssl x509 -in testkey.crt -noout -text
Informations about the used arguments from the OpenSSL man page:

	*  x509: Certificate display and signing utility.
	*  -in testkey.crt: This specifies the input filename to read a certificate from or standard input if this option is not specified.</description>
    </item>
</rdf:RDF>
