Slashdot Mirror


Crypto and IPSec Merged into 2.5

Corbet writes "Linus has just merged the new crypto API and IPSec implementation into his 2.5 BitKeeper tree. This is the first time that serious cryptographic code has made an appearance in the mainline kernel, and it will hopefully lead to more secure communications for all Linux users in the future."

13 of 229 comments (clear)

  1. Kernel bloat ? by MosesJones · · Score: 4, Insightful

    This is great that these things are comming as standard in the kernel, but so many things are "standard" now its getting pretty large for joe-schmo average user who will get a full kitchen sink kernel with their distro.

    This is also great for creating products like VPN gateways et al, but is it time to consider a different structure for kernel builds, with modules being seperately managed with a smarter installation procedure.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:Kernel bloat ? by Alioth · · Score: 5, Insightful

      With kernel modules you don't need to have the stuff loaded *in* the kernel all the time. All the distros I've used recently only have the stuff essential to run in the kernel image in /boot - the rest is all modules.

    2. Re:Kernel bloat ? by LordHunter317 · · Score: 4, Insightful

      I can't believe everyone calles 32MB of source "bloat". 32 MB is small compared to soemthings on your system, like X, KDE, GNOME sources. And in a lot of way, the Kernel is a lot more featureful than any of those. X for example, has a lot of "bloat" due to its build system.

      Joe-Schmo is goign to use the binary kernel supplied by his Distribution anyway, and probably never upgrade it, until he goes and downloads a whole new ISO image. The actual running kernel stays really small due to the use of such things as MODULES, allowing only what is needed to be running at any given moment to run.

      Bitch Bitch Bitch. Stop bitchin' about stuff you really don't have any idea about. The kernel is for all intents and purposes, small, and is indcredibly featureful for its size. So deal.

  2. IPSec lets us get Win2k from the flank by GreatDave · · Score: 5, Insightful

    In my experience, Windows 2000's support for IPSec is one reason why it has snared a foothold in many businesses. Having IPSec in mainstream Linux distributions would let us cut Bill off at the pass.

    I hope we're not far from seeing adoption of Linux in places like the financial services industry. If the distributors can make IPSec painless to configure, Linux will make inroads in such industries very quickly.

    --
    "I am root. Bow before me." To this I say, "You are root, and you bear the sins of the world upon your shoulders."
    1. Re:IPSec lets us get Win2k from the flank by phorm · · Score: 5, Insightful

      Forget the "linux Vs windows" attitude for a moment, and lets just hope that the new linux kernel works nicely with the windows (bad or otherwise) implementation of IPSec for VPN, etc.

      You'll probably snag a lot more users by showing cross-OS compatability as opposed to desktop replacement. As in most cases, it would likely be linux server, windows desktop, with VPN being a nice communication feature in both.I know that I would like my VPN's to work properly between OS's, without the half-baked configurations in FreeSwan.

  3. Export Ramifications? by nurb432 · · Score: 4, Insightful

    Does this create any export ramifications since Linus ( and i assume the code he reviews/packages )is now located here in the states?

    Just curious.. i know how hard of a time everyone else ( like BSD ) has with this garbage.

    Information should never be restricted on the basis of governmental boundries. Phfft.

    --
    ---- Booth was a patriot ----
  4. Re:Keeping stuff away from terrorists? by DuBois · · Score: 5, Insightful
    No. Nobody can. Crypto can be used for good or ill, just like any self-defense tool. Keeping it out of the hands of "enemies" also keeps it out of the hands of people rebelling against our "enemies."

    Freedom of speech also implies freedom of anonymous, or even encrypted speech, a concept that politicians have destroyed completely with "campaign reform."

    --
    The IPCC has purposely engineered a massive scientific fraud.
  5. Re:If I want IPSec stuff by Teancom · · Score: 5, Insightful

    Well, seeing as this isn't FreeSWAN, maybe you want to restate your objections? I mean, complaining about FreeSWAN when talking about putting ipsec in the kernel, doesn't make much sense if it isn't FreeSWAN that they are using...

    But on the other hand, who wants to read the article when you can, instead, spout off and look like an idiot?

  6. Re:Too bad it's not Freeswan by The+Pim · · Score: 5, Insightful
    While I appreciate all the work that freeswan has done for us, I am much more confident for the long term in work done by the core Linux networking hackers. The freeswan guys seem much more concerned with making it work (in typical situations) than making it right, with the result that the implementation is horribly klugy.

    Two examples are the need for a "nexthop" parameter, when the kernel already has this information in its routing tables; and the need to turn off route filtering. Both make it clear that freeswan is not properly integrated (and if you look at the freeswan docs, you'll see that this general problem been on the "to fix" list for a long time).

    --

    The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  7. Re:Excellent - no more FreeSWAN patches by velkro · · Score: 5, Insightful

    Why no fork yet?

    Because it's a large project, it's really complex, and it's a bitch to keep up with things.

    I should know - I'm the author of Super FreeS/WAN, a pseudo fork with includes alot of patches (NAT-T, X.509 Certs, AES/Blowfish/etc... ) @ http://www.freeswan.ca/code/super-freeswan

    It takes a few hours a day to stay on top of things. One the major ones is user support. IPSec is not easy to configure currently, especially once you introduce X.509 certs & MS Windows clients using any number of clients. So there's hundred of questions about configs, how tos, etc...

    If you want to fork it, please, go ahead. Just remember that a fork isn't just the code - you take users with you.

  8. Three kinds of bloat by DickBreath · · Score: 5, Insightful

    One man's bloat is another man's features.

    Hypothetical: I can't believe OpenOffice is so bloated compared to EDLIN from MS-DOS!

    Maybe it's "feature loaded" instead of bloated? While it is true that you can use OpenOffice to duplicate tasks that you might have done in EDLIN, it is capable of so much more.

    There is another kind of bloat which is not caused by features. This kind of bloat does not appear to be present in Linux. The kind of bloat I'm talking about is caused by "optimization". I don't mean optimizing for fast code or small code, but optimizing for "release date". Hey Mr. Customer, would take that new spreadsheet upgrade six months sooner if it required 25% more computing resources to run? All consumers I know would answer Yes. So this is a type of optimization. Optimizing for development time instead of optimizing for computer resources. Given the current low and decreasing cost of computer resources, there is some balance of this that makes sense. Just as once upon a time the "bloat" and value of high level programming languages was hugely debated. Now everyone uses high level languages to optimize for development time. The fact that I could spend six extra months doing it smaller and faster in assembler doesn't matter. Well, today it's the same thing. I don't mean that bad code is written on purpose, just that development time is valued above comptuer resources and machine optimizations, profiling, etc. Again, Linux does not appear to "suffer" from this type of "optimization".

    Another type of bloat is just from plain bad programming. It was not a purposeful decision to optimize development time, it was just the the program is badly written. Linux does not appear to suffer from this kind of bloat either.

    --

    I'll see your senator, and I'll raise you two judges.
  9. bloat by budalite · · Score: 4, Insightful

    My un-favorite types of Bloat:
    - In Apps, Games, whatever, it would be a lot nicer to be able to add features, rather than have the whole bloated thing copied/downloaded/installed onto your drive. (Cygwin has a nice setup.exe program that actually lets the user *pick* what he wants *before* the download. Very nice.)
    - Programs that say "Standby while we figure out what system you are running" and then copy every bloated driver for every type system, and its various peripherals, that ever existed onto your hard drive, anyway. Maybe this is not a problem anymore with the huge disks that exists these days, but it does signify sloppy development work that is usually mirrored in the app. :{)||

  10. More Pervasive Insecurities? by brandido · · Score: 4, Insightful

    I am not very knowledgeable about security issues, but I am curious if the inclusion of security modules in the kernel will provide for a single point of failure. In other words, as more programs become dependent on the kernel module for security, if an exploit becomes available, will all these dependent programs become exploitable?

    I ask this specifically because of the problem the IE ran into, where it depended on security APIs from Windows, the Windows API had an exploitable bug, and ta-da, IE had an exploitable bug.
    --
    First Falcon-1 to orbit, then Falcon-9. Then I can die a happy man.