123365 – cryptsetup-luks-1.0.1-r1 doesn't read properly from stdin

Bug 123365 - cryptsetup-luks-1.0.1-r1 doesn't read properly from stdin

Summary: cryptsetup-luks-1.0.1-r1 doesn't read properly from stdin

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High major (vote)
Assignee:	Benjamin Smee (strerror) (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-02-19 04:56 UTC by Massimo Burcheri
Modified:	2006-02-28 04:05 UTC (History)
CC List:	0 users

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

Attachments
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 Massimo Burcheri 2006-02-19 04:56:10 UTC

cryptsetup-luks doesn't read properly from stdin. Therefore I can't get it working with pam_mount, which provides the key out of a ssl decrypted file.
http://forums.gentoo.org/viewtopic-p-3122951.html#3122951
Quite old report about the same problem:
http://groups.google.de/group/linux.debian.bugs.dist/browse_frm/thread/803929a178785be9

# echo $KEY >cache 
# cryptsetup -c aes-cbc-essiv:sha256 luksFormat /dev/hda5 cache 
   
 WARNING! 
 ======== 
  This will overwrite data on /dev/hda5 irrevocably. 
  Are you sure? (Type uppercase yes): YES 
   
# cryptsetup -d cache luksOpen /dev/hda5 _dev_hda5 
  key slot 0 unlocked. 
# cryptsetup remove _dev_hda5 
# echo $KEY |cryptsetup luksOpen /dev/hda5 _dev_hda5 
  Command failed: No key available with this passphrase.

Comment 1 Benjamin Smee (strerror) (RETIRED) gentoo-dev

2006-02-28 04:05:26 UTC

This is a problem relating to reading from a FD and terminating with \0 or \n.