http://bugzilla.suse.com/show_bug.cgi?id=949410 http://bugzilla.suse.com/show_bug.cgi?id=949410#c2 --- Comment #2 from Lukas Ocilka --- For some reason, I actually was NOT in dialog to enter NEW password because I had to write it only once. So the problem will be in some dialog handling that allowed me to do unsupported thing. Swap was not encrypted and I just wanted to [] Encrypt it - most probably without selecting to format. Yast should take care about telling me this will not work. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=949410 http://bugzilla.suse.com/show_bug.cgi?id=949410#c4 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aschnell@suse.com | |) | --- Comment #4 from Arvin Schnell --- Since you did not tell YaST to format the partition YaST assumes that it already contains an encrypted swap and you provide the correct password. In general encrypted devices cannot be detected as such without the password (only LUKS supports that). The only solution I see is to try to decrypt the device as soon as the password is entered. This requires testing for all encryption algorithm YaST supported in the past. Then the UI can inform the user about a failure right away. But it is not possible to distinguish between "wrong password" and "not an encrypted device". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=949410 http://bugzilla.suse.com/show_bug.cgi?id=949410#c6 --- Comment #6 from Lukas Ocilka --- Created attachment 651348 --> http://bugzilla.suse.com/attachment.cgi?id=651348&action=edit two swaps, 1st 512 Bytes One plain swap, the other LUKS-encrypted Here we can really tell whether the swap is encrypted -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=949410 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[TW 2015-10-02] Cannot set |[TW 2015-10-02] Cannot set |encryption on already |encryption on already |created SWAP (too |created SWAP without |short/easy password?): |explicit formatting: error |error -3016 |-3016 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=949410 http://bugzilla.suse.com/show_bug.cgi?id=949410#c9 --- Comment #9 from Arvin Schnell --- Yes, LUKS encryption can be detected since it has a header/signature. fdisk likely displays "Linux swap / Solaris" since the partition id is 82. And yes, during installation and update the is already code to unlock encrypted partitions. -- You are receiving this mail because: You are on the CC list for the bug.