cross
|
|
response 3 of 8:
| 
Sep 10 14:47 UTC 2010 |
I recently gave DragonFly BSD a whirl. I bought an HP "netbook" at
the PX here in Afghanistan to hack around with; it's the perfect size
to put into my assault pack when I go on missions, has good battery
life, and I can play with it when I've got some down time. I wanted
to have an environment where I could hack around and read books/papers
as PDFs and PostScript, or HTML. Specific requirements included
Emacs, the JVM, a solid Lisp environment, support for suspend/resume,
X, and the network.
Getting the computer was easy enough, though I had to buy a USB DVD
drive with it so I would have some way to load the operating system
from media. I have no *real* network access here (I can download
something to the office computer and burn it to a CD, but plugging a
non-government computer into a military network is a serious no-no).
Anyway, I downloaded the latest version of DragonFly and tried it
out. It installed, and looked pretty nice; HAMMER seemed like it
could be cool (though a friend of mine tells me he doesn't trust Matt
Dillon's intuition when it comes to implementation). The WiFi didn't
work, which was disappointing. Kerberos had been removed from the
base system, which was again disappointing. But the biggest
disappointment was that most of the 3rd party stuff I was interested
in using didn't support DragonFly: there was no SBCL, no Oberon, many
other languages and applications were missing. It was kind of sad,
really....
I finally ended up installing the latest release of FreeBSD, which
pretty much solved the hardware support issues, and for which I could
get pretty much all the software I was interested in. It's a shame;
DragonFly seemed lighter-weight than the others, has some interesting
ideas in it, and seems like it could be really cool. But lack of
application and hardware support is definitely keeping it back.
|
dtk
|
|
response 8 of 8:
|
Jan 7 05:46 UTC 2013 |
IEEE 802.1x is nice because it forces the edge device to authenticate,
and can be setup to use a certificate for authentication, which canbe
issued by a CA. This provides a high levelof assurance that the device
is a trusted/vetted device or that the operator of the device was able
to steal a client cert and impersonate that client effectively. Cisco's
ISE product helps to automate the dot1x management, and there are
several nice CA products, including one that comes with Windows 2008
and RedHat's Dogtag CA. -DTK
|