5
Communicating through 127.0.0.1 can be thought of as just another IPC mechanism, but one that re-uses existing protocols. Just like shared memory or UNIX domain sockets or pipes, it's one of countless ways that two processes can communicate on a single system. If you trust that the processes on your system have not been compromised, then you can "blindly" ...
4
If you know that the IP address at the other end of a TCP socket is 127.0.0.1, this guarantees that either the system administrator has configured the firewall to redirect this particular connection, or the other end of the TCP socket is a process running on the same machine. So if you trust your server machine as a whole, you can trust 127.0.0.1. However, ...
3
This simply means that dwcore application which is listening on port 8080 and 8443 are vulnerable to path traversal. Without the knowledge of what that application is, an accurate answer cannot be provided for this.
Having said that, if the application running on those two ports are not used, you can kill those services or add an iptable rule to restrict ...
2
Google suspicious activity warning persists for 4 days despite my confirming I recognize it
This behavior is intentional. If an attacker had gained access to your account, allowing the warning to be dismissed would allow the attacker to dismiss the warning before you were able to see it.
2
I will try my best:
There is a chance that this firebase server is having other services available aswell on the system, that's why many ports show up.
This is output from a script which tries to guess under which username was the service ran.
For 3-5 please refer to NMAP manual.
NMAP by default uses few tricks to determine what remote operating system ...
1
I'll go through the points you have mentioned, and will add some extra points below as well
WEP? WPA? WPA2?
All of these schemes have flaws, but some more than others. The current best practice is to use WPA2-Enterprise with client certificates for each individual device. This way, even a rogue device will be unable to sniff traffic of other devices.
Of ...
1
Encrypt with WPA-2 with AES: Make sure the router you get has that capability. Most do, since WPA-2 has been around a while.
Hide your network name: A setting in the wireless router. Hide "SSID" or similar. Also, most wireless router will have this. Users will have to manually input the SSID however.
Turn off UPnP (is this easy to do?): Yes. Another setting ...
1
QUESTION: Does this behavior indicate that there is a further security issue that I'm unaware of? What would happen if I instead clicked Change reply? Right now I have two-factor turned off so I'm very concerned about getting locked out. Are there any further problems that I could look for somehow?
That your google account notes suspicious traffic from your ...
1
Fortigate devices, yours will support this, can do Web Content filtering, and site analysis.
https://help.fortinet.com/fos60hlp/60/Content/FortiOS/fortigate-security-profiles/Web_Filter/web_filter_chapter.htm?Highlight=web%20filtering
You can setup firewall rules based on user identities (either by sign-in page or RADIUS to your DC) that rate limit users, ...
1
If the port is connected to the network switch, and the network serves up DCHP, then the laptop will get an IP address and gateway, and will likely be able to gain access to the network. NMap could then be used to map out the network.
To help protect against this, the customer can either move to static IPs, use MAC address filtering, and/or find a firewall ...
1
This is quite an old thread but I feel still relevant especially for new comers like myself who are starting out learning to crack WEP.
I have exactly the same problem and I am using a similar wifi card (AWUS036NHA).
Until I get another manufacturer such as Panda I won't know if this is a problem with the ALFA cards.
NB: If the target AP has a an active ...
Only top voted, non community-wiki answers of a minimum length are eligible
