Project

General

Profile

Actions
Copy link

Task #176

closed

Update the fstab to automatically mount /dev/null and /dev/urandom for use by Fossil in chroot mode

Added by Nawan 17 days ago. Updated 17 days ago.

Status:
Resolved
Priority:
Urgent!
Assignee:
Nawan
Category:
-
Target version:
Q4 2025
Start date:
Due date:
% Done:

100%

Estimated time:

Description

As with #164, I redeploy Fossil with chroot jail mode. However, the chroot jail that Fossil enters automatically cannot access /dev/null and /dev/urandom. That issue has been fixed but I need to find way to automatically mount /dev/null and /dev/urandom.

Actions
Copy link
 #1

Updated by Nawan 17 days ago

  • Target version set to Q4 2025
Actions
Copy link
 #2

Updated by Nawan 17 days ago ยท Edited

  • Subject changed from Automatically mount /dev/null and /dev/urandom for use by fossil to Update the fstab to automatically mount /dev/null and /dev/urandom for use by Fossil in chroot mode
  • Status changed from New to Resolved
  • % Done changed from 0 to 100
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/vda1 during installation
LABEL=root /               ext4    errors=remount-ro 0       1
/dev/urandom /var/lib/fossil/dev/urandom    none    bind    0    0
/dev/null /var/lib/fossil/dev/null    none   bind    0    0
Actions
Copy link

Also available in: Atom PDF