Bug 32279 - secure apt not enabled with current 3.2 DVDs
secure apt not enabled with current 3.2 DVDs
Product: UCS
Classification: Unclassified
Component: General
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Erik Damrose
Lukas Walter
: interim-1
Depends on:
  Show dependency treegraph
Reported: 2013-08-21 10:52 CEST by Moritz Muehlenhoff
Modified: 2013-11-19 06:44 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2013-08-21 10:52:17 CEST
I made an installation with the DVD ucs_3.2-0-20130820153720-dvd-amd64.iso and after the completed installation (tested with base system and dc master), secure apt was disabled:

root@base:~# ucr search secure
update/secure_apt: no
 Only allow the installation of signed packages.
Comment 1 Stefan Gohmann univentionstaff 2013-08-21 10:56:26 CEST
base/univention-installer/scripts/79_apt.sh should consider testing.univention.de:

if [ "$repository_online_server" = "apt.univention.de" ] ||
   [ "$repository_online_server" = "updates.software-univention.de" ]; then
        univention-config-registry set update/secure_apt=yes
Comment 2 Erik Damrose univentionstaff 2013-08-21 14:21:56 CEST
Fixed in univention-installer 9.0.17-8.1089.201308211141
svn r43346
Rebuild DVDs.
No changelog entry for testing.univention.de, as official releases will never use it as repository server.
Comment 3 Lukas Walter univentionstaff 2013-08-22 11:40:55 CEST
Successfully reproduced the problem with the mentioned DVD.

Fixed in the current DVD (i386 and amd64)
Comment 4 Stefan Gohmann univentionstaff 2013-11-19 06:44:11 CET
UCS 3.2 has been released:

If this error occurs again, please use "Clone This Bug".