reassign 552273 libgcrypt11
thanks
Hey,
On 15/01/2010 Milan Broz wrote:
> >> reassign 551540 cryptsetup 2:1.1.0~rc2-1
>
> >> It seems that "cryptsetup luksOpen" fails when EUID != UID. In
> >> particular, this happens when it is run by pmount which is suid (I
> >> assume that the reporters abov
Milan Broz wrote:
>>> reassign 551540 cryptsetup 2:1.1.0~rc2-1
>
>>> It seems that "cryptsetup luksOpen" fails when EUID != UID. In
>>> particular, this happens when it is run by pmount which is suid (I
>>> assume that the reporters above ran pmount as non-root). If cryptsetup
>>> is run directl
>> reassign 551540 cryptsetup 2:1.1.0~rc2-1
>> It seems that "cryptsetup luksOpen" fails when EUID != UID. In
>> particular, this happens when it is run by pmount which is suid (I
>> assume that the reporters above ran pmount as non-root). If cryptsetup
>> is run directly, then it works, because
On Sat, Oct 24, 2009 at 11:52:36PM +0200, Vincent Fourmond wrote:
> I'm unsure whether this should be attributed to cryptsetup or pmount:
> maybe simply setting the real user ID to root before launching
> cryptsetup would do the trick. In principle, the security risk is hardly
> greater with UID
Hello,
Martin Orr wrote:
> reassign 551540 cryptsetup 2:1.1.0~rc2-1
> thanks
>
> It seems that "cryptsetup luksOpen" fails when EUID != UID. In
> particular, this happens when it is run by pmount which is suid (I
> assume that the reporters above ran pmount as non-root). If cryptsetup
> is r
reassign 551540 cryptsetup 2:1.1.0~rc2-1
thanks
It seems that "cryptsetup luksOpen" fails when EUID != UID. In
particular, this happens when it is run by pmount which is suid (I
assume that the reporters above ran pmount as non-root). If cryptsetup
is run directly, then it works, because nec
6 matches
Mail list logo
