Quote from: HinnomTX on September 29, 2014, 09:14:30 PM

Quote from: vertoe on September 29, 2014, 09:05:22 PM

Quote from: janos666 on September 29, 2014, 08:59:15 PM

Quote from: Ignition75 on September 29, 2014, 08:39:49 PM

Quote from: Drobek on September 29, 2014, 03:05:35 PM

Quote from: stonehedge on September 29, 2014, 02:32:52 PM

Bad luck Ed.
And to think that I know of some people running hot masternodes on spot instances. Lets hope they've got backups Cheesy

Are people still running hot masternodes? Why?

What's the issue with hot nodes? As long as your password is strong enough and your firewall is configured right nobody is going to touch your coins...

At least until the next episode of the HearthBleed and Bash bugs. Cheesy

So what, as long as the wallet encryption holds ...

It's not that simple. If you run with a password protected wallet, you need to ensure that there is no bash history or ps listing that may store (and hence give away) your password. There are ways to configure your MN to minimize this risk, but as another posted on here, don't ever make any mistakes, not even once.
If one day you forget to use darkcoind masternode start 'head -1' and instead, being in a hurry or some such, use darkcoind masternode start MYPASSWORDCUZIMINAHURRY , well, 'ps -ef' is going to show your password. It goes without saying that heartbleed and shellshock show just how fragile our systems of security really are.

As I said earlier, its fine just as long as you never screw up.

Also, vertoe has taught me a few tricks that make it easier to be secure in hot mode (thread on DCT I think).