You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Files are relevant for many security sceneraios and NTFS is often poorly understood. I recommend thinking up edge cases, what would happen if? Then test and see if it is exspected. Read about obscure edge cases- read disassebly , look at NTFS.sys
do your own tooling- that is how you learn. test ideas, try stuff, come up with hypothetical exploitable scenarios, see if you can find them. Make solutions for arb file create to code exec. read, test, try stupid stuff- sometimes you get surprised. Forget assumptions, verify
There is new exploit class I call "trusting what is learnt under impersonation"- when a service do actions based on things learned under impersonation- like read a .config file. If read under impersonation and instructs it to load a dll- it is exploitable. You can find those
"Forget assumptions, verify" is very good advice for anyone who goes into infosec thinking implementations (even by multinational billion dollar corporations) are competent.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
