|
Title: hearbleed, do I have to change my password for my wallet file? Post by: ajk on April 09, 2014, 08:44:16 PM Hi
just wondering if heartbleed is any cause for concern regarding changing my wallets current password, I have never used the 0.9.0 client still on version 0.8.6 will downloading the newest version 0.9.1 fix any of the data leaking concerns/possible theft of bitcoin? thanks Title: Re: hearbleed, do I have to change my password for my wallet file? Post by: DannyHamilton on April 09, 2014, 09:43:03 PM Hi just wondering if heartbleed is any cause for concern regarding changing my wallets current password, I have never used the 0.9.0 client still on version 0.8.6 will downloading the newest version 0.9.1 fix any of the data leaking concerns/possible theft of bitcoin? thanks Since you are running a version older than 0.9.0, you are only at risk if you are running the rpcssl command line option, or have entered that option into your bitcoin.conf. If you don't know what that is, then you are almost certainly not using it, and therefore don't have to worry about your Bitcoin-Qt being affected by the Heartbleed bug. Title: Re: hearbleed, do I have to change my password for my wallet file? Post by: Dare on April 09, 2014, 11:46:36 PM Hi just wondering if heartbleed is any cause for concern regarding changing my wallets current password, I have never used the 0.9.0 client still on version 0.8.6 will downloading the newest version 0.9.1 fix any of the data leaking concerns/possible theft of bitcoin? thanks Since you are running a version older than 0.9.0, you are only at risk if you are running the rpcssl command line option, or have entered that option into your bitcoin.conf. If you don't know what that is, then you are almost certainly not using it, and therefore don't have to worry about your Bitcoin-Qt being affected by the Heartbleed bug. While this is true, updating to 0.9.1 (which fixes the Heartbleed bug, and is safe) wouldn't be a bad idea. The official announcement (which is currently also in the news section of the forum header) can be found here (https://bitcointalk.org/index.php?topic=562400.0). Title: Re: hearbleed, do I have to change my password for my wallet file? Post by: freedomno1 on April 09, 2014, 11:53:26 PM Hi just wondering if heartbleed is any cause for concern regarding changing my wallets current password, I have never used the 0.9.0 client still on version 0.8.6 will downloading the newest version 0.9.1 fix any of the data leaking concerns/possible theft of bitcoin? thanks Since you are running a version older than 0.9.0, you are only at risk if you are running the rpcssl command line option, or have entered that option into your bitcoin.conf. If you don't know what that is, then you are almost certainly not using it, and therefore don't have to worry about your Bitcoin-Qt being affected by the Heartbleed bug. While this is true, updating to 0.9.1 (which fixes the Heartbleed bug, and is safe) wouldn't be a bad idea. The official announcement (which is currently also in the news section of the forum header) can be found here (https://bitcointalk.org/index.php?topic=562400.0). I agree having the newest software is always useful, on the rare occasion 0.9.0 that may be a bit of a problem but updating the QT client now and then is important only a few more to go till we hit 1.0 hehe Title: Re: hearbleed, do I have to change my password for my wallet file? Post by: cp1 on April 17, 2014, 08:13:52 PM Hi just wondering if heartbleed is any cause for concern regarding changing my wallets current password, I have never used the 0.9.0 client still on version 0.8.6 will downloading the newest version 0.9.1 fix any of the data leaking concerns/possible theft of bitcoin? thanks Since you are running a version older than 0.9.0, you are only at risk if you are running the rpcssl command line option, or have entered that option into your bitcoin.conf. If you don't know what that is, then you are almost certainly not using it, and therefore don't have to worry about your Bitcoin-Qt being affected by the Heartbleed bug. You'd also have to have that port open to the world. Though if you had any port using openssl open to the world then you were vulnerable. |