Thanks and kuddo’s to XS4all to be the first consumer provider that delivers IPv6!

I was convinced that I was not going to make the exam, or at least that was my idea afterwards. Today I Got the results back from ISC2. It had been confirmed that I…. made the test and that I should do some additional steps to get fully certified. This is one thing I didn’t expect to happen, especially since it took 5 weeks and I was convinced that that was because of my poor performance.

But, it seems that I can call myself CISSP now!

So I decided to give it a proper try again and fiddled with some remote clients to get it going.

Lets wait and see how the next few days will workout for it, and how the tapes are being seen after being written to (filebackend).

- zfsloader added
- zpool version of ZFS subsystem updated to version 14
- NFSv4 ACL support in UFS and ZFS; support added to cp(1), find(1),
getfacl(1), mv(1), and setfacl(1) utilities
- UltraSPARC IV/IV+, SPARC64 V support
- SMP support in PowerPC G5
- BIND 9.6.2-P2
- sendmail updated to 8.14.4
- OpenSSH updated to 5.4p1
- GNOME 2.30.1, KDE 4.4.5

For a complete list of new features and known problems, please see the
online release notes and errata list, available at:

http://www.FreeBSD.org/releases/8.1R/relnotes.html

http://www.FreeBSD.org/releases/8.1R/errata.html

For more information about FreeBSD release engineering activities,
please see:

http://www.FreeBSD.org/releng/

Availability
————-

FreeBSD 8.1-RELEASE is now available for the amd64, i386, ia64, pc98,
powerpc, and sparc64 architectures.

FreeBSD 8.1 can be installed from bootable ISO images or over the
network. Some architectures (currently amd64 and i386) also support
installing from a USB memory stick. The required files can be downloaded
via FTP or BitTorrent as described in the sections below. While some
of the smaller FTP mirrors may not carry all architectures, they will
all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO and memory stick images are
included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1: This contains everything necessary to install the base FreeBSD
operating system, a collection of pre-built packages, and the
documentation. It also supports booting into a “livefs” based
rescue mode. This should be all you need if you can burn
and use DVD-sized media.

disc1: This contains the base FreeBSD operating system and the
documentation packages for CDROM-sized media. There are no
other packages.

livefs: This contains support for booting into a “livefs” based
rescue mode but does not support doing an install from the
CD itself. It is meant to help rescue an existing system
but could be used to do a network based install if necessary.

bootonly: This supports booting a machine using the CDROM drive but
does not contain the support for installing FreeBSD from the
CD itself. You would need to perform a network based install
(e.g. from an FTP server) after booting from the CD.

memstick: This can be written to an USB memory stick (flash drive) and
used to do an install on machines capable of booting off USB
drives. It also supports booting into a “livefs” based rescue
mode. The documentation packages are provided but no other
packages.

As one example of how to use the memstick image, assuming the USB drive
appears as /dev/da0 on your machine something like this should work:

# dd if=8.1-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.1-RELEASE can also be purchased on CD-ROM or DVD from several
vendors. One of the vendors that will be offering FreeBSD 8.1-based
products is:

~ FreeBSD Mall, Inc. http://www.freebsdmall.com/

BitTorrent
———-

8.1-RELEASE ISOs are available via BitTorrent. A collection of torrent
files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP
—

At the time of this announcement the following FTP sites have
FreeBSD 8.1-RELEASE available.

ftp://ftp.freebsd.org/pub/FreeBSD/
ftp://ftp1.freebsd.org/pub/FreeBSD/
ftp://ftp5.freebsd.org/pub/FreeBSD/
ftp://ftp10.freebsd.org/pub/FreeBSD/
ftp://ftp.cz.freebsd.org/pub/FreeBSD/
ftp://ftp.dk.freebsd.org/pub/FreeBSD/
ftp://ftp.fr.freebsd.org/pub/FreeBSD/
ftp://ftp.jp.freebsd.org/pub/FreeBSD/
ftp://ftp.ru.freebsd.org/pub/FreeBSD/
ftp://ftp1.ru.freebsd.org/pub/FreeBSD/
ftp://ftp.tw.freebsd.org/pub/FreeBSD/
ftp://ftp4.tw.freebsd.org/pub/FreeBSD/
ftp://ftp.uk.freebsd.org/pub/FreeBSD/
ftp://ftp1.us.freebsd.org/pub/FreeBSD/
ftp://ftp5.us.freebsd.org/pub/FreeBSD/
ftp://ftp10.us.freebsd.org/pub/FreeBSD/

However before trying these sites please check your regional mirror(s)
first by going to:

ftp://ftp..FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The
FreeBSD Handbook. It provides a complete installation walk-through
for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Updates from Source
——————-

The procedure for doing a source code based update is described in the
FreeBSD Handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

