J.TrIDr3ESpPJEs ID: ee4cfa July 31, 2018, 3:57 p.m. No.2377313   🗄️.is 🔗kun   >>7440 >>7671

>>2376809

>don't forget single and double quotes

 

Assuming the password accepts unicode, you may have a much bigger fight ahead of you. Consider other symbols like the pound sign (£) or the euro found on keyboards from other countries.

 

If it's unicode, you can safely assume UTF-8, given it's a pretty widespread standard.

 

Also, I recommend avoiding random character generators, but having a pre-computed array/table (for 3 characters).

 

If you're looking at additional bruteforcing power, a couple of recommendations:

1) Each of you should pick one picture each and specify what image you are trying to decode, and how. That way you're not duplicating each other's work.

 

2) If failed, specify what you tried and the 'results', if any.

 

For bringing hardware resources to bear:

 

1) Consider modded PS3s (some of you might have one or two lurking around), they're ideal for bruteforcing

2) Trial periods on cloud hosting repurposed (or alternately rent out some rackspace)

3) Dust off some old laptops, machines, and set them to work continuously whilst you do other things

4) Get some programmerfags to rewrite the testing code in bare metal (like C++) which would see mild performance improvements

 

Alternatively, if exhausting the three character space is too much, assign each of yourselves a single first character, and brute force all characters under that character.

 

So if one of you was to do 'A' (A), the next person would do 'B' (B).

 

Brute forcing isn't just about power but also efficient allocation of resources.

 

PS, Bitcoin's algorithm is SHA256. So if you're looking to break SHA256, look no further than your own noses. ; )

J.TrIDr3ESpPJEs ID: ee4cfa Aug. 1, 2018, 5:56 p.m. No.2401525   🗄️.is 🔗kun   >>2218

I had posted to this thread, but my post appears to have mysteriously (?) gone missing.

 

I mentioned to factor in symbols from international keyboards (£, euro sign), dusting off old hardware to assist in brute-forcing, and divying up tasks between yourselves (and let each other know) so you're not all trying to brute force the same issue.

 

It's curious my suggestions on ways to improve the efficiency of detecting PixelKnot 'magically disappeared', given no other post I've written so far has.

I had posted to this thread, but my ID: ee4cfa Aug. 1, 2018, 5:58 p.m. No.2401556   🗄️.is 🔗kun   >>2218

Oh yeah, don't forget to factor in unicode (if the password supports it and isn't just ASCII). Most format common is UTF-8 (non-BOM), and would exponentially increase the number of characters you'd need to check before solving.

 

But I digress.