Tag Info

New answers tagged

0

It looks likely that they have used the fact your're on a local wifi network to intercept your session traffic and capture the content. There are a number of simple to use tools that can enable this type of attack in gaining your sessions. Another vector is if they have created a MITM WIFI access point masquerading as a legitimate access point to capture ...


0

There are a few possibilities how he did it: You and him were connected to the same WiFi network and he used a software like Dsploit that allows him to intercept the traffic and performing man in the middle attack - solution to that is use VPN software that will encrypt the connection. More advanced attack. He forced your mobile device by using Karma and ...


2

HTTP is an inherently "trusting" protocol: it contains little or no built-in security. This means that it is susceptible to the following: Traffic monitoring Anything transmitted over HTTP can be intercepted and read by anyone connected to any network sitting between the source device and the target server. Traffic redirection and manipulation With little ...


0

In addition to what some of the answerers pointed out, most secure sites (e.g. banking web site, etc.), will not even allow you to access secure content through their sites via http. So, using http is not even an option with these sites - you have to use https.


1

Apart from the technological hurdles of getting a tap on the intercontinental lines that could actually read the data, the scenario you provided is indeed possible. If you use HTTP instead of HTTPS your data is travelling as clear text from end-to-end, so your ISP, anyone inbetween and the ISP of your destination host can read or even modify your data if ...


0

You can sniff HTTP Packets using Tools like Wireshark and its like a walk in the park to read your data Packets.An attacker can Intercept your Data Packets modify it and forward it. eg:You ask your bank to pay you - Attacker modify this packet and ask the Bank to Pay Him. I dont understand what you mean by HTTP in your WIFI Network.Dont you want to access ...


2

The reason you're getting this is because you load certain resources over HTTP. When you look at the page source code, you'll see this: <link rel='stylesheet' id='google-font-body-css' href='http://fonts.googleapis.com/css?family=Open+Sans+Condensed&#038;ver=4.1.1' type='text/css' media='all' /> <link rel='stylesheet' ...


1

This sounds like a component of a broader targeted attack involving spear phishing. You might send a link to the victim for Banking.Example.com and begin your DNS reply spam for that domain. That way, you know which domain they are trying to resolve with DNS.


1

As per this StackExchange answer, you can find it using lsof by looking for st=07 on a raw socket: # lsof -n | grep -i st=07 ping 19241 gowenfawr 3u raw 0t0 477269 00000000:0001->00000000:0000 st=07 # ps aux | grep 1924[1] gowenfawr 19241 0.0 0.0 8596 832 pts/0 S+ 07:26 0:00 ping ...



Top 50 recent answers are included