Re: Getting started with ktls

On Sun, Mar 14, 2021 at 09:54:33AM -0600, Alan Somers wrote: > On Sun, Mar 14, 2021 at 8:57 AM tech-lists wrote: > > > I'd like to have it (ktls) available on the ARM64 > > stable/13-n244876-0b45290603b. Is it just a matter of adding the option, > > and then the sysctls become available? Is it

Re: Getting started with ktls

On Wed, Mar 10, 2021 at 06:17:42PM -0700, Alan Somers wrote: > On Wed, Mar 10, 2021 at 5:31 PM Benjamin Kaduk wrote: > > > On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > > > I'm trying to make ktls work with "zfs send/recv" to substantially r

Re: Getting started with ktls

On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > I'm trying to make ktls work with "zfs send/recv" to substantially reduce > the CPU utilization of applications like zrepl. But I have a few questions: > > * ktls(4)'s "Transmit" section says "Once TLS transmit is enabled by a >

Re: openssl in head returning "certificate expired" when it has not expired

On Tue, Feb 02, 2021 at 03:48:06AM +, Rick Macklem wrote: > Benjamin Kaduk wrote: > >On Tue, Feb 02, 2021 at 12:46:25AM +, Rick Macklem wrote: > >> I've recently been testing the daemons that do the > >> non-application data stuff for nfs-over-tls wi

Re: openssl in head returning "certificate expired" when it has not expired

On Tue, Feb 02, 2021 at 12:46:25AM +, Rick Macklem wrote: > I've recently been testing the daemons that do the > non-application data stuff for nfs-over-tls with the > openssl in head. > > These daemons work fine with both ports/security/openssl (openssl-1.1.1h) > and

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

On Sat, Jan 23, 2021 at 03:25:59PM +, Rick Macklem wrote: > Ronald Klop wrote: > >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote: > >But I think for Tor to support KTLS it needs to implement some things > >itself. More information about that could be asked at the maintainer of > >the

Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71

On Mon, Nov 16, 2020 at 09:27:29AM +, Graham Perrin wrote: > Attempting to build r367615 on Friday 13th: > > … > > ===> lib/libprocstat/zfs (install) > install -U  -C -o root -g wheel -m 444 > /usr/src/lib/libprocstat/libprocstat.h > /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ > ===>

Re: dma fails to connect (error:1408F10B:SSL routines:ssl3_get_record:wrong version number)

On Sun, Aug 16, 2020 at 04:44:51PM +0200, Ronald Klop wrote: > Hi, > > I have uname -UK -> 1300101 1300101 in my laptop. This uses libexec/dma as > mail agent. > I have 2 jails running uname -U -> 1300101 and 1300104. All dma configs > are the same. > > In all 1300101 versions dma can

Re: TLS certificates for NFS-over-TLS floating client

On Wed, Mar 04, 2020 at 03:15:48AM +, Rick Macklem wrote: > Hi, > > I am slowly trying to understand TLS certificates and am trying to figure > out how to do the following: > -> For an /etc/exports file with... > /home -tls -network 192.168.1.0 -mask 255.255.255.0 > /home -tlscert > > This

Re: how to use the ktls

On Mon, Feb 03, 2020 at 10:49:38PM +, Rick Macklem wrote: > Benjamin Kaduk wrote: > >On Tue, Jan 28, 2020 at 11:01:31PM +, Rick Macklem wrote: > >> John Baldwin wrote: > >> [stuff snipped] > >> >I don't know yet. :-/ With the TOE-based TLS I had

Re: how to use the ktls

On Tue, Jan 28, 2020 at 11:01:31PM +, Rick Macklem wrote: > John Baldwin wrote: > [stuff snipped] > >I don't know yet. :-/ With the TOE-based TLS I had been testing with, this > >doesn't > >happen because the NIC blocks the data until it gets the key and then it's > >always > >available via

Re: how to use the ktls

On Thu, Jan 09, 2020 at 10:53:38PM +, Rick Macklem wrote: > John Baldwin wrote: > >On 1/7/20 3:02 PM, Rick Macklem wrote: > >> Hi, > >> > >> Now that I've completed NFSv4.2 I'm on to the next project, which is > >> making NFS > >> work over TLS. > >> Of course, I know absolutely nothing about

Re: openssl 1.1.1 utils mkerr.pl

