I am running various nmap scripts against my servers and the http-enum often flags directories like
/css/
/error/
/images/
/js/
/xml/
If I try to navigate to the IP + folder my browser times out. Yet somehow nmap is reaching these folders.
How can I resolve these issues so the folders are truly protected/nmap no longer shows them in the scan?
Related
In other words : is it some kind of containerization/ VM technology or it's just my computer doing the whole thing ? and where's the downloaded data stored ?
Things I tried :
Code here , uncomment and use node index.js to run
1- Checking system info using systeminformation gives: (obviously not my specs)
manufacturer: 'Intel',
brand: 'Core™ i9-9880H',
other information weren't very useful at least for my level of experience .
2- Testing network interfaces
iface: 'en0',
ifaceName: 'en0',
default: false,
ip4: '192.168.1.104',
I checked my host's local ip using ifconfig , not the same.
3- Checking external ip / Network speed
Wasn't able to do that , I guess only connections to npm server are allowed for downloading packages , fetching other webpages or connecting to speed-test servers isn't working .
So far it seemed like it's not My computer BUT then I tried running npm i largest-package and directly cut my PC's connectivity (the command should continue running on the server and I should find the package installed when I reconnect) this ,however , did not happen .
As for the Data
I checked the cached data in browser.. very small (in my humble opinion)
Finally
Checking the documentation
yields (09/03/2022) link
I'd appreciate you helping me wrap my head around this .
Up until a day ago I was perfectly able to mount a drive via sshfs with the follow_symlinks option given.
In fact I set up an alias for this command and used it for several weeks.
Since yesterday, using the same alias the volume still mounts correctly but the all the soft symlinks within that volume are broken.
Logging in using a regular ssh session confirms the symlinks actually are functioning.
Are there any configuration files that may interfere with what I try to do?
I was modifying /etc/ssh/ssh_config and /etc/hosts because I experienced severe login delays when starting an ssh session from a friend's place. But I reverted any changes later on.
Could a wrong configuration in these files cause my issue?
Btw. I'm using Ubuntu 16.04
It turns out that the permissions on the particular machine I was trying to mount the folder from changed over the weekend.
It is now only allowing access to certain folders from within the same network. That is why my soft-links (pointing to now permission restricted content) seemed broken when mounting from my home network.
Is there a way to skip a host while it is being scanned. I am providing a list of hosts to nmap and while it is scanning from that list, I would like to skip one host because the scripts keep running on that host hence delaying my scan. Please suggest.
Thanks
There is not a way during runtime to stop scanning a host. However, you can impose time limits on how long Nmap spends on a particular host. The --host-timeout option will cause Nmap to drop all results and stop scanning a target when the timeout expires. Unfortunately, this means all that work is lost. But there is a better way, if NSE scripts are slowing you down.
Nmap 7.30 added the --script-timeout option, which puts a time limit on each NSE script that runs against a target. Any script that exceeds the time limit will be terminated and will produce no output, but any other scripts will be allowed to run. No port scan, OS detection, or traceroute data will be lost.
Your last option if NSE is taking too long is to find out which script is causing the problem. Most NSE scripts are designed to run quickly; even most of the brute-force password guessing scripts enforce a 10-minute time limit. But sometimes there are bugs, and other times you may select a script with an intentionally long run time. In debug mode (-d or press d during runtime), printing a status line (by pressing any key during execution) will show a list of running scripts when there are 5 or fewer running. At debug level 2 (-dd or press d twice), a full stack trace of each running script thread is produced, which can help Nmap developers debug delays. If you suspect a misbehaving script, you can file a bug report on Github or send it to dev#nmap.org.
nmap has a host timeout option which will give up on any host that takes longer than the provided value. So, the below option would give up on any host that takes longer than 10 minutes. You can read more about the various timing related options here.
nmap --host-timeout 10m
Yesterday, I :q'd Vim to try Emacs for a while. I've started using Elisp (which is a hundred times better than VimScript), but even when I first installed it (via yum), and had changed nothing, it took about 30 seconds to start, and still does (both GUI and -nw).
I checked the *Messages* buffer:
Loading /usr/share/emacs/site-lisp/site-start.d/desktop-entry-mode-init.el (source)...done
Loading /usr/share/emacs/site-lisp/site-start.d/rpmdev-init.el (source)...done
The files seem to be specific to the RPM package I installed. I tried changing their names, yet there was no difference. It still takes 30 seconds.
I've solved it partially by never exiting emacs (I only suspend it) and trying to do everything in it, but it would be nice to occasionally open two Emacs's, especially since I have a tendency to use my terminal emulator's split function rather than something like tmux.
I realized that Emacs would load slower than Vim, but this seems ridiculous for a fresh install. Has anybody got any idea what's going on?
Thanks!
Emacs's PROBLEM file says:
*** Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
This can happen if the system is misconfigured and Emacs can't get the
full qualified domain name, FQDN. You should have your FQDN in the
/etc/hosts file, something like this:
127.0.0.1 localhost
129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04
The way to set this up may vary on non-GNU systems.
This "slow startup" typically comes from a timeout, and 30s sounds about right.
As a side note: the DNS lookup that causes this slow down was considered important/useful back in the days where (almost) all machines had a static IP address. Nowadays the info gathered this way does not justify the effort, so starting with Emacs-25, Emacs does not perform this DNS lookup, so this problem should simply not exist any more.
Okay, I have a (quirky and temporary) solution. I have to run dhclient em1 to access the internet, which makes Emacs take 30 seconds to load, probably because of some timeout. So, having already run dhclient em1, I use a shell script to launch Emacs that does the following:
sudo pkill dhclient
sudo ifconfig em1 down
emacs -nw -daemon 2> /dev/null
sudo ifconfig em1 up
sudo dhclient em1
That disables networking, launches Emacs as a daemon, and re-enables networking. It's ugly, but it works for now. If anybody else has a better answer, I'd be happy to hear it. Of course, em1 would have to be replaced by your Ethernet device (probably eth0, I guess).
I had a smilar problem with emacs taking about 15 seconds for startup. In my case the reason was a DNS timeout. For some reason, with my dormitory DNS, a failed reverse lookup (host 127.0.0.1) takes about 10 seconds. Replacing the DNS server by the google nameserver (8.8.8.8) produces an almost instant "not found: 3(NXDOMAIN)" response. At the same time, emacs's startup time went down to less than 2 seconds. Thanks #Stefan who pointed me into the direction of DNS problems.
Edit: adding the google nameserver as additional NS in Network Manager also does the job. (i.e. when your resolv.conf has the NSs in this order:
nameserver a.b.c.d
nameserver 8.8.8.8
)
I am trying to run the following command against my TFS 2008 server:
TF history /server:MyTFSServer /recursive “$/MyTFSProject/Folder”
When I run I get this:
Ignoring the /server option
It then complains about workspace. The workspace part I get (it is trying to use my current folder to establish the TFS Server. Where I am running from is not mapped so it can't connect. For my needs going tot he right folder will not help.)
But WHY WHY WHY does it not like my /server option?
I have tried /s, /server and -s. None of them work. I have checked and double checked the spelling of my server name. I have checked to make sure that the tf.exe I am running is the TFS 2008 version.
I am so confused and getting a bit frustrated.
(The sad thing is I had this working last week. I ran several history commands without any issues. I don't have the text from those commands, so I don't know what I did different, but I know it CAN work.)
Any help would be great!
Usually when you get this message it's because the /server parameter is unnecessary - that is, the client has determined your workspace and server information from the path you gave it. This should only happen with local paths, however, not with server paths. Can you confirm that you're only using server paths in your commands?