Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135
Adrian, On Thu, Apr 03, 2014 at 04:42:07PM -0700, Adrian Chadd wrote: A I've had no time to continue looking at this, I'm sorry. A A I'm very overworked and I'm not able to be both the net80211, ath and A iwn maintainer given how much actual attention they all require. A Someone has to step up and take command of the iwn code. I must admit that right now iwn(4) is in much worse shape than it was a year ago. :( And the fact you abandon it in current shape is very unpleasant. I started to use laptops with iwn(4) about 3 years ago, and I always track head on my laptop. My connectivity was perfect for the first two years. But for the last year the situation is getting worse and worse. Since you were actively hacking on iwn(4), I decided to keep calm an wait for you to achieve your goals, only then complain. Now you abandon it. What hurts me right now: - The overall network performance is extremely bad. Doing an scp(1) from/to a box, that is on the same LAN I am achieving 30 Kb/s with long stalls. For the last couple of months I am moving larger files to my laptop with help of a USB memstick. - When I actually do run bulk upload/download via iwn(4), the entire office WiFi goes almost dead. My colleagues can't skype while I am copying a kernel file from my laptop to other close box, and copying lasts more than a minute (see above). Actually, not only WiFi is deafened by current iwn(4), it looks like entire 2.4GHz band is noised, because my wireless mouse gets very laggy and lossy during any bulk activity via iwn(4). - Even tiny traffic volume experiences packet loss. Right now I'm typing this via ssh, and sometimes I feel packet loss in the session. Note that my hardware haven't changed at all during last year. Only version of FreeBSD. Right now I have strong desire to update my sources of dev/iwn to early 2013, get it compilable and work with that. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: another Make (maybe) problem
Warner Losh i...@bsdimp.com writes: What happens if you say ‘DEBUG_FLAGS+= -gdwarf-2’ instead of a naked -g? Experiment in progress ... ... same result as before. (Dang.) What next? Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on amd64/amd64
TB --- 2014-04-08 09:10:26 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-04-08 09:10:26 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-04-08 09:10:26 - starting HEAD tinderbox run for amd64/amd64 TB --- 2014-04-08 09:10:26 - cleaning the object tree TB --- 2014-04-08 09:11:32 - /usr/local/bin/svn stat --no-ignore /src TB --- 2014-04-08 09:11:36 - At svn revision 264257 TB --- 2014-04-08 09:11:37 - building world TB --- 2014-04-08 09:11:37 - CROSS_BUILD_TESTING=YES TB --- 2014-04-08 09:11:37 - MAKEOBJDIRPREFIX=/obj TB --- 2014-04-08 09:11:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-04-08 09:11:37 - SRCCONF=/dev/null TB --- 2014-04-08 09:11:37 - TARGET=amd64 TB --- 2014-04-08 09:11:37 - TARGET_ARCH=amd64 TB --- 2014-04-08 09:11:37 - TZ=UTC TB --- 2014-04-08 09:11:37 - __MAKE_CONF=/dev/null TB --- 2014-04-08 09:11:37 - cd /src TB --- 2014-04-08 09:11:37 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Tue Apr 8 09:11:44 UTC 2014 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/words.c -o words.o /src/sys/boot/ficl/words.c:2573:60: warning: implicit conversion from 'unsigned long' to 'int' changes value from 18446744073709551615 to -1 [-Wconstant-conversion] flag = ((pFW != NULL) (pFW-flags FW_ISOBJECT)) ? FICL_TRUE : FICL_FALSE; ~ ^ /src/sys/boot/ficl/ficl.h:252:21: note: expanded from macro 'FICL_TRUE' #define FICL_TRUE ((unsigned long)~(0L)) ^~~~ 1 warning generated. cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/amd64/sysdep.c -o sysdep.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c softcore.c -o softcore.o building static ficl library ranlib libficl.a === sys/boot/amd64 (all) === sys/boot/amd64/efi (all) Warning: Object directory not changed from original /src/sys/boot/amd64/efi bmake[5]: .depend, 1171: ignoring stale .depend for /src/sys/boot/amd64/efi/../../ficl/libficl.a bmake[5]: .depend, 1171: ignoring stale .depend for /src/sys/boot/amd64/efi/../../efi/libefi/libefi.a cc -O2 -pipe -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include -I/src/sys/boot/amd64/efi/../../efi/include/amd64 -I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include -I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH -I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 -DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT -I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments -Wl,-T/src/sys/boot/amd64/efi/ldscript.amd64 -Wl,-Bsymbolic -shared -Wl,-znocombreloc -nostdlib -o loader.sym autoload.o bootinfo.o conf.o copy.o devicename.o elf64_freebsd.o framebuffer.o main.o reloc.o vers.o amd64_tramp.o start.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o ls.o misc.o module.o panic.o load_elf32.o load_elf32_obj.o reloc_elf32.o load_elf64.o load_elf64_obj.o reloc_elf64! .o disk.o part.o crc32.o bcache.o interp_forth.o /src/sys/boot/amd64/efi/../../ficl/libficl.a /src/sys/boot/amd64/efi/../../efi/libefi/libefi.a /obj/amd64.amd64/src/tmp/usr/lib/libstand.a cc: error: no such file or directory: '/src/sys/boot/amd64/efi/../../ficl/libficl.a' cc: error: no such file or directory: '/src/sys/boot/amd64/efi/../../efi/libefi/libefi.a' *** Error code 1 Stop. bmake[5]: stopped in /src/sys/boot/amd64/efi *** Error code 1 Stop. bmake[4]: stopped in /src/sys/boot/amd64 *** Error code 1 Stop. bmake[3]: stopped in /src/sys/boot *** Error code 1 Stop. bmake[2]: stopped in /src/sys *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** [buildworld] Error code 1 Stop in /src. TB --- 2014-04-08 12:25:11 - WARNING: /usr/bin/make returned exit code 1 TB ---
Re: vt text cursor invisible in reverse video
On Thu, 3 Apr 2014 00:38:23 -0500 Mark Linimon lini...@lonesome.com wrote: On Wed, Apr 02, 2014 at 01:01:11PM +0200, Claude Buisson wrote: After 19 years of FreeBSD use and not being part of any chapel/coterie/mafia I don't keep much illusion about the outcome.. I'm sorry that you feel that way. Rest assured that a large number of those of us that work on FreeBSD do try to improve the software. We also try to figure out ways to get more people involved as contributors, to keep things from becoming stagnant. Yes, I know we're not always successful. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Hi guys! Claude, sorry for delay. Can you please try now? WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vt text cursor invisible in reverse video
On 04/08/2014 16:25, Aleksandr Rybalko wrote: On Thu, 3 Apr 2014 00:38:23 -0500 Mark Linimon lini...@lonesome.com wrote: On Wed, Apr 02, 2014 at 01:01:11PM +0200, Claude Buisson wrote: After 19 years of FreeBSD use and not being part of any chapel/coterie/mafia I don't keep much illusion about the outcome.. I'm sorry that you feel that way. Rest assured that a large number of those of us that work on FreeBSD do try to improve the software. We also try to figure out ways to get more people involved as contributors, to keep things from becoming stagnant. Yes, I know we're not always successful. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Hi guys! Claude, sorry for delay. Can you please try now? Applied r264258 and rebuilt kernel. Problem solved - thanks As for the need for kbmux in the kernel to have a working keyboard under X.org as found in [1], it seems also to be mandatory to be able to load a keymap with kbdcontrol. Can you confirm ? [1] http://lists.freebsd.org/pipermail/freebsd-current/2014-March/048917.html WBW CBu ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135
Hi, Which hardware is it? The driver hasn't changed _that_ much since 2013. I'd really like some help in figuring out which commit(s) broke the driver for you. Would you mind bisecting the driver from HEAD from 2013 to now and tell me when the first break was? I'm happy to fix bugs, but I can only work on making it better for me. I've not had very much feedback from people (except yay it works better and it's the same) so this is news to me. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Wifi compatibility
I am looking at the TP-Link TL-WN722N high gain USB dongle. I was curious if anyone knew if the rum(4) driver will support this hardware, if I could run it in HOSTAP mode, and if not, what high gain adapter would that you all would suggest? Thanks in advanced. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on amd64/amd64
TB --- 2014-04-08 21:00:25 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-04-08 21:00:25 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-04-08 21:00:25 - starting HEAD tinderbox run for amd64/amd64 TB --- 2014-04-08 21:00:25 - cleaning the object tree TB --- 2014-04-08 21:01:34 - /usr/local/bin/svn stat --no-ignore /src TB --- 2014-04-08 21:01:37 - At svn revision 264276 TB --- 2014-04-08 21:01:38 - building world TB --- 2014-04-08 21:01:38 - CROSS_BUILD_TESTING=YES TB --- 2014-04-08 21:01:38 - MAKEOBJDIRPREFIX=/obj TB --- 2014-04-08 21:01:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-04-08 21:01:38 - SRCCONF=/dev/null TB --- 2014-04-08 21:01:38 - TARGET=amd64 TB --- 2014-04-08 21:01:38 - TARGET_ARCH=amd64 TB --- 2014-04-08 21:01:38 - TZ=UTC TB --- 2014-04-08 21:01:38 - __MAKE_CONF=/dev/null TB --- 2014-04-08 21:01:38 - cd /src TB --- 2014-04-08 21:01:38 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Tue Apr 8 21:01:45 UTC 2014 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/loader.c -o loader.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/math64.c -o math64.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/prefix.c -o prefix.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/search.c -o search.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/stack.c -o stack.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/tools.c -o tools.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/vm.c -o vm.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/words.c -o words.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c /src/sys/boot/ficl/amd64/sysdep.c -o sysdep.o cc -O2 -pipe -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC -I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64 -I/src/sys/boot/ficl/../common -c softcore.c -o softcore.o building static ficl library ranlib libficl.a === sys/boot/amd64 (all) === sys/boot/amd64/efi (all) Warning: Object directory not changed from original /src/sys/boot/amd64/efi bmake[5]: .depend, 1171: ignoring stale .depend for /src/sys/boot/amd64/efi/../../ficl/libficl.a bmake[5]: .depend, 1171: ignoring stale .depend for /src/sys/boot/amd64/efi/../../efi/libefi/libefi.a cc -O2 -pipe -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include -I/src/sys/boot/amd64/efi/../../efi/include/amd64 -I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include -I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH -I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 -DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT -I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float
Re: [CFT] ASLR and PIE on amd64
On 4/2/14, Shawn Webb latt...@gmail.com wrote: On Apr 02, 2014 04:54 PM +0200, Oliver Pinter wrote: On 4/2/14, Oliver Pinter oliver.p...@gmail.com wrote: On 3/31/14, Shawn Webb latt...@gmail.com wrote: On Mar 31, 2014 02:07 AM +0200, Oliver Pinter wrote: On 3/22/14, Shawn Webb latt...@gmail.com wrote: Hey All, First off, I hope that even as a non-committer, it's okay that I post a call for testing. If not, please excuse my newbishness in this process. This is my first time submitting a major patch upstream to FreeBSD. Over the past few months, I've had the opportunity and pleasure to enhance existing patches to FreeBSD that implement a common exploit mitigation technology called Address Space Layout Randomization (ASLR) along with support for Position Independent Executables (PIE). ASLR+PIE has been a long-requested feature by many people I've met on IRC. I've submitted my patch to PR kernel/181497. I'm currently in the process of adding PIE support to certain high-visibility applications in base (mainly network daemons). I've added a make.conf knob that's default to enabled (WITH_PIE=1). An application has to also explicitly support PIE as well by defining CAN_PIE in the Makefile prior to including bsd.prog.mk. After I get a decent amount of applications enabled with PIE support, I'll submit one last patch. The following sysctl's can be set with a kernel compiled with the PAX_ASLR option: security.pax.aslr.status: 1 security.pax.aslr.debug: 0 security.pax.aslr.mmap_len: 16 security.pax.aslr.stack_len: 12 security.pax.aslr.exec_len: 12 The security.pax.aslr.status sysctl enables and disables the ASLR system as a whole. The debug sysctl gives debugging output. The mmap_len sysctl tells the ASLR system how many bits to randomize with mmap() is called. The stack_len sysctl tells the ASLR system how many bits to randomize in the stack. The exec_len sysctl tells the ASLR system how many bits to randomize the execbase (this controls PIE). These sysctls can be set as a per-jail basis. If you have an application which doesn't support ASLR, yet you want ASLR enabled for everything else, you can simply place that misbehaving application in a jail with only that jail's ASLR settings turned off. Please let me know how your testing goes. I'm giving a presentation at BSDCan regarding this. If you want to keep tabs on my bleeding-edge development process, please follow my progress on GitHub: https://github.com/lattera/freebsd (branch: soldierx/lattera/aslr). Thank you very much, Hi! Please apply this patch. This fixed an issue with tunables. Patch merged successfully into my GitHub repo. Fixed with commit d2c0813. I'll include it in my next patch submission upstream when I submit my PIE work. Thanks! please see the attached patch, compile and boot tested on amd64 Some more patches, and one critical fix (0006-PAX-ASLR-use-the-right-sysent-before-this-commit-cal.patch). You are awesome. I'll integrate those patches today. In reviewing your patches, I noticed a few places where I'm keying off the local pax_aslr_debug variable. I ought to switch that to keying off the jail's pr_pax_aslr_debug variable. https://github.com/HardenedBSD/hardenedBSD/commits/hardened/10/aslr ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] ASLR and PIE on amd64
On Apr 09, 2014 02:17 AM +0200, Oliver Pinter wrote: On 4/2/14, Shawn Webb latt...@gmail.com wrote: On Apr 02, 2014 04:54 PM +0200, Oliver Pinter wrote: On 4/2/14, Oliver Pinter oliver.p...@gmail.com wrote: On 3/31/14, Shawn Webb latt...@gmail.com wrote: On Mar 31, 2014 02:07 AM +0200, Oliver Pinter wrote: On 3/22/14, Shawn Webb latt...@gmail.com wrote: Hey All, First off, I hope that even as a non-committer, it's okay that I post a call for testing. If not, please excuse my newbishness in this process. This is my first time submitting a major patch upstream to FreeBSD. Over the past few months, I've had the opportunity and pleasure to enhance existing patches to FreeBSD that implement a common exploit mitigation technology called Address Space Layout Randomization (ASLR) along with support for Position Independent Executables (PIE). ASLR+PIE has been a long-requested feature by many people I've met on IRC. I've submitted my patch to PR kernel/181497. I'm currently in the process of adding PIE support to certain high-visibility applications in base (mainly network daemons). I've added a make.conf knob that's default to enabled (WITH_PIE=1). An application has to also explicitly support PIE as well by defining CAN_PIE in the Makefile prior to including bsd.prog.mk. After I get a decent amount of applications enabled with PIE support, I'll submit one last patch. The following sysctl's can be set with a kernel compiled with the PAX_ASLR option: security.pax.aslr.status: 1 security.pax.aslr.debug: 0 security.pax.aslr.mmap_len: 16 security.pax.aslr.stack_len: 12 security.pax.aslr.exec_len: 12 The security.pax.aslr.status sysctl enables and disables the ASLR system as a whole. The debug sysctl gives debugging output. The mmap_len sysctl tells the ASLR system how many bits to randomize with mmap() is called. The stack_len sysctl tells the ASLR system how many bits to randomize in the stack. The exec_len sysctl tells the ASLR system how many bits to randomize the execbase (this controls PIE). These sysctls can be set as a per-jail basis. If you have an application which doesn't support ASLR, yet you want ASLR enabled for everything else, you can simply place that misbehaving application in a jail with only that jail's ASLR settings turned off. Please let me know how your testing goes. I'm giving a presentation at BSDCan regarding this. If you want to keep tabs on my bleeding-edge development process, please follow my progress on GitHub: https://github.com/lattera/freebsd (branch: soldierx/lattera/aslr). Thank you very much, Hi! Please apply this patch. This fixed an issue with tunables. Patch merged successfully into my GitHub repo. Fixed with commit d2c0813. I'll include it in my next patch submission upstream when I submit my PIE work. Thanks! please see the attached patch, compile and boot tested on amd64 Some more patches, and one critical fix (0006-PAX-ASLR-use-the-right-sysent-before-this-commit-cal.patch). You are awesome. I'll integrate those patches today. In reviewing your patches, I noticed a few places where I'm keying off the local pax_aslr_debug variable. I ought to switch that to keying off the jail's pr_pax_aslr_debug variable. https://github.com/HardenedBSD/hardenedBSD/commits/hardened/10/aslr And for anyone who's tracking HEAD (like me): https://github.com/HardenedBSD/hardenedBSD/commits/hardened/current/aslr pgpxHOeRmSC1p.pgp Description: PGP signature
When to rebuild world?
Hello, I have just started tracking freebsd-current on a spare machine. I am going through my first buildworld to update from -stable to -current. Do I need to buildworld everytime I 'svn update' (atleast weekly). Or will src/UPDATING tell me when a buildworld is actually needed? -srp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: When to rebuild world?
Hi, On Wed, 9 Apr 2014 06:43:36 +0530 (IST) Saju Ravindran Pillai saju.pil...@gmail.com wrote: Hello, I have just started tracking freebsd-current on a spare machine. I am going through my first buildworld to update from -stable to -current. Do I need to buildworld everytime I 'svn update' (atleast weekly). Or will src/UPDATING tell me when a buildworld is actually needed? UPDATING tells you nothing about the parts which got updated. If you want to save time, you would have to check which files are updated. As it is rare that only kernel files are updated, I always compile both the world and the kernel. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Wifi compatibility
On 2014/04/09 04:10, Parker Gibson wrote: I am looking at the TP-Link TL-WN722N high gain USB dongle. I was curious if anyone knew if the rum(4) driver will support this hardware, if I could run it in HOSTAP mode, and if not, what high gain adapter would that you all would suggest? Your dongle uses AR9271 chip which is currently not supported, but it seems that Adrian has been working on it [1]. I recommend using run(4). It supports hostapd. [1] http://lists.freebsd.org/pipermail/freebsd-wireless/2013-December/004220.html Thanks in advanced. Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
