I felt like sharing this info here because it matters to me more than pixel density or aspect ratio.
It turns out that GPUs like the popular Intel integrated gfx chips requires each lines of your framebuffer to be 64 bytes aligned. And yet, when using a 1366 wide resolution in 32bit per pixel mode, the visible length in bytes of a framebuffer is 5464, which is not a multiple of 64.
The operating system circumvent the problem by allocating 5504 bytes for each line of the framebuffer instead of 5464. It represent a loss of 30KB of unused memory.
Anyway, you're probably think I'm mad to care about those things instead of pixel density or aspect ratio, and 30KB is definitely meaningless compared to the memory footprint of a complete framebuffer (which is around 4-5MB). But you know these people who can't stand having the volume bar set to an odd number on their television set ? I'm exactly like them, why in hell would you not use an horizontal resolution which is not a multiple of 64 ?
It's currently running at 3200000 tries per second on my Xeon machine. I am probably going to get bored before I find the right combination because I calculated it could take up to 52 days. :)
But anyways, it is still a lot less time than trying to bruteforce something like Tr0ub4dor&3 in my opinion.
It seems you like challenges, if I gave you a SHA1 hash of something similar to "Tr0ub4dor&3", would you be able to crack it (without rainbow table) under 52 days ? I don't think so.
I find the idea incredibly stupid. If I know someone who used that precise generator to produce his password. Then I know that the generator has less than 2000 words in the dictionnary. It then takes me only a few minutes to guess his password, rather than 550 years.
Conclusion: Don't ever use this password generator, write you own, and tell no-one about it.
It turns out that GPUs like the popular Intel integrated gfx chips requires each lines of your framebuffer to be 64 bytes aligned. And yet, when using a 1366 wide resolution in 32bit per pixel mode, the visible length in bytes of a framebuffer is 5464, which is not a multiple of 64.
The operating system circumvent the problem by allocating 5504 bytes for each line of the framebuffer instead of 5464. It represent a loss of 30KB of unused memory.
Anyway, you're probably think I'm mad to care about those things instead of pixel density or aspect ratio, and 30KB is definitely meaningless compared to the memory footprint of a complete framebuffer (which is around 4-5MB). But you know these people who can't stand having the volume bar set to an odd number on their television set ? I'm exactly like them, why in hell would you not use an horizontal resolution which is not a multiple of 64 ?