<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 4, 2014 at 4:56 PM, slush <span dir="ltr"><<a href="mailto:slush@centrum.cz" target="_blank">slush@centrum.cz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">I'm cracking my head for many months with the idea of using TREZOR for web auth purposes. Unfortunately I'm far from any usable solution yet.<div><br></div><div>My main comments to your BIP: Don't use bitcoin addresses directly and don't encourage services to use this "login" for financial purposes. Mike is right, mixing authentication and financial services is wrong. Use some function to generate other private/public key from bitcoin's seed/private key to not leak bitcoin-related data to website.</div>
<div><br></div></div></blockquote><div><br></div><div>I'm probably very naive, but the fact that the authentication key is your Bitcoin address was for me a great feature :)</div><div>What are the risks associated of id yourself with a bitcoin address you plan to use on the website for transaction ?</div>
<div><br></div><div>I mean, what is the difference between doing that, and id with a login/pass and add your bitcoin address in a settings field ? (knowing you could always find a mechanism to transfer the account to another bitcoin address if needed)</div>
<div><br></div><div>Eric</div><div><br></div></div></div></div>