Christoph Badura wrote: > On Thu, Dec 27, 2018 at 10:41:55PM +0000, Alexander Nasonov wrote: > > Perhaps the simplest change would be to pass an unresolved (original) > > name when composing a paramsfile. E.g. > > > > /etc/cgd/NAME=mylabel > > /etc/cgd/ROOT.e > > Alas, this will break existing installations that e.g. use /etc/cgd/dkNN when > using NAME=label in fstab.
You can't use the same dkNN in fstab and in cgd.conf because mount will refuse to mount an encrypted partition. I think it will only break setups that use NAME=label in _cgd.conf_ and don't specify a paramsfile. These setups are rare because NAME=label syntax was documented only a couple of days ago ;-) Though, some people may have figured it out before me. > For compatibility it may be necessary to try the resolved named when the > unresolved form does not exist. > > I would prefer /etc/cgd/mylabel, btw. Yeah, I don't like /etc/cgd/NAME=mylabel either ;-) There are other considerations like handling weird labels like this one: NAME=../../../../etc/passwd Ok, lets keep the default as it is. Those who want a different name can always specify a paramsfile explicitly and choose their favourite naming convention. -- Alex