July 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312632] openSUSE Linux 12.1/LXDE: Create files with the right click mouse on my...
by fate_noreply＠suse.de 21 Jul '11

21 Jul '11

Feature added by: Genix Info (genixinfo) Feature #312632, revision 1 Title: openSUSE Linux 12.1/LXDE: Create files with the right click mouse on my... openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Genix Info (genixinfo) Partner organization: openSUSE.org Description: openSUSE Linux 12.1/LXDE: Create files with the right click mouse on my desktop programs installed on your system. -- openSUSE Feature: https://features.opensuse.org/312632

1 3

[New: openFATE 310154] Add all the programs and features also the maintenance of Parted Magic.
by fate_noreply＠suse.de 20 Jul '11

20 Jul '11

Feature added by: Genix Info (genixinfo) Feature #310154, revision 1 Title: Add all the programs and features also the maintenance of Parted Magic. openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Genix Info (genixinfo) Description: Add all the programs and also the features and maintenance characteristics of Parted Magic: http://forums.opensuse.org/english/get-help-here/looking-something-other-th… (http://forums.opensuse.org/english/get-help-here/looking-something-other-th…) -- openSUSE Feature: https://features.opensuse.org/310154

1 7

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 20 Jul '11

20 Jul '11

Feature changed by: Jiří Suchomel (jsuchome) Feature #312321, revision 16 Title: Replace blowfish with sha512 as password hash openSUSE Distribution: Implementation Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils * add support for sha512 to YaST (core, security, users) * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. #8: Lukas Ocilka (locilka) (2011-07-19 14:24:50) (reply to #6) Jiri, we already do support SHA-512 in YaST Users, don't we? Additionally, would you remove the blowfish option from YaST Users, please? #10: Jiří Suchomel (jsuchome) (2011-07-19 14:40:23) (reply to #8) Yes, we do have sha512, as a result of feature 309705, + #12: Jiří Suchomel (jsuchome) (2011-07-20 11:20:04) (reply to #8) + I've removed offering of blowfish from yast2-users and yast2-security. + The function call of cryptblowfish is still there, I'll remove it once + it is dropped from yast2-core #9: Lukas Ocilka (locilka) (2011-07-19 14:23:42) (reply to #3) These YCP built-ins are Arvin's speciality. Arvin, could you, please, do that change requested by Thorsten in comment #3? #11: Arvin Schnell (aschnell) (2011-07-19 17:38:42) (reply to #9) I will look at it when fate #312617 is finished (glibc provides salt functions). #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0

[New: openFATE 312630] openSUSE Linux 12.1: Make it Long Term Support (LTS)
by fate_noreply＠suse.de 20 Jul '11

20 Jul '11

Feature added by: Genix Info (genixinfo) Feature #312630, revision 1 Title: openSUSE Linux 12.1: Make it Long Term Support (LTS) openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Genix Info (genixinfo) Partner organization: openSUSE.org Description: openSUSE Linux 12.1: Make it Long Term Support (LTS) (https://wiki.ubuntu.com/LTS) . -- openSUSE Feature: https://features.opensuse.org/312630

1 6

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature changed by: Arvin Schnell (aschnell) Feature #312321, revision 15 Title: Replace blowfish with sha512 as password hash openSUSE Distribution: Implementation Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils * add support for sha512 to YaST (core, security, users) * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. #8: Lukas Ocilka (locilka) (2011-07-19 14:24:50) (reply to #6) Jiri, we already do support SHA-512 in YaST Users, don't we? Additionally, would you remove the blowfish option from YaST Users, please? #10: Jiří Suchomel (jsuchome) (2011-07-19 14:40:23) (reply to #8) Yes, we do have sha512, as a result of feature 309705, #9: Lukas Ocilka (locilka) (2011-07-19 14:23:42) (reply to #3) These YCP built-ins are Arvin's speciality. Arvin, could you, please, do that change requested by Thorsten in comment #3? + #11: Arvin Schnell (aschnell) (2011-07-19 17:38:42) (reply to #9) + I will look at it when fate #312617 is finished (glibc provides salt + functions). #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0

[New: openFATE 308423] CA Management Proposal: change alternative name
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature added by: Michael Calmer (mcalmer) Feature #308423, revision 1 Title: CA Management Proposal: change alternative name openSUSE-11.3: New Priority Requester: Important Requested by: Michael Calmer (mcalmer) Description: Currently the CA Management proposal detects a lot of alternative names which are added to the server certificate. These autodetected values cannot be changed. You need to remove the certificate and crerate a new one using the ca-management module, if something is wrong or not wanted. It would be good to have the possibility to change them at this time. -- openSUSE Feature: https://features.opensuse.org/308423

1 16

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature changed by: Jiří Suchomel (jsuchome) Feature #312321, revision 14 Title: Replace blowfish with sha512 as password hash openSUSE Distribution: Implementation Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils * add support for sha512 to YaST (core, security, users) * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. #8: Lukas Ocilka (locilka) (2011-07-19 14:24:50) (reply to #6) Jiri, we already do support SHA-512 in YaST Users, don't we? Additionally, would you remove the blowfish option from YaST Users, please? + #10: Jiří Suchomel (jsuchome) (2011-07-19 14:40:23) (reply to #8) + Yes, we do have sha512, as a result of feature 309705, #9: Lukas Ocilka (locilka) (2011-07-19 14:23:42) (reply to #3) These YCP built-ins are Arvin's speciality. Arvin, could you, please, do that change requested by Thorsten in comment #3? #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature changed by: Lukas Ocilka (locilka) Feature #312321, revision 13 Title: Replace blowfish with sha512 as password hash openSUSE Distribution: Implementation Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils * add support for sha512 to YaST (core, security, users) * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. + #8: Lukas Ocilka (locilka) (2011-07-19 14:24:50) (reply to #6) + Jiri, we already do support SHA-512 in YaST Users, don't we? + Additionally, would you remove the blowfish option from YaST Users, + please? + #9: Lukas Ocilka (locilka) (2011-07-19 14:23:42) (reply to #3) + These YCP built-ins are Arvin's speciality. Arvin, could you, please, + do that change requested by Thorsten in comment #3? #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature changed by: Ludwig Nussel (lnussel) Feature #312321, revision 12 Title: Replace blowfish with sha512 as password hash openSUSE Distribution: Implementation Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils - * add support for sha512 to YaST (core, security) - * Remove blowfish as option from YaST2 + * add support for sha512 to YaST (core, security, users) + * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0

[New: openFATE 312540] Number of filters provided in kmail
by fate_noreply＠suse.de 19 Jul '11

19 Jul '11

Feature added by: Frédéric BRACHOT (brachot) Feature #312540, revision 1 Title: Number of filters provided in kmail openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Frédéric BRACHOT (brachot) Partner organization: openSUSE.org Description: I wish I could define more than 8 conditions in kmail filters -- openSUSE Feature: https://features.opensuse.org/312540

1 2