The branch tag to use for updating the source is RELENG_8_1 for CVS.
For SVN use releng/8.1.

FreeBSD Update
————–

The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.[0123]-RELEASE,
8.0-RELEASE, 8.1-BETA1, or 8.1-RC[12] can upgrade as follows:

# freebsd-update upgrade -r 8.1-RELEASE

During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically
performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 7.3-RELEASE or
earlier will be prompted by freebsd-update to rebuild all third-party
applications (e.g., ports installed from the ports tree) due to updates
in system libraries.

After updating installed third-party applications (and again, only if
freebsd-update printed a message indicating that this was necessary),
run freebsd-update again so that it can delete the old (no longer used)
system libraries:

# freebsd-update install

Finally, reboot into 8.1-RELEASE:

# shutdown -r now

Support
——-

The FreeBSD Security Team has designated FreeBSD 8.1 an “Extended”
support release and currently plans to support FreeBSD 8.1 until
July 31, 2012. For more information on the Security Team and their
support of the various FreeBSD branches see:

http://www.freebsd.org/security/

Acknowledgments
—————

Many companies donated equipment, network access, or man-hours to
support the release engineering activities for FreeBSD 8.1 including
The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp,
Internet Systems Consortium, and Sentex Communications.

The release engineering team for 8.1-RELEASE includes:

