Slashdot Mirror

← Back to Stories (view on slashdot.org)

MicroBSD 0.6RC2 Released

Posted by michael on from the size-is-everything dept.

RooTchO writes "Included in this release is the new Extended Security Features, Improved/Additional sysctl parameters. New binaries in this release are: pfradix, pfsyncd, aclctl, netacl, getfacl, setfacl and cgdconfig. We have added chrooted sshd, apache, bind. Special files to also see are /etc/sysctl.conf, /etc/acl.conf and /etc/sshd/sshd_conf. And many new other goodies :)))"

9 of 30 comments (clear)

  1. Re:What is it? by LumpyCartman · · Score: 5, Informative

    http://www.microbsd.net/doc/handbook/nutshell.html

  2. Re:What is it? by evil_pb · · Score: 2, Informative

    I believe for the embedded apps you want something more like PicoBSD. I think there are even small embedded systems being sold with that, but I'm not 100% sure. Their site should have a list of compatible hardware however.

  3. we dont need yaBSD. by mnmn · · Score: 2


    Yet Another BSD??

    IT claims securiy. I thought OpenBSD did fine. It claims small footprint. I though NetBSD did that job. It claims best features of Freebsd+Net+Open but I didnt find the token ring driver in it...

    FreeBSD unifying with NetBSD and OpenBSD would be news, but this really isnt.

    Look Ma! I glued this to that, and have a new OS. At the risk of sounding like a troll, I'll say this isnt a useful OS and its goals arent convincing at least to me. These developers can better spend their time enhancing the existing BSD's and moving features from one BSD to another. That wouldnt make news but would be more useful.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  4. Chrooted? by evilviper · · Score: 2

    What is CHROOTED SSHD? Does that mean each user runs their own SSHD chrooted to their own home directory? That might screw things up.

    Or was that refering to Privlidge Severation, and the author is clueless?

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:Chrooted? by benjamindees · · Score: 2

      I assume it just means that sshd now drops root priviledges after it binds to it's network port. This enables it to run securely under a chroot jail, since running programs as root in a jail enables a hacker to be able to "break out" if he/she can exploit a security hole in the program, and defeats the purpose of using chroot.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    2. Re:Chrooted? by evilviper · · Score: 2

      Well if sshd drops privlidges after it binds to a privlidged port, it can't authenticate users, as it would have no access to passwords, and it can't give users access to their home directories, as it would be chrooted.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:Chrooted? by evilviper · · Score: 2

      Yes, there are ways to check passwords without being root... I sincerely doubt that 99.9% of them would work if the user whom is trying to do the authentication is chrooted. At the very least, they would have to have an SUID executable to perform thauthentication, which would almost completely defeat the purpose of chrooting SSHd. Besides, sshd still wouldn't have access to user's home directories.

      Sounds like you need to do a little homework yourself.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    4. Re:Chrooted? by benjamindees · · Score: 2

      I would just point out that it does, in fact, seem possible to run ssh chroot as this document indicates. The user passwords and home directories would, of course, have to be included in the jail as well. It's not something that can be used for system administration, obviously.

      --
      "I assumed blithely that there were no elves out there in the darkness"
  5. ATTN: Web Pages That Suck by SecretAsianMan · · Score: 4, Interesting
    Well, my 15-second perusal of their site has thoroughly convinced me to steer clear of their project. I can figure out the "BSD" part of the name, but what does "micro" mean? Is it for embedded machines? Is it a floppy distro? Is it just a small distro? Maybe it is BSD for microcomputers, and they don't know about Free/Net/OpenBSD.

    The first thing I see when I go to the FreeBSD website is this:

    FreeBSD is an advanced operating system for x86 compatible, DEC Alpha, and PC-98 architectures. It is derived from BSD UNIX, the version of UNIX developed at the University of California, Berkeley. It is developed and maintained by a large team of individuals. Additional platforms are in various stages of development.
    In my 15-second perusal of the FreeBSD site, I get a good idea of what FreeBSD is. The only impression I get from the MicroBSD site is that they care more about blogwhoring than about writing any real software.

    Frankly, branching a new distro for some petty reason (I'm going to assume that's what it is since it is so damn hard to find out) instead of contributing tools and patches to an existing BSD seems just a tad too reminiscent of that other large free OS community.

    --

    Washington, DC: It's like Hollywood for ugly people.