test test test
Comment by spz [dreamwidth.org] Sunday afternoon, September 10th, 2017

Since Makefile.common v1.26, the application configuration files go to ${PKG_SYSCONFBASE}/sasl/, instead of ${PREFIX}/lib/sasl as documented in a multitude of web HowTo documents including this page. After a

define(`confLOG_LEVEL', 22)dnl

sendmail(8) told me about the error of my ways, but it sure was a long way...

Comment by hauke early Wednesday morning, July 26th, 2017

Now veracrypt is supporting FreeBSD. The reason I'm pushing this is it the biggest standard across platforms. Veracrypt supports Truecrypt. Truecrypt had a method of encrypting a whole systen drive while it was running live drive and the source code is available. Does that mean it could be done for NetBSD, well no but it's a start. It has been done on Windows.


I see a lot stuff that's BSD or open source and it seems they frequently are always reinventing the wheel. It's depressing sometimes.

Comment by Sam Thursday evening, July 13th, 2017


"sailor's goal is not to provide bullet-proof security, chroot is definitely not a trustable isolator; instead, sailor is a really convenient way of trying / testing an evironment without compromising your workstation filesystem." As of 6/30/17 It's under heavy development.

Comment by Sean Plank late Friday evening, June 30th, 2017

docs: http://www.soum.co.jp/~jun/OSC2017tokyospring.pdf http://www.soum.co.jp/~jun/asiabsdcon2017.pdf

Comment by jun early Thursday morning, March 9th, 2017
Community might take https://github.com/conformal/xombrero?files=1 and make NetBrowser.
Comment by jaypatelani terribly early Thursday morning, February 23rd, 2017
Agreed. And Lumina doesn't rely on dbus.
Comment by jaypatelani terribly early Thursday morning, February 23rd, 2017

I can't imagine the specified /boot.cfg entry, with a path going into /usr/pkg/... can really be found by boot. All previous tutorials and how-to's specify copying .../xen*-kernel/xen.gz into the root directory.

The number of users having problems following the advice on the boot.cfg entry suggests that /boot can't traverse the directory tree deep enough to find xen.gz, even assuming /usr/pkg is on the same filesystem as /.

Comment by schnoebe in the wee hours of Sunday night, February 20th, 2017

I forgot to add that Truecrypt had a version for Linux and at one time had a BSD version which I believe no longer is around or operative. Truecrypt was anonymously written and he closed up shop and just disappeared one day. Truecrypt has also had extensive code verification leading to additions in Veracrypt.

Here's a link for tcplay(derivative or Truecrypt).




and the Dragonfly BSD I linked above where it's use of tcplay is described.

I hope this is helpful All the questions that you asked in the summary have been answered on other systems with TC and VC. I know they're not Net but it could be a good start on how they've managed it.

Comment by Sam early Wednesday morning, January 4th, 2017

I think you should do something that no one wants to do. Take as much as you can from a long term existing system. There's a program that started on win98(name change)(scramdisk) and moved to Win 2000(ECM) then on Win XP,...etc(Truecrpyt). It now is rewritten and called (Veracrypt) for Windows, Linux, Mac OS and Raspberry Pi ARMv7. The only thing stopping me from moving to one of the BSD's is reading truecrypt files. DragonflyBSD reads Truecrypt through tcplay a rewrite of truecrypt but DF is a little more experimental than I want for a desktop.


So there's two versions from the same Truecrypt source. Tcplay and Veracrypt. Veracrypt is a newer version that is audited and has corrected some small deficiencies of TC so is better but bigger, more complete and complex. The MacOS works through FUSE specifically OSXFUSE 2.5. Linux I think through DMcrypt. Here's what so good about Veracrypt/Truecrypt. It has encryption on the fly for not only regular drives but the OS system drive also, after it's running. This means not setting up encryption but encrypting the drive as the OS runs, then writing the boot with password enabled. It's very, very nice. I'm not saying that all these things need to be in place at once but using the code they have already written shows a pathway. Too start just use the code for equivalent encryption to Veracrypt(which has a compatibility function for Truecrypt). The important thing is Truecrypt has been around a long, long time and lots of people have this format and it works. For some reason people keep reinventing the wheel and will not use that which a lot of work has gone into already. Now I KNOW that porting this will not be easy but maybe NetBSD's FUSE can be used the same way that Veracrypt uses MacFUSE. Strip out the GUI stuff but know that it can be added and most of it is already set up for GTK in the MAC so the possibility remains to have it on a desktop with GUI using the lower level already done. Sorry so long but it complicated.

Comment by Sam early Wednesday morning, January 4th, 2017
Add a comment
Contact | Disclaimer | Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
NetBSD® is a registered trademark of The NetBSD Foundation, Inc.