|
Bugzilla – Full Text Bug Listing |
| Summary: | Improving Encrypted drives, Bug 3 (mounting encrypted partitions with YaST) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | K Takahashi <iridis.p> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | VERIFIED NORESPONSE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | forgotten_xs3PtXj4XH |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
K Takahashi
2010-05-17 09:37:10 UTC
I tried reproduce this here but was not successful. As long as there is a mount point selected and format is set to "no" YaST2 should not allow you to continue without valid crypt password. If you enter the wrong password there should be a popup telling you the password might be wrong. When I enter the correct password after entering the wrong password (and clicking the error popup away) YaST2 corretly proceeds and sets up the encrypted device without calling luksFormat or mkfs. Probabyl I did something different than you. Please provide y2log files so that I can see what exactly happened. K Takahashi, could you please provide the requested information? If there is no response then the bug will be closed. OK, we've got a report plus an inability to reproduce and no response to a NEEDINFO for nearly 3 months. Closing with NORESPONSE. |