lainlives 1027fed668 Initial il y a 3 mois
..
FunnyApp.aps 1027fed668 Initial il y a 3 mois
FunnyApp.cpp 1027fed668 Initial il y a 3 mois
FunnyApp.rc 1027fed668 Initial il y a 3 mois
FunnyApp.sln 1027fed668 Initial il y a 3 mois
FunnyApp.vcxproj 1027fed668 Initial il y a 3 mois
FunnyApp.vcxproj.filters 1027fed668 Initial il y a 3 mois
FunnyApp.vcxproj.user 1027fed668 Initial il y a 3 mois
LICENSE 1027fed668 Initial il y a 3 mois
README.md 1027fed668 Initial il y a 3 mois
offreg.h 1027fed668 Initial il y a 3 mois
offreg.lib 1027fed668 Initial il y a 3 mois
resource.h 1027fed668 Initial il y a 3 mois
windefend.idl 1027fed668 Initial il y a 3 mois
windefend_c.c 1027fed668 Initial il y a 3 mois
windefend_h.h 1027fed668 Initial il y a 3 mois
windefend_s.c 1027fed668 Initial il y a 3 mois

README.md

BlueHammer

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

Repository hosting the bluehammer vulnerability

I'm just really wondering what was the math behind their decision, like you knew this was going to happen and you still did whatever you did ? Are they serious ?

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCac8VlgAKCRDFFoRCS0/S bK8pAP9CzNnH26FVVdHZWVyDvOIwuZ1np1dTv7T5YaVCjf4tiwD+MC4Ikq+/ywdD I7dabkH7iSZflULM+hGUOur0mnAg9Qw= =Enhh -----END PGP SIGNATURE-----

Edit : There are few bugs in the PoC that could prevent it from working, might fix them later.