Skip to main content
ken Code's user avatar
ken Code's user avatar
ken Code's user avatar
ken Code
  • Member for 10 years, 2 months
  • Last seen more than 7 years ago
Loading…
awarded
comment
Preventing the exposure of public addresses on a website
no. private keys bitaddress/bulkwallet) must be stored locally, the public addresses can be stored in mongodb on the server, hidden from google etc. we built a website for an old man that runs a novelty shop, he doesn't know doodly about tech so this has got to be dumbed down automated for him, yet as anon as possible.
awarded
comment
Preventing the exposure of public addresses on a website
google can read svg files, even raw text on a pdf, but i do not see google reading the text that is drawn onto an image as of yet. (ie: captchas) i just can't think of an easier way to show the public key. maybe skip showing the text of the key altogether and just show qr codes from now on? that might make the customer on the website a bit suspicious tho, not sure if they are sending money to the correct address. i personally read the first 5 or 6 chars myself just to make sure it matches what my wallet is about to send btc to. so, how do we hide that key text from google et al? ideas?
comment
Preventing the exposure of public addresses on a website
I disagree. Displaying the public key as an image in a compiled jpeg would be more secure than displaying it as raw copy-able clear plain text on the page. Most people will just scan the qr code before they will copy/paste a key...
comment
Preventing the exposure of public addresses on a website
bitcoinaddress.js also displays everything on the page in plain text, not good. see my question above for why etc thanx :)
comment
Preventing the exposure of public addresses on a website
I hate captcha's, so does everyone else, so that's out. Using an Exchange is also no longer an option. Form method=post sounds like the only option then for hiding the key? So, what library do we use then for what I am trying to accomplish..
Loading…