Your answer for ?#2 states that the encryption of the message with the private key is the actual signing for the message.
This is can be true but it is not used b/c asymmetric encryption is not used for large messages and there is no way (currently) for the encryption algorithm to determine a large message from an small message. If it did exist then the encryption algorithm would have to change from asymmetric to symmetric to adjust for the large data load.
Rather the use of an authenticator (small block of bits that is a function of the message.) (pg 72 Network Security Essentials-William Stallings[great book]) is used. this is a secure hash method
this authenticator is then encrypted to provide a secure hash, usually MD5 or SHA-1. this encrypted hash provides a way to verify the signature with the signers public key. No this does not provide data confidentiality but it is the way a digital signature is processed in the industry.
the answer your test gives provides both confidentiality and a signature verification but then it isn't really confidential b/c anyone can access the 'public key' and decrypt the message. the secure hash provides a small block of data to use with the asymmetric algorithm providing verification and integrity while not worrying about confidentiality. This is why we don't use private keys for encryption. We use the public key and only the private key holder can open it.
This isn't the only way to but it is the most practical
So over all the answer to Sec+ ?#2 should be "the encryption of the hash value with someones private key" -- again b/c we are looking at verification and not confidentiality
Thanks,
James
bohlingj@saic.com