SSH patch for X SECURITY bug (CVE-2015-5352)?

omeone I'd ask around about it. If no patch is committed, is the plan to just defer this one until later? -- Alan Amesbury University Information Security http://umn.edu/lookup/amesbury ___ freebsd-stable@freebsd.org mailing list https://li

Re: Sanity check: FreeBSD 9.3 binaries on FreeBSD 9.1?

bability is greater than zero. It also sounds like I may be at least partially sane. Thanks! -- Alan Amesbury University Information Security http://umn.edu/lookup/amesbury ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mail

Sanity check: FreeBSD 9.3 binaries on FreeBSD 9.1?

r 9.3-RELEASE will generally run on 9.1-RELEASE. Does this sound generally correct, or am I totally off base here? Any major pitfalls I should know of? -- Alan Amesbury University Information Security http://umn.edu/lookup/amesbury ___ freebsd-s

Re: Inmutable bit in some binaries

-based OS (good luck changing any files there). I can't help in that regard. Actually, sysutils/ezjail puts together a pretty nice framework that makes use of what's effectively a read-only OS with other things overlaid on top of it.

Re: Garbled output from kgdb?

s; I'm just not ready to modify production assets without a second look. ;-) Thanks again for your help on this. I appreciate it! -- Alan Amesbury OIT Security and Assurance University of Minnesota ___ freebsd-stable@freebsd.org mailing list http:

Re: Garbled output from kgdb?

#x27;d like to keep disruptions to a minimum. That said, it's panicked more than once, so I think I can justify using it towards elimination of the cause of that panic if necessary. I appreciate you taking the time to look at it this far! Thanks! -- Alan Ame

Re: Garbled output from kgdb?

identical lines 50-114 removed] #115 0x0000 in ?? () #116 0x in ?? () Cannot access memory at address 0xac058000 -- Alan Amesbury OIT Security and Assurance University of Minnesota ___ freebsd-stable@freebsd.o

Garbled output from kgdb?

y worried... until now. (I've actually suspected hardware/BIOS issues relating to serial port access, which is why I've stayed out of that thread.) That the crash dump includes similar corruption suggests to me that it's not the serial device, but something a bit closer to FreeBSD

Re: zdump on amd64

n 27 03:29:52 -219 EST isdst=0 > gmtoff=-18000 > EST Fri Jan 1 04:59:59 -219 UTC = Thu Dec 30 23:59:59 -219 EST isdst=0 > gmtoff=-18000 > EST Fri Jan 1 05:00:00 -219 UTC = Fri Jan 1 00:00:00 -219 EST isdst=0 > gmtoff=-18000 > ^C [snip] Known bug. See http://www.freebsd

Re: getting garbage faster using FreeBSD?

s some physical coordination). It's primarily for item #1 that I hadn't mentioned this earlier, as most readers of -STABLE users are probably looking for a more scalable solution. -- Alan Amesbury University of Minnesota ___ freebs

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

dded in. Also, I've noticed that STP goes nuts for the bge(4) host, but doesn't seem to notice when the em(4) host watchdog timer goes off. However, I don't have direct access to the network equipment, so I can't check for differen

Re: FreeBSD boots too fast on Dell PE850

, so I'll do so (hopefully later today). Thanks again! -- Alan Amesbury University of Minnesota ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD boots too fast on Dell PE850

r. I hesitated to open a bug report on this because--well, it doesn't seem like the OS is really at fault here. :-\ Recommendations for improvement are welcome, as well as any suggestions for a less kludgy fix. I *really* dislike the idea of slowing down the boot process. :-( -- Ala

UID/GID ranges (was Re: Required audit group is missing...)

Looks like the Handbook needs to be updated to reflect this, as audit isn't currently listed. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-uid-and-gids.html -- Alan Amesbury University of Minnesota ___ freebsd-s

Re: Kernel INCLUDE_CONFIG_FILE workaround?

e somewhere, as well as anything included by GENERIC (such as the stuff in DEFAULTS). Again, this used to work great, but appears to have been broken in favor of... usability? -- Alan Amesbury University of Minnesota ___ freebsd-stable@freebsd.org mailing

Kernel INCLUDE_CONFIG_FILE workaround?

one that seems to make the most sense) is to delete DEFAULTS from /sys/`uname -m`/conf and use kernel configs that don't use "include {otherconfig}". However, besides the fact that DEFAULTS would come back every time /usr/src is sync'ed, I'm unsure what the long-term rami

Getting a patch integrated into -STABLE?

the bug report to indicate this, and b) is there a typical time-to-fix for this sort of thing? Thanks in advance! -- Alan Amesbury University of Minnesota ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fr

Re: Strange crashing/rebooting problem

and the memory diagnostics utilities (second pair). The .tar.gz files containg raw floppy images suitable for writing to floppy with a command like cat file.img | dd of=/dev/fd0 obs=18k or something like that. The .ZIP files contain what appear to be ISO images suitable for burning to a CD