Search results

Here's a way to prevent nmap's OS fingerprinting: 1. Find out how it actually works. 2. Then block matching packets (e.g. via ipfw). Also, make sure you're not leaking data via banners, etc: # : | nc -N localhost 22 SSH-2.0-OpenSSH_7.2 FreeBSD-20160310 # echo "VersionAddendum none"...

You probably skipped the description of the -N flag while reading the man page... ;) ... echo "$RESPONSE" | nc -N -l $HOST $PORT ...

According to Intel the i5-2410M does not support AES-NI.

.oO( ZOMG!1!! Rat Hat is teh nu Micro$oft1!!! ) Hint: Don't panic.

Well, I for one am surprised. Do you have any numbers? Did you objdump the binaries and diff them? This sounds like there's something wrong with clang's CPU detection. It should be able to figure out every nitty gritty detail of the CPU and act accordingly, e.g. it should be able to figure out...

The problem was probably caused by a file whose name started with a dash. One solution is to use cp --. The "--" means "no more options" so everything after it will be treated as a filename. This also works for other tools (like rm, mkdir, touch, etc.): $ ls -strangename $ cp *strange* /tmp...

Using static binaries actually increases memory usage because each program's address space contains copies of the libraries it uses. With dynamic linking the OS needs to load a specific library into memory only once. If a program then uses the library the OS will simply map it into the program's...

Device nodes are created by calling make_dev. There's an example in the Architecture Handbook. Btw, Joseph Kong's FreeBSD Device Drivers is a great book about the topic.

The only place where tqe_next is set to a non-NULL value seems to be _pthread_mutex_setprioceiling: ... TAILQ_INSERT_BEFORE(m2, m, m_qe); ...

Note that it says it's a link, not a list. ;) Take a look at the ENQUEUE_MUTEX and DEQUEUE_MUTEX macros (starting at line 281 on my box [1]): this is where the mutex is add to/removed from either &curthread->mutexq or &curthread->pp_mutexq. [1] the OpenGrok links you've posted are not...

Looks like they are read/modified by the macros provided in sys/queue.h (see queue for details). So you might want to search for TAILQ_INSERT_TAIL(..., m_qe) and TAILQ_REMOVE(..., m_qe). This link might come handy.

The disclosure comes with a piece of C code that checks for the vulnerability. So let's use it... % uname -rms FreeBSD 9.3-STABLE amd64 % % ls -lF /compat/linux/lib/libc[\.-]* -rwxr-xr-x 1 root wheel 1902892 Oct 15 03:36 /compat/linux/lib/libc-2.12.so* lrwxr-xr-x 1 root wheel 12 Oct 15...

Could you share the case temperature and what cooler you use?

Since "default compiler" is another way of saying "whatever compiler make uses" one could ask make directly. The compiler being used also depends on the directory since the Makefile in there might override any defaults (i.e. redefine "CC" and/or "CXX"): % make -f /dev/null -V CC -V CXX cc c++...

LOL! Excellent choice! That's the best book on UNIX programming out there. o_O ... Heretic!

No, it would not. FreeBSD (or any BSD for that matter) is like this beautiful, quiet beach you've discovered. You don't want this beach to become a fscking tourist attraction. This is exactly what happened to Linux (as pointed out by someone more than 10 years ago):

I can remember having had the same problem: the "Stats for nerds" window would keep reappearing. My "solution" was to rm -rf ~/.macromedia && touch ~/.macromedia && chmod 0000 ~/.macromedia. Doing this (obviously) removes all Flash Player settings and prevents it from storing new ones.

Looked like? Do you have any gdb output so we can have a look at what you're actually doing (and how)? If the address of s1 increases by two after incrementing s1 then *s1 is not of type "char". This is unlikely, except someone did something exceptionally funny (like "#define char short")...

Try xrdb -load Xblabla, i.e. tell xrdb to override existing settings.

Oops, I just noticed that on 10.x the correct man page is jemalloc, MALLOC_OPTIONS is called MALLOC_CONF and "6k" should probably be "opt.lg_chunk:16". Why don't you just tell us what the real problem is your trying to solve (instead of engaging in what I perceive as borderline-trolling)?