Re: 2.6.0-test2+Util-linux/cryptoapi

From: Frank v Waveren (fvw_at_var.cx)
Date: 07/31/03

  • Next message: Martin J. Bligh: "[Bug 1016] New: Boot blocked on 2.6.0-test2"
    Date:	Thu, 31 Jul 2003 07:04:17 +0200
    To: James Morris <jmorris@intercode.com.au>
    
    

    On Thu, Jul 31, 2003 at 02:39:45PM +1000, James Morris wrote:
    > > Moving to the slightly more ontopic stuff for lk@vger: Is access to
    > > the cryptoapi algorithms exposed to userspace yet?
    > No, there is no point (apart from testing) unless the kernel API is
    > providing access to crypto hardware.
    Even if we don't have the drivers yet, the sooner it's available and
    in use the better, then we can always drop in hardware support later.
    (Still, I'm not volunteering for either job so I won't complain, just
    wondering if it had been done)

    > > Thirdly, has the encryption setup changed again since 2.4.x with hvr's
    > > testing cryptoapi stuff? I have a filesystem encrypted with 256 bits
    > > serpent, yet it won't decrypt using 2.6.0-test2 and util-linux 2.12.
    > The kerneli serpent implementation is incorrect (it's reversed, a common
    > implementation problem with this algorithm).
    Owch. But I assume this didn't sneak in since the testing cryptoAPI
    patches? Or have the algorithms been redone?

    > > Lastly: Why the move from a /proc/crypto directory containing files
    > > for all the algorithms to one monolithic /proc/crypto file? Isn't the
    > > former a lot nicer from the userspace programmer's point of view?
    > Possibly, although it's probably too late to change now for 2.6.
    But why was it ever changed to on big file in the first place?

    -- 
    Frank v Waveren                                      Fingerprint: 21A7 C7F3
    fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100            1FF3 47FF 545C CB53
    Public key: hkp://wwwkeys.pgp.net/fvw@var.cx            7BD9 09C0 3AC1 6DF2
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Martin J. Bligh: "[Bug 1016] New: Boot blocked on 2.6.0-test2"

    Relevant Pages

    • Re: CSP with foreign algorithm
      ... Unfortunately, the Microsoft CA, like most applications based on CryptoAPI, ... The GOST algorithms may not be used with a Microsoft CA ... Now we are finishing the CSP development in accordance to the CSP ...
      (microsoft.public.platformsdk.security)
    • Re: [OT] Firefox 3.0
      ... Again, FWIW, signcode uses MD5 or SHA1, both of which are public ... algorithms, I have no idea what Wise Install uses (or indeed, what ... Freely available versions of what MS calls the CryptoAPI are in easy to ... things like infinite precision maths and crypto algorithms. ...
      (uk.rec.motorcycles)
    • Re: How good an encryption algorithm is this?
      ... They've designed plenty of crypto algorithms ... But surely there are enough CryptoAPI examples to help you out, ... Using "I think I'll design my own crypto algorithm" is a bad starting ... > those higher up crackers are probably more into breaking standard algorithms ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: How good an encryption algorithm is this?
      ... They've designed plenty of crypto algorithms ... But surely there are enough CryptoAPI examples to help you out, ... Using "I think I'll design my own crypto algorithm" is a bad starting ... > those higher up crackers are probably more into breaking standard algorithms ...
      (microsoft.public.vc.language)
    • Re: 2.6.0-test2+Util-linux/cryptoapi
      ... > the cryptoapi algorithms exposed to userspace yet? ... > former a lot nicer from the userspace programmer's point of view? ... James Morris ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)