sorry I am very annoyed tonight
and look I'm not saying Jeremy Paxman is some sort of god of journalism but the dude stood his ground and treated the most politically powerful people in the country like children when they wouldn't answer a question, in a country with a culture that is typified by the concept that vaguely inconveniencing another person is utterly verboten, and rather than him losing all access he instead became so iconic that politicians had no choice but to be interviewed by him. that shit worked.
and if they storm off like a petulant child then you've got one hell of a story anyway.
sorry I am very annoyed tonight
go Jeremy Paxman on their asses. don't give them an inch, don't let them bluster past a question with a non-answer. keep asking the same damn question until they give a straight fucking response.
and if they storm off like a petulant child then you've got one hell of a story anyway.
remember when journalism held people to account for being lying-ass motherfuckers? man I am tired of sycophantic techbro press release regurgitation.
go Jeremy Paxman on their asses. don't give them an inch, don't let them bluster past a question with a non-answer. keep asking the same damn question until they give a straight fucking response.
remember when journalism held people to account for being lying-ass motherfuckers? man I am tired of sycophantic techbro press release regurgitation.
me, begging: "you can't keep calling anything where there's a lack of something a hole"
semiconductor engineer, pointing to a kitchen surface with nothing on it: "hole"
can anyone recall any interesting vulnerabilities in Windows applications that were due to mishandling of character encoding and/or unexpected case sensitivity in file paths? ones with good write-ups strongly preferred.
looking specifically for Windows, specifically character encoding related bugs, and specifically bugs in apps rather than bugs in the OS's own file path handling (e.g. WorstFit)
#infosec
I am not looking for bugs relating to the handling of file contents.
I'm thinking more along the lines of assuming that file paths are always just ASCII strings, and then getting bitten by UTF-16 path names. or weird cases where two files with the same name but different case exist (e.g. due to FILE_FLAG_POSIX_SEMANTICS) leading to a security issue in an application.
I'm not looking for OS-level bugs like WorstFit.
this evening's recreational coding involves a class called FireworkSequenceControllerFactory.
can anyone recall any interesting vulnerabilities in Windows applications that were due to mishandling of character encoding and/or unexpected case sensitivity in file paths? ones with good write-ups strongly preferred.
looking specifically for Windows, specifically character encoding related bugs, and specifically bugs in apps rather than bugs in the OS's own file path handling (e.g. WorstFit)
#infosec
jfc, apparently some beauty places are now offering "RF microneedling", which is regular microneedling except they emit RF energy from the needle head to promote waves hands whateverthefuck-growth.
saw some photos, people are getting deep tissue RF burns. horrifying.
(microneedling itself is mostly fine, from what I can tell, if done right. but this RF variant is insane)
Graham Sutherland / Polynomial