Re: NVDA remote unsecurity prooven, recording of dev included
I'm not really sure why remote.ini is the problem... or even a problem. You're complaining that someone who has access to your computer can get your keys. Which is really how things generally go. Don't allow people access to your computer. If the client "hid" them, it's open source and people would just know where it is. This isn't STW where it's okay to scatter files through people's harddrives to check if they're banned. If it was encrypted, you'd have to have a password to launch NVDA remote or it would have to be a uniform key, which again would be stored... you guessed it, in the source. Or maybe we should encrypt the encrypted data, then store it on an 8-bit screen before embedding the payload file in the matrix.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
