Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Code: [Select]:~/bitsharesx# git checkout 0.4.15
error: pathspec '0.4.15' did not match any file(s) known to git.
Exactly. The command line client shows the tx's. The GUI client doesn't, even after running wallet_account_transaction_history in the gui's console.I tried rescan to recover the transactions in the gui, but nothing changed.i'd call it display bug ...
go to "console" and type "wallet_account_transaction_history" ... you'll see your transactions
Not sure how this helps.
If your computer is compromised, it won't matter how strong your password is or how you input it...
It definitely matters how you input the password. If my computer is compromised with a keylogger and the hacker gets my wallet file, he still won't be able to access it due to the wallet being secured with a strong password.
If someone can run a keylogger on your computer, he can certainly run anything else like software to capture images from the camera.
Anyway, he doesn't even need to do that. Once the wallet is in an unlocked state, he can just transfer any funds to his own account..
This isn't how hacking works. The hacker doesn't literally have complete control over your computer (in most all real world cases). The malicious code would likely:
a) Search for and send the wallet .json file.
b) Log keystrokes and send log every X days.
While it's technically possible to log video, it's nowhere near as common or easy to do.
All that aside though, using a QR code to log in would at the very least allow me to input a strong 100 character password in a user friendly way.
wouldnt it be like 2fa?
Nope, it's just letting the user input a password in a more secure way.
Could also do on-screen keyboard. All modern OS's have this, though I like the idea of some sort of non-typed input. Perhaps a third party add-on.
The problem with an on screen keyboard is I have to use a password I can hold in my memory and it can't be too difficult to type out.
QR code login:
a) Allows for LONG secure passwords
b) Keylogger resistant
c) User friendly (hold paper up to camera)
There's a chance that your webcam could be spied on as well, though, isn't there?
I use a password manager with copy-to-clipboard functionality. The password is never shown, and the clipboard is cleared after 10 seconds. Easy!
Not sure how this helps.
If your computer is compromised, it won't matter how strong your password is or how you input it...
It definitely matters how you input the password. If my computer is compromised with a keylogger and the hacker gets my wallet file, he still won't be able to access it due to the wallet being secured with a strong password.
I've sent $10 to reddit account moosapor for his 40 posts long support at reddit:
http://www.reddit.com/r/BitShares/comments/2g5092/linux_install_help_required/Code: [Select]2014-09-13T10:22:06 PENDING talktip.xeroc arubi 10.0000 USD reddit support 0.50000 BTSX 5c322425
Yeah, that was htdocs param in config. Works great now
Got it with a different ssh client for Win. But now localhost:9999 returns a blank page with "Invalid RPC Request" only. Any further suggestions?
You need to have your htdocs folder in the same folder as bitshares_client
{
"rpc": {
"enable": false,
"rpc_user": "rpc-username",
"rpc_password": "rpc-password",
"rpc_endpoint": "127.0.0.1:0",
"httpd_endpoint": "127.0.0.1:0",
"htdocs": "/home/<linux username>/bitsharesx/programs/web_wallet/generated"
},
....
me@remote:~$ ~/bitsharesx/programs/client/bitshares_client --server --httpport 9999me@local:~$ ssh <remote machine> -L 9999:127.0.0.1:9999 -NThen use your web browser to access localhost:9999wallet_open <wallet name>while on the remote machine, since there is no way to do this (that I know of) using the GUI, without first logging in.if i understand it correct you are asking if it is possible to claim the snapshot BTSX double or tripple times
i didn't tried it, but i expect with your transaction you once claimed the PTS snapshot BTSX and with the transaction "GENESIS -->your user" it is already included in the blockchain. So you can try to claim again with a other wallet but it is useless.
No, Im pretty sure you can import your PTS into multiple different BTSX Accounts, until the first time that stake actually gets moved.
This makes sense because if you look at your "GENESIS -->your user" transaction, it shows a transaction fee of 0 - because nothing was actually done/changed on the blockchain. Your wallet just added an extra key to its local file.
This is correct.
