According to this article, Mike Lynn has found 15 new, more dangerous flaws in Cisco IOS software.
“Essentially there are more bugs, and they’ve gagged me from telling anyone the details of what they are,” Lynn said.

I have a fully functional Postfix server running Apache and MySQL.
As RoundCube’s webmail requires IMAP, I also installed the Dovecot IMAP server from the OpenBSD ports tree. Then, I unzipped RoundCube’s webmail package to my webroot, and in 5 minutes it was running and working properly on an OpenBSD-3.8-STABLE server. Check it out at RoundCube’s website.
This is a must-have webmail interface. (even tho it’s kinda RedHat-ish, I still like it!)
Plus, it’s completely skinnable with XHTML and CSS2.

I’ve just spent a few days out of town, and realised upon my return, that OpenBSD 3.8 has been released! yay!
I chose to use the “Upgrade without install media”,
not cause I couldn’t access the machine, but I can’t stand being in the server closet, standing there, installing something. waiting…
I should be able to supply the media, manually overwrite the system files, and re-boot to my new OS. (from the couch ; ) Well, now I can. (and I did!)
So, to begin, I verified that my 3.7-STABLE install was running all necessary patches, then followed this document found on OpenBSD’s site regarding upgrading from OpenBSD 3.7 to 3.8. It worked flawlessly, and now my dmesg happily reports:

OpenBSD 3.8 (PRINCETON) #0: Sun Nov  6 01:17:15 CST 2005
root@cryptednets.org:/usr/src/sys/arch/i386/compile/PRINCETON
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2 cache) 565 MHz
real mem  = 132489216 (129384K)
avail mem = 114262016 (111584K)

Here it is!

These UNIX Commands will help out if you need to log in to a foreign system,
and pkg_info just doesn’t work for you!
Thanks Unixguide! Who knew that ” instfix -i ” shows all installed patches on AIX? (not me)

This was posted using WordPressDash version 0.3.
It was written by the obviously talented Paniris Web development
It’s a very cool must-have widget for OS X 10.4. (aka. Tiger)
So, making use of the very cool Expose, (which gives the overlayed panel of tools you see in the screenshot below)

Now, posting to a WordPress blog is as easy as mousing into the right corner of my screen to bring up the dash board, and clicking “New Post”.

Thank you, Paniris, for your very excellent widget!

This is a work in progress, do not follow these directions without having the capability of continuing on your own.

Steps:

1. You need a working openbsd machine on which to compile and build ISO images.
2. Make a directory in which to keep the cd’s contents, such as /home/livecd or
   similar. If you can make this a separate partition, so you can boot it for testing, all the better.
3. Untar base37.tgz and etc37.tgz in this directory.
4. Make sure the kernel sources (/usr/src/sys) are installed on the machine.
5. cd into /usr/src/sys/arch/i386/conf and copy the kernel config file GENERIC to CDBOOT or similar.
6. edit the file CDBOOT. Replace the include of ../../conf/GENERIC with the contents of that file.
7. make the following changes to CDBOOT:
   1. add the options RAMDISK_HOOKS and MINIROOTSIZE=3560 to support ramdisks
   2. comment out the line config bsd swap generic, as there will be no disk to swap to
   3. add the line config bsd root on cd0c to allow for / on the cd
8. run the command “config CDBOOT”
9. cd into ../compile/CDBOOT and run make depend and then make
10. copy this kernel into /home/livecd
11. edit the file /usr/src/distrib/i386/common/Makefile.inc, replacing the lines

            strip ${.OBJDIR}/boot
            strip -R .comment ${.OBJDIR}/boot
    

    with the line

    strip --strip-all -R .comment -K cngetc bsd.strip
    

12. cd into /usr/src/distrib/i386/floppies
13. create the directory CDBOOT as a copy of ramdisk_cd
14. edit the makefile in CDBOOT, changing the line RAMDISK=RAMDISK_CD to RAMDISK=CDBOOT
15. do a make in /usr/src/distrib/crunch and then /usr/src/distrib, to setup some prerequisites, then do a make in /usr/src/distrib/i386/CDBOOT. copy cdrom35.fs to /home/livecd/boot.img, this is the image you need to make the cd properly bootable.
16. change /etcs to make booting work right
    1. Edit the CD version of /etc/rc to mount the floppy on /etc, then run
       /etc/rc off the floppy or run the installer if it doesn’t exist.
    2. edit the floppy version of /etc/rc to mount the appropriate filesystems.
    3. edit the CD version of /etc/fstab to include the cd and the floppy
    4. edit the floppy version of /etc/fstab to include the cd and floppy, and
       all ramdisk filesystems
17. Create an etc floppy, or include the installer script and related files.
18. Create the ISO image using the command: mkisofs -b cdrom37.fs -c boot.catalog -R -v -o OBSDCD.iso /home/livecd

So I’ve gotten this really *sweet* OEM firewall appliance on demo….
And I thought I’d put OpenBSD-3.7-STABLE onto it.
No hard drive or VGA port, just a com0, 256mb CompactFlash and 512mb of RAM…
Hmmm….
Serial console time….
yup. i guess i got the cable. ;P
So… I have my serial cable, plugged into the DB9 on the demo unit, and also to com0 on my laptop.
no dice. (or console redirection….) #$$%#@^@!!@#%$#!@

## Screw-driver time ##
Ok. I’ve gotten the cover off of this thing, and installed the not-supplied-but-overnight-shipped VGA cable.
(what are they, like $.59 in bulk? )
Monitor plugged in, CDROM drive perched precariously over the open system, USB keyboard plugged in, READY.
Into the BIOS, re-direct the console to com0, save and exit.
## End Screw-driver time ## (for now)

So, just to get an idea of what we’re working with, I installed a simple 3.7-STABLE system.
The 256mb compact flash was recognized as wd0, and so I installed to it as if it were a hard disk.
{swap} 32m
/ {remainder} ~209mb

I installed the following packages:
bsd
base37.tgz
etc37.tgz
misc37.tgz
comp37.tgz (just ’cause I wanted to see if it would fit)

It all fit with ~9mb left over. {cool} Obviously not very useful, as a noisy log would fill the disk rather quickly.
So, let’s build a bootable RAMDISK_CD and boot it from the flash.

We need a similar 3.7-STABLE x86-based build host, preferrably with plenty of drive space, for making the bootable RAMDISK_CD.

Think I’ll go set that up… (more later)

Piles of valuable information, a must read for any mail server admin.
http://www.flakshack.com/anti-spam

Taken directly from the OpenBSD FAQ

The standard OpenBSD kernel configuration (GENERIC) is designed to be suitable for most people. More people have broken their system by trying to tweak their kernel than have improved system operation. There are some people that believe that you must customize your kernel and system for optimum performance, but this is not true for OpenBSD. Only the most advanced and knowledgeable users with the most demanding applications need to worry about a customized kernel or system.

Some reasons you might want or need to build a custom kernel:

Nice bit of writing, guys. Keep up the good work! (and thanks for the help)

5.11.3 – My IPv6-less system doesn’t work!

Yes.
Please do not make modifications to the base system that you don’t
understand the implications of.
One “little” change in the kernel can have very large impact to the
entire rest of the system.
Please re-read this.