On Wed, Jan 16, 2019 at 09:52:26AM -0800, Enji Cooper wrote: > > > On Jan 15, 2019, at 5:55 PM, David Cornejo wrote: > > > > Hi, > > > > I am working on some code that wants to use mkerr.pl from the openssl > > distribution - but this appears to have been left out of the import to > > base. >

Re: Upcoming release of V 12

On Tue, Sep 11, 2018 at 10:21:31AM -0700, Jeffrey Bouquet wrote: > I'm running v12 as HEAD [ 12.0-CURRENT] > > And am at a loss as to how to change it to 12.0-STABLE vs one day > running a non-rebuilt 13.0-CURRENT > > Without risking a scenario such as: >svn up 12.0, fail for some reason

Re: Celeron J3160 with enabled Turbo mode stays at 480MHz(lowestsetting) forever and can not lower frequency without Tuebo mode

On Thu, Sep 06, 2018 at 03:02:29AM +0300, Lev Serebryakov wrote: > Hello Benjamin, > > Thursday, September 6, 2018, 1:32:46 AM, you wrote: > > >> > I don't think you need something accurate. > >> Ok, here is results. I'm working in single-user mode. > >> > >> TL;DR "Turbo" mode make "openssl"

Re: Celeron J3160 with enabled Turbo mode stays at 480MHz(lowestsetting) forever and can not lower frequency without Tuebo mode

On Wed, Sep 05, 2018 at 07:27:06PM +0300, Lev Serebryakov wrote: > On 05.09.2018 17:51, Cy Schubert wrote: > > > I don't think you need something accurate. > Ok, here is results. I'm working in single-user mode. > > TL;DR "Turbo" mode make "openssl" much slower (x3.5)! > > I can not properly

Re: Status of OpenSSL 1.1.1

On Fri, Aug 03, 2018 at 07:02:18AM -0400, Eric McCorkle wrote: > On 08/03/2018 04:44, Warner Losh wrote: > > > > > > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk > <mailto:ka...@mit.edu>> wrote: > > > > On Wed, Aug 01, 2018 at 10:05:28AM -

Re: Status of OpenSSL 1.1.1

On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > wrote: > > > > Hi folks, > > > > I'm wondering what's the status of OpenSSL 1.1.1

Re: ESXi NFSv4.1 client id is nasty

On Sun, Jun 17, 2018 at 12:35:12PM +, Rick Macklem wrote: > Hi, > > Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi > 6.5u1 > (VMware) against the FreeBSD server. I have given him a bunch of hackish > patches > to try and some of them do help. However not all

Re: how do I use the make universe machines?

On Wed, Jun 06, 2018 at 12:47:17AM +, Rick Macklem wrote: > I've heard mention of "make universe" machines multiple times, > but have no idea how to use them? > Is there doc on this? > > Thanks, rick > ps: I'll admit I haven't looked at the developer's guide in a long time. I think

Re: ``make buildkernel'' fails when /usr/obj is empty

On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > On Thu, 31 May 2018 09:52:22 +0200 > Gary Jennejohn wrote: > > > There's something totally screwy about trying to build a kernel when > > /usr/obj is not populated. > > > > I ran ``make clean'' in /usr/src and then ``make

Re: Can't load linux64.ko module

On Wed, Apr 04, 2018 at 02:34:53PM -0700, Steve Kargl wrote: > > The answer is compat/linux/linux_vdso.c where we find > > #if defined(__i386__) || (defined(__amd64__) && defined(COMPAT_LINUX32)) > #define __ELF_WORD_SIZE 32 > #else > #define __ELF_WORD_SIZE 64 > #endif > > having

Re: clang manual page?

On Thu, Apr 05, 2018 at 05:56:24PM -0700, Steve Kargl wrote: > I never said that you said it was in base. I'm noting that > referring a user to a non-existent manual page is of little > help. In fact, your 7 word response is an affirmation that > the tools supplied in base should be properly

FINAL CALL for 2017Q4 quarterly status reports

Dear FreeBSD Community, This is the last call for submissions for the 2017Q4 FreeBSD Quarterly Status Update. The deadline for submissions is January 14, 2018, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening

Second Call for 2017Q4 quarterly status reports

