s. But currently
there are a few bugs with YaST expecting a signature to be there etc.
We will also provide tools for setting up your own signed and checksum-enabled
installation sources ASAP.
I'll keep you posted and will try to answer your questions. If you want to put
this information onto opensuse.org, I wouldn't object. ;-)
I'll try to update opensuse.org on my own as soon as possible, too.
Cheers
Joachim
--
Joachim Werner <[EMAIL PROTECTED]>
Project Manager Contracts, Migration, SDK
Novell, Linux R&D Nuernberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ept digitally
> signed software/updates" where the user should be able to review his
> trusted keys)
The default will be secure (at least on the enterprise products based on SUSE
Linux), but this can be switched off per installation sou
at I mean to say is: Shouldn't ``type="sha1"'' be used instead?
Yes, it should. But we didn't write that part of the YUM format, so we have to
keep "sha" to stay compatible for now. ;-)
> Regards,
> Ulrich
> P.S. Una
These pages will be updated as soon as I have more details on how you can
generate your own secure sources.
Cheers
Joachim
--
Joachim Werner <[EMAIL PROTECTED]>
Project Manager Contracts, Migration, SDK
Novell, Linux R&D
personal firewalls" on Windows. This is a long-term project, not
something we can change in the current SuSEfirewall by just adding
appropriate Samba rules.
Cheers
Joachim
--
Joachim Werner <[EMAIL PROTECTED]>
Project Manager Contracts, Migration, SDK
Novell, Linux R&D Nuernberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
