core-admin/qubes-rpc-policy/qubes.GetDate.policy

## Note that policy parsing stops at the first match,
## so adding anything below "$anyvm $anyvm action" line will have no effect

## Please use a single # to start your custom comments

$tag:anon-vm	$anyvm	deny
$anyvm	$anyvm	allow,target=dom0
clock synchronization rewrite clock synchronization mechanism rewritten to use systemd-timesync instead of NtpDate; at the moment, requires: - modifying /etc/qubes-rpc/policy/qubes.GetDate to redirect GetDate to designated clockvm - enabling clocksync service in clockvm ( qvm-features clockvm-name service/clocksync true ) Works as specified in issue listed below, except for: - each VM synces with clockvm after boot and every 6h - clockvm synces time with the Internet using systemd-timesync - dom0 synces itself with clockvm every 1h (using cron) fixes QubesOS/qubes-issues#1230 2017-07-06 23:37:26 +02:00			`## Note that policy parsing stops at the first match,`
			`## so adding anything below "$anyvm $anyvm action" line will have no effect`

			`## Please use a single # to start your custom comments`

$tag:anon-vm $anyvm deny 2018-08-07 18:29:07 +02:00			`$tag:anon-vm $anyvm deny`
Add qubes.GetDate proxy service This enable two things: 1. Follow global clockvm setting, without adjusting qrexec policy. 2. Avoid starting clockvm by arbitrary VM. Fixes QubesOS/qubes-issues#3588 2018-03-02 20:39:28 +01:00			`$anyvm $anyvm allow,target=dom0`