<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="https://openwall.info/wiki/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://openwall.info/wiki/feed.php">
        <title>Openwall Community Wiki people:solar:algorithms</title>
        <description></description>
        <link>https://openwall.info/wiki/</link>
        <image rdf:resource="https://openwall.info/wiki/lib/tpl/local/images/favicon.ico" />
       <dc:date>2026-04-22T12:42:29+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://openwall.info/wiki/people/solar/algorithms/challenge-response-authentication?rev=1518876923&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://openwall.info/wiki/lib/tpl/local/images/favicon.ico">
        <title>Openwall Community Wiki</title>
        <link>https://openwall.info/wiki/</link>
        <url>https://openwall.info/wiki/lib/tpl/local/images/favicon.ico</url>
    </image>
    <item rdf:about="https://openwall.info/wiki/people/solar/algorithms/challenge-response-authentication?rev=1518876923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-02-17T15:15:23+02:00</dc:date>
        <title>Enhanced challenge/response authentication algorithms</title>
        <link>https://openwall.info/wiki/people/solar/algorithms/challenge-response-authentication?rev=1518876923&amp;do=diff</link>
        <description>Here are a couple of challenge/response authentication algorithms that I came up with while working on popa3d (a POP3 server).  The goal was to address the major drawback of existing simple C/R schemes such as APOP and CRAM-MD5 (where they would require storage of plaintext passwords or of plaintext-equivalents on the server, thereby possibly making the setup less secure than it would be with simple password authentication not involving C/R), yet not go all the way for public-key crypto (stay si…</description>
    </item>
</rdf:RDF>
