user6707: Pay to public key hash scripts hash the recipients public key for added security.
Is the same done with the public keys that make up part of a multisig script?
https://en.bitcoin.it/wiki/Script doesn't seem to indicate they are.

user208: Typically, you will use P2SH (pay to script hash) for multisig transactions, which means the transaction output does not contain the full script (with full public keys), but instead a hash of that script - and the full script is revealed when spending. See BIP16 for more information.
When this is done, you get the same effect: the transaction output does not contain a public key directly.
Note that there is indeed a  small security benefit to this (it takes 2^160 steps in theory to reverse the hash function, while it takes 2^128 steps to find a private key for a given public key), but there are larger advantages (like the sender not needing to know the full script, and less data in the database of unspent transaction outputs that every full node maintains).

user21052: Yes and no.
In a bare multisig pubkey script, the public keys are not hashed.  For example, a 2-of-3 pubkey script would look like:
2 <pubkey1> <pubkey2> <pubkey3> 3 OP_CHECKMULTISIG

In a multisig pay-to-script-hash (P2SH) script, the whole redeem script---including the public keys---would be hashed.  For example, the redeem script would be the same as above, but the actual pubkey script would be:
OP_HASH160 <Hash160(redeemScript)> OP_EQUAL

Almost all multisig transactions on the network currently use P2SH multisig.
As an aside, although there is some hypothetical security increase from hashing public keys in case of a major problem with ECDSA, the main reason for hashing public keys is to create short addresses.

6707: <p>Pay to public key hash scripts hash the recipients public key for added security.</p>

<p>Is the same done with the public keys that make up part of a multisig script?</p>

<p><a href="https://en.bitcoin.it/wiki/Script" rel="nofollow">https://en.bitcoin.it/wiki/Script</a> doesn't seem to indicate they are.</p>
 208: <p>Typically, you will use P2SH (pay to script hash) for multisig transactions, which means the transaction output does not contain the full script (with full public keys), but instead a hash of that script - and the full script is revealed when spending. See BIP16 for more information.</p>

<p>When this is done, you get the same effect: the transaction output does not contain a public key directly.</p>

<p>Note that there is indeed a  small security benefit to this (it takes 2^160 steps in theory to reverse the hash function, while it takes 2^128 steps to find a private key for a given public key), but there are larger advantages (like the sender not needing to know the full script, and less data in the database of unspent transaction outputs that every full node maintains).</p>
 21052: <p>Yes and no.</p>

<p>In a bare multisig pubkey script, the public keys are not hashed.  For example, a 2-of-3 pubkey script would look like:</p>

<pre><code>2 &lt;pubkey1&gt; &lt;pubkey2&gt; &lt;pubkey3&gt; 3 OP_CHECKMULTISIG
</code></pre>

<p>In a multisig pay-to-script-hash (P2SH) script, the whole redeem script---including the public keys---would be hashed.  For example, the redeem script would be the same as above, but the actual pubkey script would be:</p>

<pre><code>OP_HASH160 &lt;Hash160(redeemScript)&gt; OP_EQUAL
</code></pre>

<p>Almost all multisig transactions on the network currently use P2SH multisig.</p>

<p>As an aside, although there is some hypothetical security increase from hashing public keys in case of a major problem with ECDSA, the main reason for hashing public keys is to create short addresses.</p>
