it shouldn't matter if there is or isn't txt at the end. and i changed that number is 1 character as well.
and that hash has been solved by others, so it works

1. you get length of password from a filename of the file
2. uppercase can be anywhere

1. The rar-file tells you how many characters there are in the password. 6a1A.rar would be 7 characters long (6 lowercase and 1 uppercase).

2. I hope it's always at the start, or I'm going to have to rethink a lot of my rulesets for cracking those otherwise =) I'm on a 6a1A at the moment. If the uppercase character can be on any position, it will take 6 times longer on an already several day long bruteforcing.

Edit: Oh damn, ozo just replied before me. That creates a lot of problems.

gonna add something like that - only by requesting new you will have to give up one "success" :D > meaning that if a minimum to be eligible is 5, with a request minimum for you will be 6 for one request, 7 for two, etc... :D
only as the assign is random, you may end up with same hash afterwards :D

In each town it has to be some asshole T_T. Sorry to hear that, mate.

Will progress be reset then? Just so I know if I should keep trying to bruteforce the one I'm on, or just wait for the update to start fresh with new hashes.

been solved 5 times

One of the easier ones to bruteforce if nothing else. Only 6 letters. :) I'm one of those that solved it.

restart wont happen, add me and tell me your ip. i blocked only few, like 3 or 4 ips that have visibly more tries to register

if you haven't posted any solves yet, i can just delete you and register again for new key

who decrypts most

if you did solve any password than i would suggest to wait a bit. if you didnt solve any yet, i can just delete you and you register again for new key

i removed fake ones

site still has old version, and that number represents top 5 instead of top 10

didn't really understand what you're asking

6a1A_3 - 11 solvers
6a1A - 9 solvers

So there are FOUR 6a1A types currently.
I have found:
6a1A.rar
6a1A_1.rar
6a1A_2.rar
6a1A_3.rar

All of which have been solved by me except 6a1A_3.rar :(
So yes there are a bunch of us stuck on that one.

The site gave me 6a1A_3.rar as my third hash and have not been able to pass it, even though I have solved a bunch of others.
Edit found.

Ran another "educated" brute force attempt with my computer last night, trying over 150 million passwords.. still haven't found it :-(

May I suggest adding a "Get next hash" type of button on the Home tab which gives out the hashes? Perhaps add a timer (1h, 8h, 24h, ?) to prevent people from grabbing a bunch of hashes at once if that is a concern of yours.

Really anything that allows solvers to still move forward if they get stuck on a particular hash would be awesome.

Well here's a bit more advanced version of "get next hash button".
Why not mix it together with a slot system that's similar to SteamGifts?

See the picture of how it could work

The picture assumes that there are 10 hashes in total. [The hashes could be shuffled once in a specific order, so it wouldn't be random for everyone]
Player starts with a one hash slot. By solving the slot he gets a new set of slots. If all of the hashes in a slot set are solved then the player gets +1 hash slot for the next slot set.
If a player can't solve a hash then he can "cancel" it (it gets moved to the very end of the hash shuffle). Doing so, the player gets -1 hash slot for each "canceled" hash in the next slot set.
If the player has been "canceling" till he's back to only one hash slot, then he has to wait a certain time to "cancel" the current hash and move on to the next one.

The currently solved hashes for each player could be just skipped from the initial shuffle.

I think that by doing it this way, it would ensure that players with somewhat good wordlists don't get completely stopped in their tracks if there's a hash that they can't solve in a reasonable amount of time. And the people who "cancel" too much would be forced to wait out a certain period of time, maybe forcing them to improve their wordlists.

View attached image.

Similar to Amrahds suggestion, but maybe easier to implement.
Give the user x (5/10) unsolved (by that user) random hashes at all time:except the user has less as n remaining OFC.

edit: Something like (for mysql)
SELECT hash from hashes, user_solved AS s WHERE s.userid=?user? AND s.solved=false AND hash_id = s.hash_id ORDER BY RAND() LIMIT 5;
Sry its a long time since i wrote mysql the last time
mysql select random rows

I think you could give out all passwords, but that would change the system to use A LOT... a lot more planing about what to do next etc... My preferred solution would be to give out a random and allow us to abandon it after a while, i like the 8-24h part. I don't feel that this is "too few" cause the plan is not to get ALL right and you should only abandon after trying a lot of stuff... But I would not punish people for doing it, the "wasted time" should be punishment enough.

Giving out a few like Amrahd supposed sounds acceptable as well... Giving out all changes too much how this works, in my opinion. You suddenly would have to do a lot more planing of what hashes to do when etc...

Considering we are given a lot of time I'd vote for a simpler solution - a timer. After getting a new hash if not solved within 12 hours you'll get a button "request a new hash" and so on.

Arghh so close, I am at 16/17. What is your cracking speed?

Solved as well!

update coming soon, just wait. i won't add new hashes before update, unfortunetly

in current passwords only in the end. when updated will be added, then anywhere