Inform yourself about the HTTP Digest authentication method How is it better than HTTP Basic? Which risks do still exist? What would a client send as a response to the following server message, if his username would beMx" and his password-Secure123"? 1. 2. 3. Request GET /index.html HTTP/1.1 Host: localhost Response HTTP/1.0 401 Unauthorized www-Authenticate: Digest realm-"Secured Area", nonce-"aer95b7fg2dd2hhe8b11d0f6f7afb0c14v" Content-Length: 0 Inform yourself about the way, how Public Key- Authentication in SSH Authentication Protocol2 works. Configure the SSHD service on a server (or the local machine), so that it enables Public Key Authentication 1. Create a key pair for a user: ssh-keygen -t rsa 2. Transfer the public key to the server: ssh-copy-id-i ssh/id_rsa.pub fuserl@server) 3. Configure the SSH service to use the Public Key Authentication a. Remove the comment symbols in /etc/ssh/sshd config in the rows with PublicKeyAuthentication yes and AuthorizedFiles.ssh/authorized keys Restart the service:/etc/init.d/sshd restart b. 4. Test the authentication using the newly created keys