|
|
|
em3rgentOrdr
|
 |
May 06, 2011, 10:54:46 PM |
|
I am downloading it. I am a little paranoid to run it since I don't know if will steal my coins or not. Could you provide me a link to the open source code so I can see what's going on under the hood?
|
"We will not find a solution to political problems in cryptography, but we can win a major battle in the arms race and gain a new territory of freedom for several years.
Governments are good at cutting off the heads of a centrally controlled networks, but pure P2P networks are holding their own."
|
|
|
|
Belkaar (OP)
|
|
May 07, 2011, 07:56:43 AM |
|
I am downloading it. I am a little paranoid to run it since I don't know if will steal my coins or not. Could you provide me a link to the open source code so I can see what's going on under the hood?
I created a project at sourceforge. Took a while, it was my first :-). Source code is all up there tho. https://sourceforge.net/projects/bitcoiner/If you want to help improving feel free to contact me |
|
|
|
|
kseistrup
|
|
May 07, 2011, 08:06:14 AM |
|
Cool.
One question, though: Does it use SSL for the RPC connection?
Cheers,
|
Klaus Alexander Seistrup
|
|
|
|
Belkaar (OP)
|
|
May 07, 2011, 08:13:25 AM |
|
Cool.
One question, though: Does it use SSL for the RPC connection?
Cheers,
If you use a https://... url it uses ssl, otherwise not. You need to install the certificate on the phone tho if its self signed. |
|
|
|
|
kseistrup
|
|
May 07, 2011, 08:29:13 AM |
|
If you use a https://... url it uses ssl, otherwise not.
Sweet!
You need to install the certificate on the phone tho if its self signed.
Any idea how I do that? Cheers, |
Klaus Alexander Seistrup
|
|
|
|
|
|
Belkaar (OP)
|
|
May 08, 2011, 06:11:17 PM |
|
Update to v0.91
Client allows untrusted certificates because installing certs on android is a pain. So more people can use SSL (https://... instead of http://)
Please consider a small donation (button in the send-mode) to cover the outrageous 25$ android market fee to publish even free apps :-).
Or alternatively: Some feedback would be nice. Always trying to improve.
|
|
|
|
|
Matt Corallo
|
|
May 08, 2011, 06:21:59 PM |
|
Update to v0.91
Client allows untrusted certificates because installing certs on android is a pain. So more people can use SSL (https://... instead of http://)
Could you cache ssl certs for known servers and/or warn the user if a certificate is untrusted? |
|
|
|
|
Belkaar (OP)
|
|
May 08, 2011, 06:29:32 PM |
|
Could you cache ssl certs for known servers and/or warn the user if a certificate is untrusted?
You mean like a message "This certificate is untrusted, trust anyway and never show this message for this certificate again"? |
|
|
|
|
Matt Corallo
|
|
May 08, 2011, 06:30:39 PM |
|
You mean like a message "This certificate is untrusted, trust anyway and never show this message for this certificate again"?
Yep, something like that. |
|
|
|
|
kseistrup
|
|
May 08, 2011, 06:58:55 PM |
|
Update to v0.91
Client allows untrusted certificates because installing certs on android is a pain. So more people can use SSL (https://... instead of http://)
That's very cool! I managed to import an SSL-certificate, but the previous version failed to connect over https anyway. Perhaps I did something else wrong… With the new version, however, I have to ring in the server's IP address — if I ring in a hostname Bitcoiner crashes (and I have to go to the system settings and clear any data associated with Bitcoiner to be able to enter an IP address instead). Is this the expected behaviour, or should I be able to use a hostname? Cheers, |
Klaus Alexander Seistrup
|
|
|
|
Belkaar (OP)
|
|
May 08, 2011, 07:49:02 PM |
|
Update to v0.92 Alert the user if SSL certificate changes. ---------- You should be able to use host names. I'm using ' https://somehost.dyndns.org:8332' as URL string and it works fine. |
|
|
|
|
kseistrup
|
|
May 08, 2011, 07:53:13 PM |
|
Thanks, I'll give it one more try… Update: it works with hostname, I don't know why it crahsed last time then. Cheers, |
Klaus Alexander Seistrup
|
|
|
SleepMachine
Member
 Offline
Activity: 118
Merit: 10
|
|
May 08, 2011, 08:02:27 PM |
|
Perhaps a noob question... but do i have to compile my own version of the official bitcoin client to get SSL support?
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
|
|
|
|
|
Belkaar (OP)
|
|
May 08, 2011, 08:48:42 PM |
|
Perhaps a noob question... but do i have to compile my own version of the official bitcoin client to get SSL support?
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
I guess its because bitcoin can't create a certificate itself. This " https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon) should get your started. |
|
|
|
SleepMachine
Member
Offline
Activity: 118
Merit: 10
|
|
May 08, 2011, 09:03:14 PM |
|
I did try to follow those instructions. After i've created my certificate and updated bitcoin.conf to use rpcssl=1 i am told to restart bitcoin.exe but then it chrashes with the "bitcoin not compiled with full openssl libraries" error. Could it have anything to do with this? http://bitcointalk.org/index.php?topic=1434.msg16585#msg16585or is that old post no longer relevant? |
|
|
|
|
Belkaar (OP)
|
|
May 08, 2011, 09:24:35 PM |
|
I did try to follow those instructions. After i've created my certificate and updated bitcoin.conf to use rpcssl=1 i am told to restart bitcoin.exe but then it chrashes with the "bitcoin not compiled with full openssl libraries" error. Could it have anything to do with this? http://bitcointalk.org/index.php?topic=1434.msg16585#msg16585or is that old post no longer relevant? I just tried it on windows and it seems like you'd have to compile it with ssl support. My node runs on linux and apparently it's already built in there. In the meantime you can try the app out inside your local network without SSL. |
|
|
|
SleepMachine
Member
Offline
Activity: 118
Merit: 10
|
|
May 08, 2011, 10:32:44 PM |
|
I figured as much. =/
Oh well, compiling bitcoin with SSL support is a project for another day... unless someone trusted already has the compiled binaries for this?
|
|
|
|
|
Belkaar (OP)
|
|
May 09, 2011, 04:40:09 PM |
|
Just an idea:
What would you think about a thin client that doesn't store the block chain, but only talks to one trusted node who does all the checking and verifying.
It would have it's own wallet.
It seems like no advantage over the existing RPC client, but you could choose to trust a node of a friend or a respected community member like the slush pool node.
So you would not necessarily need to set up your own internet-accessible node.
Any thoughts?
|
|
|
|
|
