Does MoonCoin have the same backdoor as TIPS to steal wallets even with the private key ?
I was reading a document and you can "apparently" clone other peoples wallets and even though there is a private key you can still gain access to it by making a mould....
Maybe that is what happened.
No, I already posted what happened after I talked to Cryptsy's fraud dept.
This was not Cryptsy's fault -
people left same RPC PASS/Login across multiple wallets and someone with daemon wallet cleared them out.But during the last days I tried to connect via RPC to my mooncoin wallet, testing different mooncoin.conf configurations. And it
was not possible for me to reach it because the
RPC Port 44663 is not reachable from the internet
because my router doesnt know what to do with port 44663. And my computer with the wallet ALWAYS was behind a router. The only way to establish connections from the outside to my wallet is with P2P Port 44664, which the wallet uses for mooncoin network communication.
As long as no one can get access to a mooncoin wallet via RPC (mooncoin.conf in server mode and no rpcuser and no rpcpass set) it is unlikely that the thief could connect via RPC !Please help to think about other vulnerabilities so that we can find the real reason to disable it within the coming new wallet version!What is with the SSH-Heartbleed bug?Does MoonCoin have the same backdoor as TIPS to steal wallets even with the private key ?
I was reading a document and you can "apparently" clone other peoples wallets and even though there is a private key you can still gain access to it by making a mould....
Maybe that is what happened.
--> this is also something we should think about, could you please send me details about the fedoracoin issue?And to avoid panic: please keep your coins ALWAYS in an ENCRYPTED wallet. Then every transaction out needs the wallet passphrase. I made this mistake to not encrypt my wallet and the thief could initiate transactions, on which way ever (we have to find out).best regards,
peme