Dawnline 0.6.0
- Access rules fail closed: when the table cannot load, no device is loaded into the tunnels (the firewall alone would let every loaded device reach everything); an older table that survived a failed rebuild keeps its rules and a revoked device still leaves. The agent re-syncs within a minute when the table is gone - A change the router saved but could not put into effect (access rules that did not load, a server that refused its devices) is said in the admin UI instead of a plain "Saved" - The guard judges every packet, not only a connection's first: a change of access, a pause or a limit now cuts open connections too - Each server's home networks are its own: with several servers, "all home" on one no longer reaches the other's networks where firewall zones overlap - People limited to some home networks reach the router only on the addresses in those networks (LuCI and SSH on the main LAN stay closed) - Internet-only people can open their personal portal with the VPN on - Tunnel DNS reaches the resolver and the LAN's DNS from servers that do not forward to those zones on their own (Home-only names on servers without "like a home device", LAN DNS on servers with no home network) - A new personal link offers to remove the devices added through the old one, so a leaked link is really contained - Import and restore refuse an inconsistent file (devices with addresses outside their server, shared addresses, malformed keys, broken references); Health reports one, and the sync leaves such a device out instead of failing its server. A config write that did not reach flash is an error, not a silent success - Backups are kept per kind (nightly ones no longer push out manual or pre-delete ones), nightly and pre-change backups hold the config only, archives are written whole or not at all, and a failed nightly backup is logged. A restore no longer has its history overwritten by the agent's in-memory counters - Settings defaults and ranges come from one place (dawnline.schema) - Portal: anything not shaped like a personal link is answered by a shell before ucode starts (a scan on the root costs nothing); 4 portal processes at once instead of 16; a link may make 40 changes a quarter hour; over plain HTTP the page shows but configurations, new devices and new keys are refused with the HTTPS twin of the link; the connect sheet polls only while the first connection is awaited, with backoff, and stops once the link stopped working - Updates: after Dawnline's own package changes, a shell checks that LuCI reaches it and the agent runs, and puts the kept previous version back when they do not (automatic runs always keep it); the AmneziaWG module reload verifies rmmod and modprobe; installs check free space; on apk a reinstall that changed nothing is an error; uninstall.sh hands the update lock to the removal it calls; an upgrade restarts the service only where it was enabled; the release workflow pins the SDK images by digest and the actions by commit - AmneziaWG: features count only when both the tools and the kernel module have them; a server whose disguise this build cannot run (a 3.1 preset after a rollback to 2.0) is kept down and reported; Components tells 1.0 builds from 2.0 ones; `awg show dump` is parsed by shape; Maximum's DNS-shaped signature packets are made for each server and its keep-alive is a 25-35 s range - CI compiles every ucode file and runs the new tests/ucode unit tests (54 tests on the real libuci) in OpenWrt 24.10 and 25.12 rootfs containers; scripts/compile-ucode.sh does the same wherever ucode runs and scripts/ucode-container.sh locally with docker; lint-ucode checks POSIX regexes and module layering; a tag builds only after CI passes
This commit is contained in:
1 parent
2b98abdba4
commit
31a2065f05
70 files changed
+2008
-307
No files matched your search
@@ -18,11 +18,40 @@ export function invite(page: PersonPage) {
|
||||
void inviteCard(page.p, server);
|
||||
}
|
||||
|
||||
/**
|
||||
* A new link locks the old one out of the portal, but not what it already
|
||||
* got: devices added through it keep their tunnel. They are offered for
|
||||
* removal here, ticked, so a leaked link is really contained.
|
||||
*/
|
||||
export async function newLink(page: PersonPage) {
|
||||
const p = page.p;
|
||||
if (!(await confirmDialog('Create a new link?', 'The old link stops working right away.', 'Create new link', true))) return;
|
||||
const r = await attempt(() => api.personRegen(p.id), 'New link created');
|
||||
if (r?.link) await copyText(r.link, 'New link copied');
|
||||
const since = p.code_set ?? 0;
|
||||
const suspect = p.devices.filter((d) => d.created_by === 'portal' && d.created >= since);
|
||||
const boxes = suspect.map(
|
||||
(d) => E('input', { type: 'checkbox', id: `dl-rm-${d.id}`, checked: 'checked', 'data-id': d.id }) as HTMLInputElement,
|
||||
);
|
||||
const body: Node[] = [E('p', {}, 'The old link stops working right away.')];
|
||||
if (suspect.length)
|
||||
body.push(
|
||||
E('p', {}, 'Devices added through the old link keep working until they are removed. Remove them too:'),
|
||||
E(
|
||||
'div',
|
||||
{ class: 'dl-checklist' },
|
||||
suspect.map((d, i) => E('label', { for: `dl-rm-${d.id}` }, [boxes[i], ` ${d.name}`])),
|
||||
),
|
||||
);
|
||||
const go = async () => {
|
||||
const remove = boxes.filter((b) => b.checked).map((b) => b.dataset.id as string);
|
||||
const r = await attempt(
|
||||
() => api.personRegen(p.id, remove),
|
||||
remove.length ? `New link created, ${remove.length} device${remove.length === 1 ? '' : 's'} removed` : 'New link created',
|
||||
);
|
||||
if (!r) return;
|
||||
closeModal();
|
||||
if (remove.length) await page.refresh();
|
||||
if (r.link) await copyText(r.link, 'New link copied');
|
||||
};
|
||||
modal('Create a new link?', body, [cancelButton(), ' ', button('Create new link', go, 'negative')]);
|
||||
}
|
||||
|
||||
export function editNote(page: PersonPage) {
|
||||
|
||||
Reference in new issue
Block a user