Happy new year, and I hope that meltdown and spectre are not taking too much of everyone's time. That said, the submission deadline is still January 14th, so please do send in your status report entries to us! Thanks, Ben On Mon, Dec 25, 2017 at 06:27:16PM -0600, Benjamin Kaduk wrote: > D

Call for 2017Q4 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 14, 2018, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

FreeBSD Quarterly Status Report - Third Quarter 2017

more about these, as well as improved support for the AMD Zen family of processors (e.g., Ryzen), and a whole lot more! --Benjamin Kaduk __ The deadline for submissions covering the period from October to December

Re: FreeBSD Documentation

On Sun, Oct 29, 2017 at 07:47:33PM +0300, Yuri Pankov wrote: > On Sun, 29 Oct 2017 22:13:16 +0800, Blubee Blubeeme wrote: > > How can we suggest edits for the docs? > > > > The docs still reference using sysinstall to setup a jail when it hasn't > > been that since at least 2011 > >

Re: svn: E170013: Unable to connect to a repository at URL 'svn+ssh://svn.freebsd.org/ports/head'

On Thu, Oct 26, 2017 at 08:47:06PM +0300, Boris Samorodov wrote: > Hi All, > > Since a few days I can't update repository (info and cleanup works, > but not update and commit) both at local and remote systems. > > Is it my personal problem/misconfig? > > --- > % svnlite up > Updating '.': >

FINAL CALL for 2017Q3 quarterly status reports

Dear FreeBSD Community, This is the last call for submissions for the 2017Q3 FreeBSD Quarterly Status update. The deadline for submissions is October 21, 2017, for work done in July through September. Status report submissions do not need to be very long. They may be about anything happening

Re: Update AppleMacbook wiki

On Wed, Oct 11, 2017 at 12:20:52PM +0200, Johannes Lundberg wrote: > Hi > > (cc: koobs because he last updated the wiki page) > > I have a 2014 Macbook Pro Retina 15" which suffers from ahci msi > related timeouts when writing to the internal storage. (sorry don't > have the error message

Call for 2017Q3 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is October 21, 2017, for work done in July through September. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

FreeBSD Quarterly Status Report - Second Quarter 2017

FreeBSD Quarterly Status Report - 2nd Quarter 2017 FreeBSD continues to defy the rumors of its demise. Much of the development work done this quarter was not particularly visible, especially the effort needed to ensure the upcoming 11.1 release has as few regressions as possible.

Re: linux64.ko fails to load in -CURRENT

On Fri, Jul 28, 2017 at 01:58:12PM -0700, R. Tyler Croy wrote: > > > COMPAT_LINUX32 was in the kernel configuration, guess I know that these things > are incompatible now :) > > I think the handbook notes on statically linking linux support should probably > be removed: >

Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

On Tue, Jul 11, 2017 at 11:48:55AM +, Rick Macklem wrote: > Cy Schubert wrote: > > > >How about a warning message + an UPDATING entry + no MFC? And, relnotes = > >yes to say we now support RFC7530 in 12.0? > Sounds fine to me. I'll wait to see if there are more comments. Yes, this seems like

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: > 09.07.2017 18:48, Boris Samorodov пишет: > > 09.07.2017 18:37, Benjamin Kaduk пишет: > >> > >> Documentation looks okay, as -I is documented during > >> the install stage, and is not supp

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: > Hi All, > > I try to create a FreeBSD guest as per TH, section "21.7.2. Creating > a FreeBSD Guest". All is good up until the last command at the section. > When I try to launch the installed client, I get: > - > # sh

Re: .configure && make fails to find ld [dlopen]

On Thu, Jul 06, 2017 at 09:55:35AM +0800, blubee blubeeme wrote: > > those are sprinkled all over the place, how do I avoid that and use libc > instead? The software you are building needs to update their configure process to cope with dlopen being somewhere other than libdl, from what

Re: Current amd64 new error or warning from today's current with ruby r320323

On Tue, Jun 27, 2017 at 1:56 PM, Trond Endrestøl < trond.endres...@fagskolen.gjovik.no> wrote: > On Tue, 27 Jun 2017 20:28+0200, Trond Endrestøl wrote: > > > On Sun, 25 Jun 2017 22:05+0300, Konstantin Belousov wrote: > > > > > On Sun, Jun 25, 2017 at 08:51:07PM +0200, Trond Endrest?l wrote: > > >

Final Call for 2017Q2 Quarterly Status Reports

