Univention Bugzilla – Full Text Bug Listing |
Summary: | Unclear how to disable the welcome screen | ||
---|---|---|---|
Product: | UCS | Reporter: | Philipp Hahn <hahn> |
Component: | System setup | Assignee: | UCS maintainers <ucs-maintainers> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | best, birkefeld, gohmann, grandjean, troeder |
Version: | UCS 4.0 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=39948 | ||
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: |
Description
Philipp Hahn
2015-10-30 08:38:06 CET
(In reply to Philipp Hahn from comment #0) > Today after reboot the Welcome Screen is shown again. > UCS-4.0-2 used for install, then updated to UCS-4.0-3 > Clicked away the welcome screen yesterday. You have to uninstall the package if you don't want to see it again: univention-remove univention-welcome-screen You can also disable it via the UMC services module! *I* know how to disable it, but it pops up over the KDE greeter ever time I boot the computer. That is very annoying. And there is no guide for the user how to finally get rid of it. It also consumes valuable resources (Bug #39241). We could easily add a "disable forever" button. I don't want to have the welcome screen on a system running KDM hiding the graphical login screen. I don't want to have the welcome screen running on my servers hosted in a dark compute center or with no monitor attached. I don't want to have the welcome screen running on my VMs wasting system resources. I don't want to get kernel/boot messages hidden by the welcome screen. Just my 2¢ PDN="cn=packages,cn=update,cn=policies,$(ucr get ldap/base)" udm policies/memberpackages create \ --position "$PDN" \ --set name=bug39678 \ --append memberPackagesRemove=univention-welcome-screen udm container/cn modify \ --dn "cn=memberserver,cn=computers,$(ucr get ldap/base)" \ --policy-reference "cn=bug39678,$PDN" For me a Firefox on a server is scary too, but if you look closely: it is running as 'nobody' and would be the 1st to be swapped out. So not really scary. Anyway, I do this also in all my VMs: ucr set welcome-screen/autostart=no I suggest: * add hint about ucr to welcome-screen * add hint about ucr to manual (only if not doing the above) (In reply to Daniel Tröder from comment #6) > For me a Firefox on a server is scary too, but if you look closely: it is > running as 'nobody' and would be the 1st to be swapped out. So not really > scary. WRONG: EC2 has *no* swap: # cat /proc/swaps Filename Type Size Used Priority "nobody" is *not* special in regard to swappiness Using <http://www.bitkistl.com/2015/04/firefox-enable-starting-of-scripts-and.html> <http://kb.mozillazine.org/Register_protocol> I was able to get a local shell as user "nobody". This is enough to use the host as a drone in a bot network or can be used as a stepping stone to get elevated permissions by finding a local root exploit. (In reply to Philipp Hahn from comment #7) > Using > <http://www.bitkistl.com/2015/04/firefox-enable-starting-of-scripts-and.html> > <http://kb.mozillazine.org/Register_protocol> > I was able to get a local shell as user "nobody". This is enough to use the > host as a drone in a bot network or can be used as a stepping stone to get > elevated permissions by finding a local root exploit. In this case we should give Bug #39241 more priority. I've set it to 4.1-0-errata. (In reply to Philipp Hahn from comment #7) > I was able to get a local shell as user "nobody". This is enough to use the > host as a drone in a bot network or can be used as a stepping stone to get > elevated permissions by finding a local root exploit. → Here is one: Bug #40245 @Philipp: Still an issue with the new welcome screen? (In reply to Florian Best from comment #10) > @Philipp: > Still an issue with the new welcome screen? No: the "press any key to go to console was enough". |