The AUF repository contains digitally signed Release files.
 This package contains the repository key used for that.
 
 Le dépôt AUF contient des fichiers Release signés électroniquement.
 Ce paquet contient la partie publique des clés utilisées pour cela.

 File::Listing exports a single function called parse_dir(), which can be used
 to parse directory listings.
 
 The first parameter to parse_dir() is the directory listing to parse. It can
 be a scalar, a reference to an array of directory lines or a glob
 representing a filehandle to read the directory listing from.
 
 The second parameter is the time zone to use when parsing time stamps in the
 listing. If this value is undefined, then the local time zone is assumed.
 
 The third parameter is the type of listing to assume. Currently supported
 formats are 'unix', 'apache' and 'dosftp'. The default value 'unix'.

 This class is for objects that represent a "cookie jar" -- that is, a
 database of all the HTTP cookies that a given LWP::UserAgent object knows
 about.
 
 Cookies are a general mechanism which server side connections can use to both
 store and retrieve information on the client side of the connection. For more
 information about cookies refer to
  and
 . HTTP::Cookies also implements the new
 style cookies described in RFC 2965. The two variants of cookies are supposed
 to be able to coexist happily.
 
 Instances of the class HTTP::Cookies are able to store a collection of
 Set-Cookie2: and Set-Cookie: headers and are able to use this information to
 initialize Cookie-headers in HTTP::Request objects. The state of a
 HTTP::Cookies object can be saved in and restored from files.

 Instances of the HTTP::Daemon class are HTTP/1.1 servers that listen on a
 socket for incoming requests. The HTTP::Daemon is a subclass of
 IO::Socket::INET, so you can perform socket operations directly on it too.
 
 The accept() method will return when a connection from a client is available.
 The returned value will be an HTTP::Daemon::ClientConn object which is
 another IO::Socket::INET subclass. Calling the get_request() method on this
 object will read data from the client and return an HTTP::Request object. The
 ClientConn object also provide methods to send back various responses.
 
 This HTTP daemon does not fork(2) for you. Your application, i.e. the user of
 the HTTP::Daemon is responsible for forking if that is desirable. Also note
 that the user is responsible for generating responses that conform to the
 HTTP/1.1 protocol.

 The HTTP::Headers class encapsulates HTTP-style message headers. The headers
 consist of attribute-value pairs also called fields, which may be repeated,
 and which are printed in a particular order. The field names are cases
 insensitive.
 
 Instances of this class are usually created as member variables of the
 HTTP::Request and HTTP::Response classes, internal to the library.

 HTTP::Negotiate provides a complete implementation of the HTTP content
 negotiation algorithm. Content negotiation allows for the selection of a
 preferred content representation based upon attributes of the negotiable
 variants and the value of the various Accept* header fields in the request.

 The Net::HTTP class is a low-level HTTP client.  An instance of the
 Net::HTTP class represents a connection to an HTTP server.  The
 HTTP protocol is described in RFC 2616.  The Net::HTTP class
 supports HTTP/1.0 and HTTP/1.1. Net::HTTP is a sub-class of IO::Socket::INET.
 You can mix its methods with reading and writing from the socket directly.
 This is not necessarily a good idea, unless you know what you are doing.

 libwww-perl (also known as LWP) is a collection of Perl modules that provide
 a simple and consistent programming interface (API) to the World-Wide Web.
 The main focus of the library is to provide classes and functions that allow
 you to write WWW clients. It also contains general purpose modules, as well
 as a simple HTTP/1.1-compatible server implementation.

 WWW::RobotRules parses /robots.txt files as specified in "A Standard for
 Robot Exclusion", at . Webmasters
 can use the /robots.txt file to forbid conforming robots from accessing parts
 of their web site.
 
 The parsed files are kept in a WWW::RobotRules object, and this object
 provides methods to check if access to a given URL is prohibited. The same
 WWW::RobotRules object can be used for one or more parsed /robots.txt files
 on any number of hosts.

 This metapackage is a convenient way to install both the OpenSSH client
 and the OpenSSH server. It provides nothing in and of itself, so you
 may remove it if nothing depends on it.

 This is a transitional package depending on the regular Debian OpenSSH
 client and server, which now support GSSAPI natively. It will add the
 necessary GSSAPI options to the server configuration file. You can
 remove it once the upgrade is complete and nothing depends on it.