deleted---
deleted---
Last edited by Omni; 3rd December 2018 at 16:42.
alh02 (24th August 2015), Aspen (1st September 2015), Aurelius (23rd August 2015), avid (23rd August 2015), Baby Steps (23rd August 2015), Betty (23rd August 2015), Bill Ryan (23rd August 2015), BMJ (24th January 2018), bojancan (23rd August 2015), Calz (23rd August 2015), Cardillac (23rd August 2015), DaRkViPeR (23rd August 2015), Daughter of Time (23rd August 2015), Deega (23rd August 2015), DNA (23rd August 2015), earthadvocate (23rd August 2015), Elisheva (23rd August 2015), Frenchy (23rd August 2015), gaiagirl (17th December 2017), Gardener (23rd August 2015), genevieve (23rd August 2015), Hervé (23rd August 2015), Jhonie (23rd August 2015), johnh (23rd August 2015), Joseph McAree (23rd August 2015), justntime2learn (26th August 2015), Karezza (23rd August 2015), KiwiElf (23rd August 2015), mab777 (1st September 2015), Matisse (24th August 2015), Melinda (23rd August 2015), Michelle Marie (1st September 2015), mosquito (24th August 2015), Nasu (31st August 2015), Nat_Lee (1st September 2015), Operator (23rd August 2015), Orph (23rd August 2015), ponda (24th August 2015), PRAGMAE (23rd August 2015), Raven (14th November 2016), Rhah (23rd August 2015), Rita Sweeney (23rd August 2015), RunningDeer (23rd August 2015), Selkie (23rd August 2015), shadowstalker (5th October 2016), Shannon (27th August 2015), Sierra (23rd August 2015), Sophocles (23rd August 2015), SR19 (23rd August 2015), T Smith (2nd September 2015), Terra (23rd August 2015), toppy (23rd August 2015), TrumanCash (24th August 2015), WhiteLove (23rd August 2015), yelik (25th August 2015)
Omniverse, thanks for this! Anyone here know any YouTube video demonstrating the keylogger data being sent over the network? That would be an incredible YouTube video that I'm sure would generate millions of views...! But it's probably sent encrypted in kernel mode so you can't even easily tap into that stream of data eventhough you have "full" access to the machine (and who knows maybe someone else has more access), pretty scary stuff...
Found this:
Please note, the guy in the video above does not know anything, he has no clue (all he did was to copy a few lines of code from a forum and added his own personal ideas/opinions to it), these things you must confirm by capturing the raw data being logged. The entire possible scope of key logging must be captured since the privacy agreement does not state what the scope of the keylogging is and what processes go into that scope. Now, that information might be out there somewhere, but so far I have not seen it. The only real way you can find out this is by monitoring all data being sent from any network adapter from a computer with W 10 installed, decrypt possible encryptions and then find out exactly what is being sent, how and when. And that requires tons of expertise. If this feature has the origin it seems to have, you can bet that it's not going to be easy to find and turn it off, in fact I think it might not even be possible to turn it off without kernel level access which users or administrators don't have.
There is another issue here as well, which is that the way the data is being collected does not necessarily need to be done through a keylogger. Those characters could be collected at the system level by the system at the receiving end, if the system did not have access to the raw data being received from the user, it could not read it. So the way the data is being collected is important relative to what is stated in the privacy agreement. Every time a new OS is being made, the owners of the OS can decide what access, how the access is distributed and why, in regards to their own access and the normal user/administrator access. How the data is synced up to the cloud might for instance be during wake up/shutdown when the memory is recalled/released, it could be buffered so that chunks of data portions at a time are sent so that users cannot notice anything.
Also, if they don't state how this works, its scope and how you turn it off, then that is an indicator that access to the whats, hows and whys about this are denied to the public.
In general, this is bad news.
I think the real question here is: Can one find the data being logged and sent and prove it. And I bet one can't unless you are a highly skilled security specialist/researcher having inside information about how the OS was built and know how and where to look for it, how it has been embedded/encrypted... The implications of not being able to find the data stream containing the keys being logged, yet at the same time having agreed to allow the keys being logged, those are enormous!
I would like to know what encryption is trusted so much that this is done. I mean it's one thing to want access to all of the users data and get that, it's a different thing if it leaves the system vulnerable to third parties picking up the same data. Just the existence of something like this in an OS appears to make that system unsecure. So the scenario here could be that the whats, hows, and whys about all of this might be unaccessible for "those" security reasons. This in turn leaves normal users with nothing left but a choice that needs to be made.
Last edited by WhiteLove; 23rd August 2015 at 10:44.
Aspen (1st September 2015), Baby Steps (23rd August 2015), Bill Ryan (23rd August 2015), Calz (23rd August 2015), Daughter of Time (23rd August 2015), exponentialist (5th August 2016), Frenchy (23rd August 2015), Hervé (23rd August 2015), justntime2learn (26th August 2015), KiwiElf (23rd August 2015), Nasu (31st August 2015), Omni (23rd August 2015), Operator (23rd August 2015), Orph (23rd August 2015), Rhah (23rd August 2015), Rita Sweeney (23rd August 2015), Selkie (23rd August 2015), Sierra (23rd August 2015)