For my team, I manage several Linux auto-installations for RedHat & SLES. I have fairly stock autoyast.xml's that have been working quite well for a while. With SLES11SP2, I'm running into a new problem. As our add-on repository is for internal access only, we've never seen any value in signing our packages. I use the signature-handling flags to bypass the signing checks: <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> </general> With SLES11SP2 (beta3) autoyast attempts to retrieve the repomd.xml.asc and repomd.xml.key files anyway. This throws up a blocking error dialog. Am I doing something wrong or has this behavior changed? -- Douglas Parrish Programmer Dell | PG Customer Operations -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org