Re: [PATCH] Delete cryptoloop

From: Bill Davidsen (davidsen_at_tmr.com)
Date: 07/27/04

  • Next message: Marcelo Tosatti: "Re: "swap_free: Unused swap offset entry 00000100" but no crash?"
    To: linux-kernel@vger.kernel.org
    Date:	Tue, 27 Jul 2004 15:47:22 -0400
    
    

    Walter Hofmann wrote:
    > You wrote on linux.kernel:
    >
    >>dpf-lkml@fountainbay.com wrote:
    >>
    >>>Hopefully someone else will follow up, but I hope I'm somewhat convincing:
    >>
    >>Not really ;)
    >>
    >>Your points can be simplified to "I don't use cryptoloop, but someone else
    >>might" and "we shouldn't do this in a stable kernel".
    >>
    >>Well, I want to hear from "someone else". If removing cryptoloop will
    >>irritate five people, well, sorry. If it's 5,000 people, well maybe not.
    >
    >
    > I use cryptoloop and I would be really annoyed if it disappeared in
    > the stable kernel series. Besides, I read in another mail in this thread
    > that dm-crypt will not work with file-based storage (I'm using
    > cryptoloop on a file), and that it is new and potentially buggy.
    >
    > I'm really surprised that people here argue that dm-crypt doesn't get
    > enough testing so cryptoloop has to go to force people to test dm-crypt
    > with their valuable data. This is all upside-down. First dm-crypt has to
    > be stable, safe and feature-complete, then people can convert their data
    > to dm-crypt and only then can cryptoloop be deleted.

    Not to mention working with mount... That would be good if we didn't
    have to train people, change scripts, etc.

    -- 
        -bill davidsen (davidsen@tmr.com)
    "The secret to procrastination is to put things off until the
      last possible moment - but no longer"  -me
    -
    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: Marcelo Tosatti: "Re: "swap_free: Unused swap offset entry 00000100" but no crash?"

    Relevant Pages

    • Re: 2.6.3-mm1
      ... >> The target already takes an offset into the device, so you have what you want. ... dm-crypt has the same vulnerabilities as cryptoloop? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Delete cryptoloop
      ... why not adding on option for DEPRECATED code? ... you'd just have to migrate cryptoloop into this DEPRECATED ... >> Ditching cryptoloop completely in 2.7 after dm-crypt ... > To unsubscribe from this list: ...
      (Linux-Kernel)
    • Re: [PATCH] Delete cryptoloop
      ... > cryptoloop on a file), and that it is new and potentially buggy. ... Device-Mapper (and thus dm-crypt) can only create mappings on block-devices. ... dm-crypt on top of this loop device. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Delete cryptoloop
      ... Dropping cryptoloop should ... dm-crypt and cryptoloop share the same on-disk format. ... absolutely no security gain by switching to dm-crypt. ... an attacker is able to find two identical cipher blocks on disk, ...
      (Linux-Kernel)
    • Re: [PATCH] Delete cryptoloop
      ... This seems to be a discussion about cryptoloop vs dm-crypt. ... point of view there is zero reason to switch. ... robustness of kernel implementation, together with the idea that we ...
      (Linux-Kernel)