Ken Smith Release Engineering,
amd64, i386, sparc64 Release Building,
Mirror Site Coordination
Robert Watson Release Engineering, Security
Konstantin Belousov Release Engineering
Marc Fonvieille Release Engineering, Documentation
Hiroki Sato
Release Engineering, Documentation
Bjoern Zeeb Release Engineering
Marcel Moolenaar ia64, powerpc Release Building
Takahashi Yoshihiro PC98 Release Building
Joe Marcus Clarke Package Building
Erwin Lansing Package Building
Mark Linimon Package Building
Pav Lucistnik Package Building
Ion-Mihai Tetcu Package Building
Martin Wilke (miwi@FreeBSD.org> Package Building
Colin Percival Security Officer

Trademark
———

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums
——————-

MD5 (FreeBSD-8.1-RELEASE-amd64-bootonly.iso) = e522b6f4af801e40f52d402d937f1886
MD5 (FreeBSD-8.1-RELEASE-amd64-disc1.iso) = 644ded0765f68984f2c2d8159e16acd1
MD5 (FreeBSD-8.1-RELEASE-amd64-dvd1.iso) = 3dc2f3131c390f3d8312349cd945aa24
MD5 (FreeBSD-8.1-RELEASE-amd64-livefs.iso) = 05ef3fb0e60cc0b263f2889f3a31c6c5
MD5 (FreeBSD-8.1-RELEASE-amd64-memstick.img) = 2769c3a606d786fa3840bb2937ac75c1

MD5 (FreeBSD-8.1-RELEASE-i386-bootonly.iso) = 7266163259fe288f08e3749503c58f73
MD5 (FreeBSD-8.1-RELEASE-i386-disc1.iso) = 4ead632b2655ca3bd5fc11f8d0c91a53
MD5 (FreeBSD-8.1-RELEASE-i386-dvd1.iso) = 75eb10e7586de1adf793e897ae344eb1
MD5 (FreeBSD-8.1-RELEASE-i386-livefs.iso) = 2f245b65923ff37fe5b760515072d8a9
MD5 (FreeBSD-8.1-RELEASE-i386-memstick.img) = db63bb7c02fad1cf0d1f2f5c24530c45

MD5 (FreeBSD-8.1-RELEASE-ia64-bootonly.iso) = 86ab91535a04cef25dcbe9d8a3f28944
MD5 (FreeBSD-8.1-RELEASE-ia64-disc1.iso) = d878a85d9fa3ed50e441222c5ffdbd3d
MD5 (FreeBSD-8.1-RELEASE-ia64-disc2.iso) = 206a5b1f00cc640aa7267ab25a8e37e8
MD5 (FreeBSD-8.1-RELEASE-ia64-disc3.iso) = c9f36660ad87ff71c95a3a14c4a36683
MD5 (FreeBSD-8.1-RELEASE-ia64-dvd1.iso) = 95c32e513c84a54d6b1e741943bb34b3
MD5 (FreeBSD-8.1-RELEASE-ia64-livefs.iso) = 76fb856ca73a6ad2b2d683cdbc46f6eb

MD5 (FreeBSD-8.1-RELEASE-pc98-bootonly.iso) = 3a8d1d854a389588a6344494ddc7f73c
MD5 (FreeBSD-8.1-RELEASE-pc98-disc1.iso) = 647399d13fb24753071b2c1e2c21198b
MD5 (FreeBSD-8.1-RELEASE-pc98-livefs.iso) = f7ee871bc4682e54cd365934f16dbd1a

MD5 (FreeBSD-8.1-RELEASE-powerpc-bootonly.iso) = 5a1a6ba5034fb6cc387f5ee39abd27fa
MD5 (FreeBSD-8.1-RELEASE-powerpc-disc1.iso) = d4cebf352ddd75b8ae288444f1931cd8
MD5 (FreeBSD-8.1-RELEASE-powerpc-disc2.iso) = 38a81b33fc22092d8ba851bd1b27ca78
MD5 (FreeBSD-8.1-RELEASE-powerpc-disc3.iso) = dc6074506bf4d26a8ae1dd6406883891

MD5 (FreeBSD-8.1-RELEASE-sparc64-bootonly.iso) = 7b44be3d8532b76ef1546b432e2af624
MD5 (FreeBSD-8.1-RELEASE-sparc64-disc1.iso) = 6a11b5a9bfff83e3833eefe1cac79d69
MD5 (FreeBSD-8.1-RELEASE-sparc64-dvd1.iso) = 3432fdb346e2cc00e26a025dbd7a7799
MD5 (FreeBSD-8.1-RELEASE-sparc64-livefs.iso) = 5b97fd1d08bb3d0699dc0a054a6a22f8

SHA256 (FreeBSD-8.1-RELEASE-amd64-bootonly.iso) = e24c270e1351d259b49a540647beaca88de3a5163371aa41e866fb0bf47ec572
SHA256 (FreeBSD-8.1-RELEASE-amd64-disc1.iso) = 2b87563d876cfe6095d1a7fef164d0eb0d63a6a889320b4bb91f138dc29e01e1
SHA256 (FreeBSD-8.1-RELEASE-amd64-dvd1.iso) = 5a7f23188bc20c8fbcc3a8d0eb630f2aa445c72d5bf1483c6bc83b17e590b397
SHA256 (FreeBSD-8.1-RELEASE-amd64-livefs.iso) = 9e40d4f72c82d8ab47a110ea73a3835f908fc0d5aefdb0dd89bf52775804a6d7
SHA256 (FreeBSD-8.1-RELEASE-amd64-memstick.img) = 44400547769fd8d3d4ab8eed09bfb1c0b8a4f4bc403bd2f848ec58963212cb37

SHA256 (FreeBSD-8.1-RELEASE-i386-bootonly.iso) = 8e0b4c877c3ae7714656d9ffacbf1b23710f71fe60255e81b902505af29e5ea9
SHA256 (FreeBSD-8.1-RELEASE-i386-disc1.iso) = 7b80c34ad0cb49ace8def6261561ab22ab9346c58b69e79a82c148682a62bdc1
SHA256 (FreeBSD-8.1-RELEASE-i386-dvd1.iso) = e273a66c370c519fe83711ee20b9a07165c2c3acd24dc3105efd6609ecb0b24f
SHA256 (FreeBSD-8.1-RELEASE-i386-livefs.iso) = a446f5572cd711ee3907f17149b5cae4552ba9d4a676a29ee0d8a557304fb787
SHA256 (FreeBSD-8.1-RELEASE-i386-memstick.img) = 549800209a67e6b6cfbe93b0cd1289ee7801a53c30ca229e82be14617b2ffa17

SHA256 (FreeBSD-8.1-RELEASE-ia64-bootonly.iso) = de4a56a9d02669285e1fdd3fbf4024a3fca427df24acd0663c840ed0d2b6e3aa
SHA256 (FreeBSD-8.1-RELEASE-ia64-disc1.iso) = 89747ee7f04fc3949da5ccac71b2cababb3d3be65842e46f1d545e0e6f6f9f94
SHA256 (FreeBSD-8.1-RELEASE-ia64-disc2.iso) = b3564cf59e4181ea9a7323f8f372a13a713615d444ccec90dac42d28bc46488a
SHA256 (FreeBSD-8.1-RELEASE-ia64-disc3.iso) = 084851c14850ad98bf52e00e49e9c4db90b420c52f6abbd015d7ab478f93ca9c
SHA256 (FreeBSD-8.1-RELEASE-ia64-dvd1.iso) = e7a8d16240b1890c24a8e46f5c03a4dec10ebc2ff585e9c2dcceb8bbfe099dc9
SHA256 (FreeBSD-8.1-RELEASE-ia64-livefs.iso) = 84910d35b37d03c4ff593de25fe6f0a7a2a5c34ee34d66d0d7d59015d87a19ce

SHA256 (FreeBSD-8.1-RELEASE-pc98-bootonly.iso) = 25e345c38d6a606a4363110c58ad5b21ecc8c0d03d1349b13772761d5d2a99be
SHA256 (FreeBSD-8.1-RELEASE-pc98-disc1.iso) = b7183eafec116954e5b729878eaa8b9f31af16c84651f9900dfd686f3ceae994
SHA256 (FreeBSD-8.1-RELEASE-pc98-livefs.iso) = 436981209a3d34a522f57e73340e9a74d4e28191df743ec2b55b7051d78de04a

SHA256 (FreeBSD-8.1-RELEASE-powerpc-bootonly.iso) = 44b3b08f225b863c0e8f5dcd3d54b64ce2a664fee1893377ef504a54b8677e40
SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc1.iso) = 0a27021d6c8bad5cd185bbd694a9dcc46eac71b12eb98180cd9d6875323a34d0
SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc2.iso) = 8c135cccbfbf260fef62fa2722fa7bbec823aaf76447f90108a4be02a10c79a8
SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc3.iso) = de7277e1ad23c8f9a5f2bb979becfb71602ceda89eb7c0dde8838a0f87e07e20

