That's what I came here to say as well. The failure to provide an SSL version of AdSense is one of the biggest impediments to the implementation of SSL-only sites on the net currently. Until they fix that, they are not entirely serious about this.

I wonder how often this will be misused:

To utilize the NoSSLSearch option for your network, please configure the DNS entry for www.google.com to be a CNAME for nosslsearch.google.com. We will not serve SSL search results for requests that we receive on this hostname. If we receive a search request over port 443, the certificate handshake will complete successfully, but we will then redirect the user to a non-SSL search experience along with an initial message explaining so.

http://www.google.com/support/websearch/bin/answer.py?hl=en&...

This can't be said enough. Has Google even acknowledged this as a security issue?