Urgent.News

What's breaking now, across thousands of outlets.

Tech

Tailscale device tags are identities, not deployment labels

Tailscale device tags are identities, not deployment labels Tags in Tailscale give a device an identity separate from the user who enrolled it. The tag then participates in access control, grants, subnet routers, and other policy decisions. That makes a tag an authorization object. Treating tag:prod as a harmless deployment label can give a device more access than its owner intended. The policy…

Tailscale device tags are identities and not deployment labels, according to Dev.to. These tags provide a device with an identity separate from the user who enrolled it and are used in access control, grants, subnet routers, and other policy decisions, making a tag an authorization object. The report advises reviewing tag names for purpose and environment, avoiding broad tags, and assigning ownership to narrow and accountable teams.

It also suggests treating tags as security groups and reviewing enrollment, ownership, and the devices carrying each tag. Additionally, the report emphasizes the importance of distinguishing tags from user identity and performing thorough testing before rolling out policy changes.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How a Live Unsaved-Changes Diff Works in a VS Code Extension

| Baselines, Myers line diffs, debouncing, undo/redo, and the edge cases behind SavePoint Diff's gutter markers. I recently shipped SavePoint Diff , a VS Code extension that shows gutter markers for…

  • SavePoint Diff highlights unsaved changes with gutter markers
  • Baseline captures last saved content of each file
  • Performance optimized with debounce time for diffing

Git seance: I let deleted functions speak from beyond the grave (with local Gemma)

This is a submission for the Hacktoberfest Open-Source AI Challenge: Ghost in the Machine What I Built Every repository is a graveyard.

  • Script reads repository's git history to summon deleted functions
  • Identifies functions never returned, reveals writer, addition date, removal commit
  • Demonstrated on psf/requests repo, uncovered seven "ghosts" from last 400 commits

More from Friday 30 October →