[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/HowTo/TestInstallVirtualMachine" by WolfgangSchweer

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianEdu/HowTo/TestInstallVirtualMachine" page has been changed by WolfgangSchweer:
https://wiki.debian.org/DebianEdu/HowTo/TestInstallVirtualMachine?action=diff&rev1=22&rev2=23

Comment:
remove outdated information abot GOsa issue (occurred temporarily in Wheezy).

  === Set up a thin client ===
  In VirtualBox GUI, create a new machine for a thin client. The most easy way is to clone the ws1 image, and change the "NAT Network" to "thinclient". Recommended values for memory is 1024 MB RAM, 512 MB RAM is minimum. Give it a name (for example "tk1"), 1024 MB RAM and no hard drive. After creation, change settings. On System, allow the machine to boot from network in the Boot Order list. Under Network, Adapter 1, select  "NAT Network" and the correct network ("thinclient" in this example). You might change the MAC address by pressing the two arrow circle under the Advance menu. Given that the main and thin client server already runs in a virtual machine, just start the wk1 virtual machine, and it should start. Easy peacy. 
  
- == NB: Fixing GOsa² login ==
- 
- 
- After investigating further it seems to be that the mechanism using encrypted passwords in gosa.conf is failing now.
- 
- (As far as I know the random cleartext password generated during setup  is encrypted using gosa-encrypt-passwords and a file gosa.secrets is generated to let apache2 cope with the encrypted passwords.)
- 
- This seems to work getting an upgraded Wheezy main-server working again (no need to generate a new gosa.conf):
- 
-  1. sudo cat /dev/null > /etc/gosa/gosa.secrets. 
-  1. This can be done running 'sudo cat /dev/null > /etc/gosa/gosa.secrets' in a command console. 
-  1. take the random cleartext password from gosa.conf.orig and put it instead of the encrypted long one into gosa.conf (actually twice: adminPassword and snapshotAdminPassword). 
-  1. You can use 'pico' text exitor in the command shell doing that on the server which runs on VirtualBox. E.g copying the original adminPassword and snapshotAdminPassword from gosa.conf.org by using the 'sudo less /etc/gosa/gosa.conf.org' command in the server command console, and put that password in the gosa.conf file by using 'sudo pico /etc/gosa/gosa.conf'. 
-  1. restart apache2 with 'sudo serice apache2 restart' in the server command console. 
- 
- From a security point of view it's probably more than dubious...
- Maybe gosa-encrypt-passwords has to be adjusted. 
-