SHA256 (FreeBSD-8.1-RELEASE-sparc64-bootonly.iso) = c33ae727ef70ff351fdd09a37afbe1beb5065a10536444af93136993943e1d8c
SHA256 (FreeBSD-8.1-RELEASE-sparc64-disc1.iso) = 7f6b9a6bbfd01866dd0a7f305198a38cf66a2a2db5e071557ad45fc1bd77b561
SHA256 (FreeBSD-8.1-RELEASE-sparc64-dvd1.iso) = e741cbad4d7c72a6e15bdd84c8e7fcf08767ee269b6f1ae6a036a237fef9ff23
SHA256 (FreeBSD-8.1-RELEASE-sparc64-livefs.iso) = ef5254aad4b1376fd7b0dcc242498aac67d11a9ef32c0d9c2df256e59f370e03

Oranje: Thank you for getting this far, in two years the EK and after that the WK !

All my services (web/mail etc) had been dual-stacked to IPv4 and IPv6. That not only goes for *evilcoder.org, but also for a broad range of different hosts that I am running. Since it’s a great way to give every host it’s own IP, I also made a few more vhosts then I previously had.

And ofcourse JR-Hosting had also been adopted to run on IPv6, there all customers will gain their own IPv6 IP address, next to their current IPv4 address.

Whoehoe!

It makes it a bit more difficult this way since it used to be all in one post, but well, you will manage .

I will take some time to slowly convert all posts from the Polyglot setup to WPML. Tom had created a nice little script for that, which I need to tweak a little (his native language is NL, while mine is set to EN, should be a trivial change, but nevertheless I will proceed with caution ).

They all depend on some software version, or some specific library, or some specific way on how things are being dealt with. I am not entirely opposed to that, but I want to have the freedom to upgrade packages and my system where needed, instead of waiting for new versioned / static libraries. So, as long as functionality remains the same, I can use it.

I started developping evil-admin from scratch. Everything I had (including working DNS adminstration) was wiped (well preserved into my versioning control system, subversion) and I first started to design the application (read my previous post on why i might be doing this, it’s my job now!) and fill in requirements. Justin (my partner at JR-Hosting.nl, heh consider buying one of our products, it makes our world better, or at least mine haha) proposed that he can help with the frontend things, as long as I produce a working backend.

The entire idea is to store all information in a database (What else is new, we all do that!); extract it periodically and write it to flat files. That way the used system does not rely on the information retrieval speed, nor does it rely on databases in general.

There are different configurations for each machine in the cluster, like mail-relay settings, dns duplication etc. I am considering: Apache, (Bind or PowerDNS), ProFTPD, Exim, Postfix (incoming filters, then drop to exim since that has flexible delivery locations), MySQL, PostgreSQL, etc, all build on my FreeBSD servers.

If you would like to propose some ideas, just let me know and I will see what I can do. Remember that I just recently started recoding the application and that basically only a ”design.txt” is there, and some simple backend scripts are written. It takes time, it will take time, it wont be done yesterday, yadayada. But it feels good to write again!

We (lemar and I) were both new to this kind of work and the way it is handled, and I think we are doing a really good job so far. Things are not always great, but then we sit together one way or the other, and choose to make the fogg less foggy and clarify a few things.

We already have established one of the smaller goals of our project, and more to come very quickly. I just hope that the partner that we are doing this for, is as happy with the situation as we are. but I think we are fine

Anyway; I will try to blogpost a little more often, show my grumpy feelings about the decreasing privacy, tell happy things (like this one) and well whatever pops to mind.

Some difficulties with the replacement procedure (follow this, get a different ticket within the box, needing to get the arrangement with the carrier yourself) etc. I am now running on a fine working (so far at least) version2 WAP4410N.

Hurray for Cisco for their continued support!