The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.


Authen::Challenge::Basic - A Basic challenge/response authentication scheme.


        use Authen::Challenge::Basic;

        $server = Authen::Challenge->new ('Secret' => 'known2us',
                                          'Timeout' => 30,
                                          'Sync' => 10);

        $client = Authen::Challenge->new ('Secret' => 'known2us',
                                          'Timeout' => 30,
                                          'Sync' => 10);

        $challenge = $server->Challenge;
        $response = $client->Response($challenge);

        if ($server->Validate($challenge, $response)) {
                print "Hi master\n";
        else {
                print "Impostor!\n";


Authen::Challenge::Basic provides a simple MD5-based challenge/response protocol allowing for mutual peer authentication in a session. The protocol includes timing information, so it is possible to introduce time constraints in the session to help prevent attacks that rely on adjusting the clock in one of the peers.

This protocol requires a shared secret to be known only to the peers. The compromise of this secret also compromises this protocol, so it should be treated as a trusted password for that matter.

Challenge/response sessions are not 'replayable' provided that the attacker ignores the shared secret. The sessions are also associated to the instance that produced the challenge. This means that it can only be Validate()'d by the instance that produced the challenge in the first place.

The built-in random number generator from perl is used in this module. Hooks for better random number generators are planned soon to increase the relative strength of this protocol. In any case, the main security dependencies for this module are MD5 itself and the secrecy of the shared secret.

The following functions are provided by this class.


Creates a new instance of a challenge/response endpoint. It has three parameters that influence its behavior. Those can be seen next

        $server = Authen::Challenge::Basic->new ('Secret' => 'known2us',
                                                 'Timeout' => 30,
                                                 'Sync' => 10);

'Secret' is used to indicate the shared secret to use in this session.

'Timeout' specifies the lifespan, in seconds, for this transaction. This means that a succesful Validate() must occur within this many seconds to have a chance to be acknowledged. Reducing this value too much can cause problems as a slight ammount of load can make the session fail. 30 seconds is a reasonable default for many uses. If left unspecified, no timeout is enforced.

'Sync' indicates how strict are we with regard to the clock in our peer. The parameter contains the maximum offset in seconds between the clocks of the peers. The more strict we are (ie, the smaller the number), the less tolerant we are. If left unspecified, we'll allow any ammount of drift. It's specified in seconds.


Issues a new challenge. The object creating this challenge stores information about it that allows for later recognition and validation. The Challenge() is a typical function of the server, though a double Challenge/Response scenario allows mutual authentication such as in the following scheme:

                Client                          Server
(1)               C1    ---------------------->   
(2)                     <----------------------  R(C1), C2
(3)             R(C2)   ---------------------->

On stage (2), the Client is authenticated to the server. On stage (3), both are mutually authenticated.

This method is usually invoked like

        $challenge = $server->Challenge;

$challenge will contain a printable string that must be passed to the peer in order for a response to be received.


This method takes a challenge and generates the required response. This is usually invoked as

        $response = $client->Response($challenge);

Where $challenge contains a Challenge generated by a call to Challenge(). $response will contain a printable string that must be returned to the peer in order for it to be validated.


This method verifies the correctness of the Challenge/Response session by insuring that:

        (a) The challenge was indeed generated from this instance 
        and is pending validation
        (b) The time interval for the validation is acceptable
        (c) The shared secret was used by the peer to create the 

Usually this method is invoked like this

        $r = $server->Validate($challenge, $response);

It returns a true value to indicate a correct session where (a), (b) and (c) hold true or false otherwise.


Note that this module helps insure that the peers were who they said they where provided that the shared secret is not known to any third parties. If this is not true, then anything could happen.

Also, after the initial authentication, a network connection can be stolen or hijacked, rendering all of the tests useless.


Luis E. Munoz <>