oh... are you mpalmer on github ? yeah, I see that there are some still open PRs, I think atom/jsteube is busy a lot, but I will try to ping him on IRC etc. normally it doesn't take that long (I think one reason could be that we/he saw that some PRs were still incomplete or were updated a lot... so might have decided to wait a little bit etc)...
Actually, what comes to my mind now is that it would be great to find some "collision" (or just another password that would work) and try to decrypt the file with that "wrong" password.... would this be feasible for you to test... it might take some time to find a collision, but you could be lucky. It would be interesting to see if the software is able to reject the collision (wrong password, but still correct "checksum"/quick check)
I think/hope there is some other means to validate the data... but again, you could also be right and this is the only test.
Thx
Actually, what comes to my mind now is that it would be great to find some "collision" (or just another password that would work) and try to decrypt the file with that "wrong" password.... would this be feasible for you to test... it might take some time to find a collision, but you could be lucky. It would be interesting to see if the software is able to reject the collision (wrong password, but still correct "checksum"/quick check)
I think/hope there is some other means to validate the data... but again, you could also be right and this is the only test.
Thx