Dear FreeBSD Community, Only one week remains before the July 7 deadline for submitting entries for the next FreeBSD Quarterly Status update, covering work done in April through June. Please consider submitting an entry for work you have done this quarter, even if it seems minor to you. Status

Re: Current amd64 new error or warning from today's current with ruby r320323

On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov wrote: > No need, I understood why MAP_STACK failed in this case, thanks to the > ktrace log. This is indeed something ruby-specific, or rather, triggered > by ruby special use of libthr. It is not related to the main

Re: [RESOLVED] Failover Mode Between Ethernet and Wireless Interfaces broken on >= 11

On Fri, Jun 23, 2017 at 11:22:46PM -0500, Benjamin Kaduk wrote: > I fixed the rc.conf snippet in the handbook in r50399. > I lost track of the rest of the thread as to what needs to be > changed in the actual command examples in lagg.4 and/or the > handbook, though. To be clear,

Re: Has gdb been disconnected from make installworld?

On Sun, Jun 25, 2017 at 09:03:58PM +0200, Trond Endrestøl wrote: > On Sun, 25 Jun 2017 20:55+0200, Trond Endrestøl wrote: > > > I was at bit surprised to see gdb missing from /usr/bin this evening. > > The executables are still being built in /usr/obj/usr/src/gnu/usr.bin/gdb. > > > > This is on

Re: [RESOLVED] Failover Mode Between Ethernet and Wireless Interfaces broken on >= 11

I fixed the rc.conf snippet in the handbook in r50399. I lost track of the rest of the thread as to what needs to be changed in the actual command examples in lagg.4 and/or the handbook, though. -Ben On Fri, Jun 23, 2017 at 05:33:05PM -0700, Adrian Chadd wrote: > hi! > > Thanks! Yes please

Second Call for 2017Q2 Quarterly Status Reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 7, 2017, for work done in April through June. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to

Re: Buildworld failing early. Nothing SVN yet except Makefile.inc1

On Thu, Jun 22, 2017 at 12:11:48PM -0700, Jeffrey Bouquet wrote: > Wishing to avoid SVN for now to salvage nvidia-driver just in case... [snip] It's really hard to understand what you are trying to say in this email. Does "avoid SVN for now" mean that you are trying to stay on a specific

Re: Unsure about buildworld

On Wed, Jun 21, 2017 at 06:23:30AM -0700, Jeffrey Bouquet wrote: > > > On Tue, 20 Jun 2017 22:15:18 -0500, Benjamin Kaduk <ka...@mit.edu> wrote: > > > > > Building a release and extracting the tarballs is something that > > people do, though I don't have

Re: Unsure about buildworld

On Tue, Jun 20, 2017 at 01:58:58PM -0700, Jeffrey Bouquet wrote: > Used rsync to put /usr/src/.svn to > /usr2/src/.svn [another disk] > did an svn up of that ^^ Is there some reason (e.g., documentation) to believe that will result in a stable and

Call for 2017Q2 Quarterly Status Reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 7, 2017, for work done in April through June. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to

Re: The future of the roff toolchain

On Sun, May 21, 2017 at 02:57:33PM +0200, Baptiste Daroussin wrote: > > What I want to propose now, it to render them as PDF (html?) once and push > them > somewhere (to be defined) as static document on our documentation website. > Please doceng@ provide me a location where to push them. > >

FreeBSD Quarterly Status Report - First Quarter 2017

of reports, covering the first quarter of 2017. --Benjamin Kaduk __ The deadline for submissions covering the period from April to June 2017 is July 7, 2017. ___

FINAL CALL for 2017Q1 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2017, for work done in January through March. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way

Second call for 2017Q1 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2017, for work done in January through March. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way

Re: LOR on RPi3 r314894

On Thu, Mar 09, 2017 at 07:01:07AM +0100, Gergely Czuczy wrote: > > > On 2017. 03. 09. 6:59, Benjamin Kaduk wrote: > > On Wed, Mar 08, 2017 at 02:06:33PM +0100, Gergely Czuczy wrote: > >> On 2017. 03. 08. 13:06, Hans Petter Selasky wrote: > >>> You might

Re: LOR on RPi3 r314894

