See if you can break my hiding algorithm –> take the private key | Hacker News Reader

See if you can break my hiding algorithm –> take the private key

redactsure.com

5 pointsredactsure19 comments

I have a new browser security method. Inside this link you'll have access to a virtual browser environment. In this environment you will have the ability to control and access a plain text private bitcoin key worth 20$. There is only a single key, first one to take it ends the challenge for all.

Demo Signup: https://app.redactsure.com/ Bitcoin Checker: https://redactsure.com/bitcoinchallenge/

Limitations: - 15mins per session (why? GPU per session, limited spots) - US only is preferred (why? latency, I am streaming video to you) - No mobile, keyboard required - Requires you to verify an email

Some people were asking about implementation I'll provide a few details. - A server hosted browser - I manipulate what you are seeing on the webpage in real time - While I don't change the underlying webpage I do manipulate your actions to the webpage - A full transformer model runs in real time along side you (tries to find all sensitive words you see)

Overall the systems goals are to allow you to perform work without ever seeing the data. It's in a early prototype stage and I expect a large numbers of edge cases just from the nature of the problem. The bitcoin is a proxy to the real goal which is protecting real PII in remote work settings.

Other notes: - It would be nice if you tell me the bug. I would like to post how you broke it. - I'll post updates as well as info on bugs sessions here: https://x.com/CharlesCurt2

The key Nextgrid pasted is correct, I got the coins under email kiknubesti@necub.com. I got the key by pasting into the text input line in the HTML input types demo and adding spaces after the text. The box blocking the view moved to the left and uncovered some characters. I then selected these characters and while dragging left, the key was revealed one by one, which I then OCRd from the screencap. Though at some point after it, typing spaces after the text wasn't possible anymore with an error message saying that editing is prohibited.

Nice! Thanks again. You're definitely making me fix all my laziness for sure. I honestly hopped that bug would only expose the tail ends but the select and drag is definitely not something I've tried before.

Up...again

got it. went to the html form example, pasted into the text box and then tried uploading a file. "Access to local files ..." text on the top of the page moved the whole page down, exposing the key.

Ahhh, this is fun. My own security policy working against me! back to top of the leaderboard for you!

sent you an email through the contact form :)

Back up if you want another go.

Is the "BitcoinKey" (Kzfyg6...4bUvKpD)? And if so, are you sure this is correct? Pasting this into Electrim's "sweep" feature does not appear to work and says no inputs were found.

I found the key as well, also used Electrum, and also was (seemingly) unable to do anything with it.

Turns out, you have to prefix the private key with "p2wpkh:", or else it imports it as a legacy key, and generates a completely different public hash.

What did you try to do? If you had the full key it should be relatively simple. Maybe I should post some instructions on claiming the key?

Launch Electrum, create a new wallet, "Import Bitcoin addresses or private keys", paste in the recovered key.

If you just paste the raw key, Electrum uses a legacy format, and none of the transactions show up for that private key. Adding the "p2wpkh:" prefix to the key makes the transactions show up, but I realized that well after someone else claimed it.

I don't know if this is an Electrum thing, if this is considered general knowledge now for those who regularly use BTC, or if it's a quirk of how BTC has evolved.

that was brutal! I knew you were holding out something. Oh man this is a brutal bug as well. That's an OS popup! That's gonna take me some time.

Actually even worse it's neither an OS level or dom level item custom chrome rendering layer.

That explains why the validator error looked entirely different when I tried to reproduce it locally -- I was wondering about that.

And yeah, it's a CTF, gotta hold onto issues until the flag redemption is back up.

bet you couldn't do it again. It's back up. Patch is a bit hacky but should work plus I blocked the signup page.

Real patch is a chromium update (like a week of work) so imma avoid that until needed.

back up if you want another chance

Got it :)

Pasted the private key into the email address field on the Wufoo signup page, and the validator helpfully told me my "email" was invalid, with the whole key included.

It is. You may have been just a little too late. It was claimed.

back up if you want another go -> again

Reply on news.ycombinator.com