http://bugzilla.novell.com/show_bug.cgi?id=557761 http://bugzilla.novell.com/show_bug.cgi?id=557761#c1 J. Daniel Schmidt <jdsn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #1 from J. Daniel Schmidt <jdsn@novell.com> 2009-11-23 18:03:26 UTC --- (In reply to comment #0)

The generated certificate has CN : localhost.suse.de O: not set OU: not set

We do not know what "Organization" or "Organizational Unit" will use the appliance. That's why it is not set. Not setting this is not an error.

1. The hostname should be better. Ideally, create the certificate only after network is up and a proper hostname is assigned. Or use 'webyast'.

Thats what my intent was. Because of that I hooked the certificate creation to the rc-script of yastwc. But then you can not start yastwc until network is up. Chicken-egg problem. Or the user must ssh to the appliance and start yastwc manually when network is up (maybe needs to configure network manually first, too). As a result of this I just got this: bug #557752. The original behaviour was exactly as you described: only create a certificate if there is a FQDN available and until then do not start yastwc. This was regarded as a P1 bug. So not matter what way you choose, you have to live with one backdraw. 1. no certificate at all, and no yastwc running 2. Have a certificate in any case, but maybe with a non-FQDN hostname I think 2) is the best option in this case and fixed it accordingly.

2. O should not be empty 3. OU should not be empty

Why? It is very common to not set fields that do not apply. I'll close this one as duplicate of bug#557752 as it deals with the same issue, just looking at it from the other side. *** This bug has been marked as a duplicate of bug 557752 *** http://bugzilla.novell.com/show_bug.cgi?id=557752 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557761 http://bugzilla.novell.com/show_bug.cgi?id=557761#c3 J. Daniel Schmidt <jdsn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #3 from J. Daniel Schmidt <jdsn@novell.com> 2009-11-24 10:56:45 UTC --- (In reply to comment #2)

The bug is not so much about technical issues but about the impression WebYaST has on our target group.

Yes, and thats what concerns me.

As an unexperienced Windows user, I would be scared by all the warnings Firefox shows me.

Its the aim of such warnings to warn. There will always be warnings in Firefox unless the user/admin implments a certificate that is trusted by Firefox by default. This is something we can not do. And until then Firefox will mark this page as untrusted. This is the idea behind SSL, trust and security. Its a security issue the user has to be made aware of. Any other behaviour would simulate that everything is ok, secure and trusted. The best thing we can do is to create a self-signed certificate, thats what we do. But there will always be warnings - we can not prevent this. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557761 http://bugzilla.novell.com/show_bug.cgi?id=557761#c5 --- Comment #5 from Klaus Kämpf <kkaempf@novell.com> 2009-11-24 14:05:33 UTC --- Simply enter reasonable values like "WebYaST" or "To be defined by appliance vendor". -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557761 http://bugzilla.novell.com/show_bug.cgi?id=557761#c7 J. Daniel Schmidt <jdsn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #7 from J. Daniel Schmidt <jdsn@novell.com> 2009-11-24 15:16:57 UTC --- Fixed in version 0.0.21 and submitted to OBS. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.