Samsung Devices Appear to Communicate Via Mains Wiring

I have a Samsung A6 that has developed a fault that means it will only intermittently charge whilst it is turned off (the charging symbol comes on for a few seconds, then turns of for a few seconds, repeats … charging is very slow so it appears to be charging in increments).
I also have a Samsung S9. It hadn’t been turned on for over a year and its charge was completely depleted.

The A6 was already charging, and its charging symbol was turning on and off as per usual. When i plugged the S9 into the same multisocket extension, the A6 immediately showed it’s charging symbol continuously for over 30s, until the S9 showed it’s 0% charging screen (a different screen to the simple charging symbol).

I unplugged the S9 and depleted the charge to retest it, and the same thing happened.

Just out of interest, I also tested the following configuration…

S9 – MULTIPLUG – USBPortableCharger – A6

and the A6 still lit up when i plugged the depleted S9 in.

Why am I posting this in security.stackexchange?!

Is it normal that two devices from the same manufacturer are somehow aware that they are both plugged into the same electricity supply, even if it is ‘by accident’? By devices, I am mean the phones and the chargers.

Go to Source
Author: 3-14159265358979323846264

what is an example of out of bounds read in order to leak sensitive information?

I Am trying to understand a little bit better behind the scenes on bypassing aslr by reading the bytes in the memory of a process, but how can I make an example of an info leak in WIN32? my code does the leaks of bytes , but how can I check the image base based on those bytes?

#include <stdio.h>
#include <string.h>

int main(int argc, char **argv) {
    char a[16];

    strncpy(a, "0123456789abcdef", sizeof(a));

    //... lots of code passes, functions are called...
    //... we finally come back to array a ...

    printf("%sn", a);

Go to Source
Author: pepe