380795 – sys-fs/cryptsetup: dm-crypt-start.sh: get keys via custom pipe

Bug 380795 - sys-fs/cryptsetup: dm-crypt-start.sh: get keys via custom pipe

Summary: sys-fs/cryptsetup: dm-crypt-start.sh: get keys via custom pipe

Status:	RESOLVED DUPLICATE of bug 357227

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-08-26 23:30 UTC by Leho Kraav (:macmaN @lkraav)
Modified:	2015-04-12 22:18 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
cryptsetup-1.1.3-r3-pipe-support.patch (cryptsetup-1.1.3-r3-pipe-support.patch,1.96 KB, patch) 2011-08-26 23:32 UTC, Leho Kraav (:macmaN @lkraav)	Details \| Diff
0001-get-keys-via-custom-pipe-v2.patch (0001-get-keys-via-custom-pipe-v2.patch,2.97 KB, patch) 2011-08-29 16:59 UTC, Leho Kraav (:macmaN @lkraav)	Details \| Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Leho Kraav (:macmaN @lkraav) 2011-08-26 23:30:28 UTC

Adds possibility to dynamically build keys for unlocking devices

Reproducible: Always

Comment 1 Leho Kraav (:macmaN @lkraav) 2011-08-26 23:32:08 UTC

Created attachment 284757 [details, diff]
cryptsetup-1.1.3-r3-pipe-support.patch

Comment 2 SpanKY gentoo-dev

2011-08-28 22:46:06 UTC

Comment on attachment 284757 [details, diff]
cryptsetup-1.1.3-r3-pipe-support.patch

documentation belongs in the conf.d file, not in the patch header

Comment 3 Leho Kraav (:macmaN @lkraav) 2011-08-29 16:59:53 UTC

Created attachment 285027 [details, diff]
0001-get-keys-via-custom-pipe-v2.patch

good point. is this better?

Comment 4 Leho Kraav (:macmaN @lkraav) 2011-09-23 15:26:00 UTC

any progress here SpankY?

Comment 5 SpanKY gentoo-dev

2015-04-12 22:18:48 UTC


*** This bug has been marked as a duplicate of bug 357227 ***