|
Bugzilla – Full Text Bug Listing |
| Summary: | Cryptoloop AES multi key broken | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Jensen <junk26> |
| Component: | Basesystem | Assignee: | Hendrik Vogelsang <hvogel> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Following the sample commands given in the losetup man page (these exact commands worked fine with SuSE Linux 10.0. Resulting error is: ioctl: LOOP_MULTI_KEY_SETUP_V3: Invalid argument ---excerpt from man page--- The following commands can be used as an example of using the loop device. dd if=/dev/zero of=/file bs=1k count=500 head -c 2925 /dev/random | uuencode -m - | head -n 66 \ | tail -n 65 | gpg --symmetric -a >/etc/fskey9.gpg losetup -e AES128 -K /etc/fskey9.gpg /dev/loop0 /file ... ---end excerpt--- Using similar commands modified for single-key mode has no problem.