Re: NVDA remote unsecurity prooven, recording of dev included
Ok, there are a fiew things that need to get streightened out here, huge points that people sceme to not propperly understand in this situation. First one, this twitter key posting. Yes, ivan posted to twitter to connect to key 123. That was ivan. I didn't post that on twitter. You guys shouldn't get mad because anyone connected to it. We just followed a twitter tweat. After ivan disconnected, a VM of tylers connects and tells us that hacking can ruin peoples lives, he was defenatly against fucking up ivan. Then he crashes all the clients. So... Ivan posted the key and got his computer fucked up, but not the rest of us. And? If it was someone else that did this, then it could be a bug reported to the remote devs and done. But no, this was the dev him self connected to his own nvdaremote.com server, though the server doesn't matter. And everyone was connected as control another machine, not allow this amchine to be controled. So the only just reason for you guys talk ing about us connecting to a key posted publicly is that tyler was made aware of the key.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
