Ticket #139 (closed task: fixed)

Opened 3 years ago

Last modified 3 years ago

mounting of configuration partition delayed

Reported by: lars Owned by: lars
Priority: lowest Milestone: cryptobox-cd 0.3.x
Component: live-cd Version: cryptobox-live-cd 0.3.0
Severity: normal Keywords: bootup mount configuration partition
Cc:

Description (last modified by lars) (diff)

during tests of the live-cd within an qemu environment, the method get_available_partitions in source:trunk/src/cryptobox/core/settings.py failed to retrieve the existing configuration partition

during the first website request, the configuration partition is mounted, as expected

this mysterious delay has an important side effect: "bootup" events of plugins cannot load the previously stored settings - thus they stay at their default values (e.g.: the network plugin does not reconfigure the interface)

I was unable to reproduce this behaviour inside of a uml environment. Maybe the problem is qemu-specific.

Attachments

Change History

Changed 3 years ago by lars

  • version changed from svn to cryptobox-server 0.3.3
  • description modified (diff)

Changed 3 years ago by age

Well, the question is: are you able to reproduce this with a burned CD?

Changed 3 years ago by lars

  • status changed from new to closed
  • resolution set to fixed

this was caused by an incomplete privilege dropping within the server wrapper script: only the uid was changed to the one of the cryptobox user - its group settings were not used, thus making it impossible to gain the necessary privileges for reading the partition names

fixed in [835]

Add/Change #139 (mounting of configuration partition delayed)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.