On Wed, Mar 08, 2017 at 02:06:33PM +0100, Gergely Czuczy wrote: > On 2017. 03. 08. 13:06, Hans Petter Selasky wrote: > > You might check the links on this page to see if your LOR is already > > listed: > > > > https://wiki.freebsd.org/LOR > Thank you, I wasn't aware of this page. It turns out

Call for 2017Q1 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2017, for work done in January through March. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way

Re: Lock order reversal [ newbie ] report [2nd one]

Hi Jeffrey, Thank you for your enthusiasm in reporting these. Unfortunately, it is very likely that these two are "well-known" and believed to be harmless, so you have not discovered something terribly exciting. An old and no-longer particularly maintained listing of these and other LORs is at:

FreeBSD Quarterly Status Report - Fourth Quarter 2016

brings the usual mix of continuations of many stalwart projects and entires of new participants, as well as the return of some items after a few quarters' hiatus. Enjoy and be enlightened! --Benjamin Kaduk

Re: ISO image: where is the CLANG compiler?

On Thu, Jan 19, 2017 at 07:38:30PM +, Glen Barber wrote: > > Random thought: > > Brought up out-of-band, can you try this from a memstick.img and your > already-built userland/kernel to do what you had originally tried to > install the system? > > # make -C /usr/src

Re: recent change to vim defaults?

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: > I noticed that suddenly vim is grabbing mouse movements, which makes > life really hard. > > Was there a specific revision that brought in this change, and can it > be removed? I remember seeing something go by during an

Re: New Lock Order Reversal in 12.0?

On Mon, Jan 09, 2017 at 02:31:39AM +, Anindya Mukherjee wrote: > Hi Ben, > > Thanks for your reply, and yes, I did notice #238. I should say at this point > that I'm a newbie when it comes to kernel code and am trying to learn about > it (hence current). Understood. It's good that you are

Re: New Lock Order Reversal in 12.0?

On Mon, Jan 09, 2017 at 12:32:28AM +, Anindya Mukherjee wrote: > Hi, I'm running 12.0-current and noticed a LOR message from WITNESS which I > couldn't find a report about. I looked at > http://sources.zabbadoz.net/freebsd/lor.html, among other places. > > system details: >

FINAL CALL for 2016Q4 status reports

The deadline for submitting 2016Q4 entries is just a week away! -Ben On Mon, Dec 26, 2016 at 02:31:44PM -0600, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline for the next FreeBSD Quarterly Status update is January 7, > 2016, for work done in October thro

Re: A question about updating src & ports

On Thu, Dec 29, 2016 at 11:44:20AM +0100, O. Hartmann wrote: > > from my own experience I left the path of "portsnap" and stay with svn alone. > portsnap > tends to "flood" the /var filesystem with a tremendous number of files over > time. Each > time you issue "portsnap fetch update", a file

second call for 2016Q4 status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2016, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

Call for 2016Q4 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2016, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

FreeBSD Quarterly Status Report - Third Quarter 2016

is no less exciting, with 11.0 making its way out just after the end of Q3, the new core coming into its own, and much more that you'll have to read and find out. --Benjamin Kaduk __ Please submit status reports

Re: was: CURRENT [r307305]: r307823 still crashing

On Sun, 23 Oct 2016, O. Hartmann wrote: > How can I track a memory leak? I think I did not read enough of the context, but vmstat and top can track memory usage as a general thing. > How can I write to disk the backtrace given by the debugger when > crashing? My box I can freely test is using

Final call for 2016Q3 quarterly status reports

Dear FreeBSD Community, The deadline for the submissions to the next FreeBSD Quarterly Status is October 9, 2016, for work done in July through September. This is the final call for submissions; please let us know if you are considering making a submission but are not sure that your submission

/dev/dsp got more sensitive about writes?

Hi all, I've updated from r302211 (June 26) to r306427 (yesterday), and the behavior of audio/sox (in its play(1) alias) seems to have changed. I used to be able to suspend play(1) for an arbitrary period of time and have the output continue when it was foregrounded again. Now, it seems that I

Second Call for 2016Q3 quarterly status reports

Dear FreeBSD Community Ten days remain in the submission period -- plase send in your entries for the 2016Q3 report! More details quoted below. -Ben (on behalf of monthly@) On Wed, 7 Sep 2016, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline for the next FreeBSD

Re: Panic @306337: Duplicate free of 0xfffff8000ef61500 from zone 0xfffff8000772b000(mbuf) slab 0xfffff8000ef61f90(5)

