On Fri, 12.04.13 09:45, har...@redhat.com (har...@redhat.com) wrote:
From: Harald Hoyer har...@redhat.com
cryptsetup itself has no timeout as default from the beginning. So the
default timeout has been 0 from the beginning.
Makes sense I guess. Applied.
Also added a comment to crypttab(5)
From: Harald Hoyer har...@redhat.com
cryptsetup itself has no timeout as default from the beginning. So the
default timeout has been 0 from the beginning.
https://bugzilla.redhat.com/show_bug.cgi?id=949702
---
src/cryptsetup/cryptsetup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
