[pkg-cryptsetup-devel] new cryptsetup version breaks local setups

[Guilhem Moulin]

Hi Marc,

On Tue, 19 Jun 2018 at 13:10:29 +0200, Marc Haber wrote:
> first let me thank you for caring about cryptsetup and bringing the
> package up to date. The package was in dire need of some love and it is
> good that it got it.

Thanks for the kind words! :-)

> I am aware that I am using an internal interface, hence not a bug report
> but this message. I just want you to be aware that there are people
> using those internal interfaces that went away with this update which
> only touched a third-level version number.

Sounds like #901795.  I agree that it's a valid use case, and I'm now
thinking of exposing part of the script as a documented, public
interface.  It's probably no that many functions in the end, in fact I
can think only of two that might be useful

    - a function to loop through the system or initramfs crypttab(5),
      ignoring lines that are commented out and setting CRYPTTAB_* to
      proper values
    - a function to unlock a mapping (corresponding to a crypttab(5)
      line), using the CRYPTTAB_OPTION_keyscript output when this
      variable is set

(Feel free to extend the list.)
 
> I will have to adapt my scheme and hope that I can cope with that. And
> sadly, I do not have a solution to avoid those things in the future. Do
> you plan doing similiarly invasive changes in the near future or can I
> start my adaption work right now?

You might want to wait until the fix for #901795, as it'll probably some
further refactoring.  But not nearly as large as the 2:2.0.3-1 → 2:2.0.3-2
upgrade.

Cheers,
-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20180619/f3ca4b13/attachment.sig>