Slashdot Mirror

← Back to Stories (view on slashdot.org)

BSD User Groups?

Posted by timothy on from the quest-for-bugs dept.

*no comment* writes "Deadly.org has an article running that started out as a call for Seattle OpenBSD people to start a local usergroup, but has since turned into a thread for people all over the country looking for people."

2 of 32 comments (clear)

  1. Re:BSD and USA by cant_get_a_good_nick · · Score: 3, Informative

    Hmm? a whois on freebsd.org brings up Oregon, which is still in the states last I checked. OpenBSD is in Canada because of stupid crypto laws.

  2. Re:BSD and USA by Guy+Harris · · Score: 2, Informative
    Isn't OpenBSD in canada because thats where Theo De Raadt lives?

    That might be part of the reason, but this item suggests it's not the only reason:

    Why do we ship cryptography?

    In three words: because we can.

    The OpenBSD project is based in Canada.

    The Export Control List of Canada places no significant restriction on the export of cryptographic software, and is even more explicit about the free export of freely-available cryptographic software. Marc Plumb has done some research to test the cryptographic laws.

    Hence the OpenBSD project has embedded cryptography into numerous places in the operating system. We require that the cryptographic software we use be freely available and with good licenses. We do not directly use cryptography with nasty patents. We also require that such software is from countries with useful export licenses because we do not wish to break the laws of any country. The cryptographic software components which we use currently were written in Argentina, Australia, Canada, Germany, Greece, Norway, and Sweden.

    When we create OpenBSD releases or snapshots we build our release binaries in free countries to assure that the sources and binaries we provide to users are free of tainting. In the past our release binary builds have been done in Canada, Sweden, and Germany.

    OpenBSD ships with Kerberos IV and Kerberos V included. The two codebases we use are the exportable KTH-based release from Sweden. Our X11 source has been extended to make use of Kerberos as well.