search for: kernelconfig

...me story and a solution but the solution does not work for me and I see the same situation at http://www.centos.org/modules/newbb/viewtopic.php?topic_id=5087 I do not know what do to any more, hopefully you can help me with getting kernel 2.6.18 working. CentOS systems: 4.3 en 4.4 Kernel: 2.6.18 Kernelconfig: http://www.netfeed.nl/software/kernels/2.6.18/kernelconfig Many thanks in advance! -- Met vriendelijke groeten / Kind regards, ? Thijs Joosten

...system panic. IV. Workaround Do one of the following: 1) Disable IPv6 entirely by following these steps: - Remove or comment out any lines mentioning `INET6' from your kernel configuration file, and recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html>. - Reboot your system. 2) If all untrusted users are confined within a jail(8), ensure that the security.jail.socket_unixiproute_only sysctl is set to 1 and verify that no IPv6 sockets are currently open: # sysctl security.jail.socket_unixiproute_only=1 # sockstat -6 This will restr...

...system panic. IV. Workaround Do one of the following: 1) Disable IPv6 entirely by following these steps: - Remove or comment out any lines mentioning `INET6' from your kernel configuration file, and recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html>. - Reboot your system. 2) If all untrusted users are confined within a jail(8), ensure that the security.jail.socket_unixiproute_only sysctl is set to 1 and verify that no IPv6 sockets are currently open: # sysctl security.jail.socket_unixiproute_only=1 # sockstat -6 This will restr...

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

...only application known to utilize accept filters by default. IV. Workaround Do not use accept filters. If you have enabled the ACCEPT_FILTER_DATA or ACCEPT_FILTER_HTTP options in your kernel, remove these options and recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. If you have loaded one of the kernel accept filters by using kldload(8), then you must modify your startup scripts not to load these modules and reboot your system. You may list loaded kernel modules by using kldstat(8). If loaded, the HTTP accept filter will be l...

...loaded as a module: # kldstat | grep linux.ko If no output is produced, the linux compatibility layer is compiled into the kernel. Remove the line options COMPAT_LINUX from your kernel configuration file and recompile the kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. If output is produced, then the linux compatibility layer is loaded as a kernel module. If the module is not currently being used (by a process running under linux emulation, for example) then it may be possible to unload it: # kldunload linux # kldstat | grep lin...

...loaded as a module: # kldstat | grep linux.ko If no output is produced, the linux compatibility layer is compiled into the kernel. Remove the line options COMPAT_LINUX from your kernel configuration file and recompile the kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. If output is produced, then the linux compatibility layer is loaded as a kernel module. If the module is not currently being used (by a process running under linux emulation, for example) then it may be possible to unload it: # kldunload linux # kldstat | grep lin...

...o one of the following: 1) Disable the System V Shared Memory interface entirely by following these steps: - Remove or comment out any lines mentioning `SYSVSHM' from your kernel configuration file, and recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html>. - Remove or comment out any lines mentioning `sysvshm' from /boot/loader.conf and /etc/rc.conf. - On FreeBSD 5.x systems only , System V Shared Memory support may be provided as a kld(4). To be absolutely safe, remove any files named `sysvshm.ko' in /module...

...mpact, present only in FreeBSD 5.x systems, can be avoided by uncommenting or adding the `INVARIANTS' line to your kernel configuration: options INVARIANTS #Enable calls of extra sanity checking Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. NOTE WELL: This workaround is only for FreeBSD 5.x systems. This workaround does not eliminate the possibility of a local denial-of-service attack. V. Solution 1) Upgrade your vulnerable system to 4.8-STABLE, or to any of the RELENG_4_8 (4.8-RELEASE-p2), RELEN...

...mpact, present only in FreeBSD 5.x systems, can be avoided by uncommenting or adding the `INVARIANTS' line to your kernel configuration: options INVARIANTS #Enable calls of extra sanity checking Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. NOTE WELL: This workaround is only for FreeBSD 5.x systems. This workaround does not eliminate the possibility of a local denial-of-service attack. V. Solution 1) Upgrade your vulnerable system to 4.8-STABLE, or to any of the RELENG_4_8 (4.8-RELEASE-p2), RELEN...