On Mon, 26 Sep 2016, David Wolfskill wrote: > > I tried "panic" at the laptop's "db> " prompt, but I have no crash dump. IIRC, just 'dump' is supposed to work these days. Also 'call doadump' which is older. 'panic' does more stuff and is somewhat more likely to fail than directly dumping.

Re: Heimdal in base

On Wed, 14 Sep 2016, Garrett Wollman wrote: > < > said: > > > Well, it's definitely too late for 11, now. > > > But, Debian is preparing to remove their heimdal package entirely, > > imminently: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837728 > [...] > > Since 11.0 hasn't been released

Heimdal in base

(was Re: OpenSSH HPN) [See https://lists.freebsd.org/pipermail/freebsd-security/2015-November/008747.html for the bits that Dag-Erling skipped] On Fri, 13 Nov 2015, Dag-Erling Smørgrav wrote: > Benjamin Kaduk <ka...@mit.edu> writes: > > Things seem to have slowed down a lot

Call for 2016Q3 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is October 7, 2016, for work done in July through September. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

Re: date(1) default format changed between 10.3 and 11.0-BETA3

On Sat, 6 Aug 2016, Baptiste Daroussin wrote: > On Sat, Aug 06, 2016 at 02:15:36PM +1000, Greg 'groggy' Lehey wrote: > > On Friday, 5 August 2016 at 18:56:33 +0300, Andrey A. Chernov wrote: > > > On 05.08.2016 18:44, Mark Martinec wrote: > > >> On 2016-08-05 17:23, Andrey Chernov wrote: > > >> >

FreeBSD Quarterly Status Report - Second Quarter 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FreeBSD Project Quarterly Status Report - Second Quarter 2016 Now available: the 2016Q2 model of the FreeBSD Project Status Report! This quarter brings several exciting improvements over previous models. We have enhancements from

Re: svn: Skipped '.' Summary of conflicts: Skipped paths: 1

On Thu, 21 Jul 2016, Julian H. Stacey wrote: > Hi, Reference: > > From: Benjamin Kaduk <ka...@mit.edu> > > Date: Thu, 21 Jul 2016 12:19:43 -0400 (EDT) > > Benjamin Kaduk wrote: > > OK, it wasn't an svn problem then, I was maybe missing

Re: svn: Skipped '.' Summary of conflicts: Skipped paths: 1

On Thu, 21 Jul 2016, Julian H. Stacey wrote: > Hi current@ > I've seen this ### about 3 times lately, anyone else ? > uname -a > FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD > 12.0-CURRENT #1 r302560M: Wed Jul 13 01:28:27 CEST > 2016 >

Last call for 2016Q2 quarterly status reports

Reminder: we're still looking for more submissions for the 2015Q2 status report! Please let us know if you wish to write an entry, even if it will not be finished by today. Thanks, Ben (for the monthly@ team) On Tue, 21 Jun 2016, Benjamin Kaduk wrote: > Dear FreeBSD Commun

Call for 2016Q2 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 7, 2016, for work done in April through June. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to

Re: Packaging the FreeBSD base system with pkg(8)

On Tue, 5 Apr 2016, Gary Jennejohn wrote: > Will there be an option not to merge? I never update /etc when > I do installworld because what I have works for me and I see no > need to make any changes to a working system. And you expect your system to continue working after a new system user is

Last call for 2016Q1 quarterly status report submissions

Dear FreeBSD Community, There are just a few days left until the April 7 deadline for submitting entries for the next FreeBSD Quarterly Status Report. Please submit entries for work done in January, February, or March. Status report submissions do not have to be very long. They may be about

Second call for 2016Q1 quarterly status report submissions

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2016, for work done in January through March -- less than two weeks away! Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and

Re: Several LOR's with most recent install media

On Thu, 3 Mar 2016, Chris H wrote: > > > > Mar 2 22:00:00 spare newsyslog[705]: logfile turned over due to size>100K > > Mar 2 22:12:00 spare kernel: lock order reversal: > > Mar 2 22:12:00 spare kernel: 1st 0xda5f45a0 bufwait (bufwait) @ > > /usr/src/sys/kern/vfs_bio.c:3488 > > Mar 2

Re: Lock order reversal in CURRENT

On Wed, 24 Feb 2016, Eax Melanhovich wrote: > Hello. > > Yesterday I built a kernel and world using master branch (6a8922d3) of > FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I > got a "lock order reversal" report: > > http://i.imgur.com/jDZ4A3O.png > > According to this

FreeBSD Quarterly Status Report - Fourth Quarter 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FreeBSD Project Quarterly Status Report: October - December 2015 The fourth quarter of 2015 saw a great deal of activity for FreeBSD. This is now the third quarter running for which I can say that this is the largest report yet published!

Third call for 2015Q4 quarterly status reports

One last reminder -- less than a week remains to submit entries for the 2015Q4 report! -Ben On Mon, 28 Dec 2015, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > There are less than two weeks left before the deadline for the next > FreeBSD Quarterly Status update -- submiss

second call for 2015Q4 quarterly status reports

Dear FreeBSD Community, There are less than two weeks left before the deadline for the next FreeBSD Quarterly Status update -- submissions are due on January 7, 2016, for work done in October through December. Status report submissions do not have to be very long. They may be about anything

Re: RPC request sent to 127.0.0.1 becomes from other IP on machine

On Thu, 10 Dec 2015, Rick Macklem wrote: > Hi, > > Mark has reported a problem via email where the nfsuserd daemon sees > requests coming from an IP# assigned to the machine instead of 127.0.0.1. > Here's a snippet from his message: > Ok, I have Plex in a jail and when I scan the remote NFS

call for 2015Q4 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2016, for work done in October through December. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great

Re: CFT: uintmax_t rman

On Mon, 16 Nov 2015, Warner Losh wrote: > > > > On Nov 15, 2015, at 9:13 PM, Justin Hibbits wrote: > > > > (Attempted to send this yesterday, but appears it didn't go through. > > Apologies if it really did go through). > > > > As part of a project getting FreeBSD on the

Re: OpenSSH HPN

On Thu, 12 Nov 2015, Dewayne Geraghty wrote: > Heimdal is (and has been for some time) undergoing constant development. > For reasons unknown, they do not perform releases. I am aware of updates > from heimdal that are being applied to the samba project (in fact some of > the samba developers

kereros telnet/rlogin/etc. (was Re: OpenSSH HPN)

On Wed, 11 Nov 2015, Daniel Kalchev wrote: > > Perhaps similar level of security could be achieved by “the old tools” > if they were by default compiled with Kerberos. Although, this still > requires building additional infrastructure. The kerberized versions of the old tools are basically

FreeBSD Quarterly Status Report - Third Quarter 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FreeBSD Project Quarterly Status Report: July - September 2015 The third quarter of 2015, from July to September, was again a period of busy activity for FreeBSD: for the second quarter in a row we have the largest report yet published.

Re: is building kernel in /sys/amd64/conf depreciated in 11 ?

On Tue, 20 Oct 2015, John wrote: > Hi, > > as subject - is building kernel in /sys/amd64/conf depreciated? > > I can get a modified kernel to build and install in /usr/src but not > in /sys/amd64/conf. I always used to be able to do this in there, then > again I either used -RELEASE or -STABLE. I

Re: r286615: /usr/libexec/ftpd broken!

On Tue, 18 Aug 2015, Garrett Cooper wrote: On Aug 18, 2015, at 08:57, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: On Tue, 18 Aug 2015, Marcel Moolenaar wrote: On Aug 17, 2015, at 10:15 PM, O. Hartmann ohart...@zedat.fu

Re: r286615: /usr/libexec/ftpd broken!

On Tue, 18 Aug 2015, Marcel Moolenaar wrote: On Aug 17, 2015, at 10:15 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Port security/heimdal installs its own ftpd with its appropriate manpages. Ugh :-( I would argue that heimdal should not be in the business of supplying an ftpd.

FreeBSD Quarterly Status Report - Second Quarter 2015

Block __ This status report was compiled by Benjamin Kaduk and Warren Block. Please submit status reports for the third quarter of 2015 (July to September) by October 7, 2015

Call for FreeBSD 2015Q2 (April-June) Status Reports

Dear FreeBSD Community, Only one week remains before the deadline to submit entries for the next FreeBSD Quarterly Status update -- the deadline is July 14, 2015, for work done in April through June. Status report submissions do not have to be very long. They may be about anything happening in

  1   2   3   >