If I unlock my account on my system at 2:00 and someone breaks into my system at 3:00, can they retrieve my private key? Can anyone help me here? I'm trying to figure out if my private key can be stolen after I unlock my account. |
|
|
|
|
How am I doing?
23341 9433259657262176905 Mon Dec 23 16:33:42 2013
1 0 + 1 142 B
1 4130762073563279823 1244 %
|
|
|
|
|
If I unlock my account on my system at 2:00 and someone breaks into my system at 3:00, can they retrieve my private key?
|
|
|
|
If I open my wallet in the VPS, is it insecure and if so, why is it more insecure than doing the same in my laptop? There is a risk (which you cannot control) that someone on VPS company has a backdoor access to your server. Does the security risk come from someone intercepting your private key when you submit it to your server? Is there any risk *after* you have unlocked your account on the VPS? I'd really like to run my account's node in a remote VPS and I'm hoping I could destroy/recreate the VPS before entering my private key in order to minimize the risk. |
|
|
|
Why does refreshing the browser lock my account? Why do you refresh? There is no need to. Well, the same thing happens if I close the browser and re-open. The account is then locked. Since forging requires the account to be unlocked, I'm trying to figure out how to keep it unlocked. If I close my browser and I don't re-open it, will my account remain unlocked? |
|
|
|
How is this:
23282 11299278613223005670 Mon Dec 23 14:20:11 2013
0 0 + 0 0 B
1 6026538789233531925 721693 % i think you need to reload the blockchain How can you tell? Current block is only 23264 OK but how do you know that? In other words, how can I tell whether I need to reload or not? |
|
|
|
|
Why does refreshing the browser lock my account?
After unlocking my account, if I refresh the page it comes back as locked. The wiki says it should remain unlocked until I explicitly lock it again. Does that only apply if I have a balance in my account?
|
|
|
|
How is this:
23282 11299278613223005670 Mon Dec 23 14:20:11 2013
0 0 + 0 0 B
1 6026538789233531925 721693 % i think you need to reload the blockchain How can you tell? |
|
|
|
|
How is this:
23282 11299278613223005670 Mon Dec 23 14:20:11 2013
0 0 + 0 0 B
1 6026538789233531925 721693 %
|
|
|
|
|
I can't reach nextcoin.org.
|
|
|
|
|
Are DGEX deposits and withdrawals working properly now? I'd like to buy some Nxt but I don't want anything to get stuck.
|
|
|
|
|
I saw so many more peers a few hours ago. Were they zombies from the attack which has died down?
|
|
|
|
Currently if u announce urself by putting IP into myAddress u say that anyone can connect to u. Ur IP is shared with other peers.
In nxt version if u connect to a peer then that peer will connect back to u, but it will NOT share ur IP with the others if myAddress is empty. I thought you said you were going to remove myAddress from the next release. Maybe I misunderstood. You are going to leave the myAddress parameter but change the behavior as you described above? |
|
|
|
If I understand correctly, this will make all nodes into public nodes as long as 7874/7875 are accessible from the internet? No. Nodes that u connect to will connect back, but they won't announce ur address to peers. I thought myAddress was the only thing that separated a private node from a public node. How is the private/public distinction made? |
|
|
|
I'm going to get rid of "myAddress", peers will try to connect back to each other to make Nxt network more symmetrical. If I understand correctly, this will make all nodes into public nodes as long as 7874/7875 are accessible from the internet? |
|
|
|
|
Are there separate client and server programs or is everyone running the same thing?
How can we monitor the distribution of Nxt amongst stakeholders?
|
|
|
|
See my sig first line, I updated the guide for hallmarked nodes. Thank you but the link you posted seems to go to unrelated info unless I'm missing something: https://bitcointalk.org/index.php?topic=345619.msg3863559;topicseen#msg3863559If you run a public node, anyone can access your node, unless you configure in web.xml only your, for example, home IP Doesn't running "allowedUserHosts *" allow anyone to change any node to their account number? I propose http authentication support for the nodes. |
|
|
|
|
Is there any way to monitor the health of Nxt's network? I'm curious how we're doing against the attack.
Since I haven't associated my node with an account, can't someone just point their browser to my node and do so themselves? Is there any protection against this?
|
|
|
|
ok i'll edit the guide to upgrade ram for hallmarked nodes I'd like to provide maximum benefit to the network. It sounds like running a hallmarked node falls into this category. What is hallmarking (I don't see it on the FAQ), how can I do it, and how much RAM should I have? |
|
|
|
|
Show Posts