...mpact, present only in FreeBSD 5.x systems, can be avoided by uncommenting or adding the `INVARIANTS' line to your kernel configuration: options INVARIANTS #Enable calls of extra sanity checking Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. NOTE WELL: This workaround is only for FreeBSD 5.x systems. This workaround does not eliminate the possibility of a local denial-of-service attack. V. Solution 1) Upgrade your vulnerable system to 4.8-STABLE, or to any of the RELENG_4_8 (4.8-RELEASE-p2), RELEN...

...o one of the following: 1) Disable the System V Shared Memory interface entirely by following these steps: - Remove or comment out any lines mentioning `SYSVSHM' from your kernel configuration file, and recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html>. - Remove or comment out any lines mentioning `sysvshm' from /boot/loader.conf and /etc/rc.conf. - On FreeBSD 5.x systems only , System V Shared Memory support may be provided as a kld(4). To be absolutely safe, remove any files named `sysvshm.ko' in /module...

...to mount filesystems, a successful jail root compromise in a jail without procfs visible cannot exploit this vulnerability. * Remove the "options PROCFS" line from your kernel configuration file, if present, and compile a new kernel as described in http://www.freebsd.org/handbook/kernelconfig.html If the running kernel was compiled with "options PROCFS", then any user who has root privileges can mount procfs and exploit vulnerability 3, regardless of system securelevel. If the kernel does not include this option, then an attempt to mount procfs will trigger a load...

...fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-04:04/tcp47.patch # fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-04:04/tcp47.patch.asc b) Apply the patch. # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. VI. Correction details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - ----------------------------------------------------------------...

...mpact, present only in FreeBSD 5.x systems, can be avoided by uncommenting or adding the `INVARIANTS' line to your kernel configuration: options INVARIANTS #Enable calls of extra sanity checking Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. NOTE WELL: This workaround is only for FreeBSD 5.x systems. This workaround does not eliminate the possibility of a local denial-of-service attack. V. Solution 1) Upgrade your vulnerable system to 4.8-STABLE, or to any of the RELENG_4_8 (4.8-RELEASE-p2), RELEN...

...sing your PGP utility. ftp://ftp.freebsd.org/pub/FreeBSD/CERT/patches/SA-00:52/tcp-iss-3.x.patch ftp://ftp.freebsd.org/pub/FreeBSD/CERT/patches/SA-00:52/tcp-iss-3.x.patch.asc # cd /usr/src/sys/ # patch -p < /path/to/patch [ Recompile your kernel as described in http://www.freebsd.org/handbook/kernelconfig.html and reboot the system ] 2b) FreeBSD 4.x systems Apply the patch below and recompile your kernel. Either save this advisory to a file, or download the patch and detached PGP signature from the following locations, and verify the signature using your PGP utility. ftp://ftp.freebsd.org/pub/Fr...

I have heard that somebody has compile a new kernel and he made Virtual User ....and if somebody want to use exploit he will connect to the virtual! can you tell me how to compile a kernel ??? I just have one but I want one more kernel to create that virtual user ! -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered

...${CWD}/build-kernel-injail.sh ${CWD}/${WORKDIR}/ cp -p ${CWD}/list ${CWD}/${WORKDIR}/ you were overwriting the kernel config you adjusted the MINIROOTSIZE before?! i was able to get up to a 58mb ramdisks on that board without failure at startup. please tell me if you are interested in any dmesg/kernelconfig/whatever listings for your configs. greets adrian

...fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-06:11/ipsec.patch # fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-06:11/ipsec.patch.asc b) Apply the patch. # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. VI. Correction details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - ----------------------------------------------------------------...

...fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-06:11/ipsec.patch # fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-06:11/ipsec.patch.asc b) Apply the patch. # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in <URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot the system. VI. Correction details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - ----------------------------------------------------------------...