Cryptograss:Runbooks/A key is compromised - Revision history

JMyles: Verified bot edits (removed proposal markers)

2026-11-10T16:38:07Z

Verified bot edits (removed proposal markers)

Magent: AZ5 brake live (via update-page on MediaWiki MCP Server)

2026-11-08T02:15:34Z

AZ5 brake live (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 02:15, 8 November 2026
Line 4:		Line 4:
	{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}		{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. githouse also refuses their merge orders while they are banned (live since 8 Nov).		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. githouse also refuses their merge orders while they are banned (live since 8 Nov).
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ~~''Once maybelle-config#286 and magenta#426 are deployed,~~ githouse merges nothing during AZ5.''		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. githouse merges nothing during AZ5 (live since 8 Nov).
	# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}		# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}
	# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}		# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}

Magent: Brakes live (via update-page on MediaWiki MCP Server)

2026-11-08T02:15:32Z

Brakes live (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 02:15, 8 November 2026
Line 3:		Line 3:
	== 1. Brakes (minutes; no merge, no deploy) ==		== 1. Brakes (minutes; no merge, no deploy) ==
	{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}		{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ~~''Once maybelle-config#286 and magenta#426 are deployed,~~ githouse also refuses their merge orders while they are banned.''		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. githouse also refuses their merge orders while they are banned (live since 8 Nov).
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Once maybelle-config#286 and magenta#426 are deployed, githouse merges nothing during AZ5.''		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Once maybelle-config#286 and magenta#426 are deployed, githouse merges nothing during AZ5.''
	# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}		# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}

Magent: AZ5 reaches githouse: built, pending deploy (via update-page on MediaWiki MCP Server)

2026-11-08T00:22:29Z

AZ5 reaches githouse: built, pending deploy (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 00:22, 8 November 2026
Line 4:		Line 4:
	{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}		{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Once maybelle-config#286 and magenta#426 are deployed, githouse also refuses their merge orders while they are banned.''		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Once maybelle-config#286 and magenta#426 are deployed, githouse also refuses their merge orders while they are banned.''
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''~~Planned:~~ githouse merges nothing during AZ5.''~~\|by=Magent}}~~		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Once maybelle-config#286 and magenta#426 are deployed, githouse merges nothing during AZ5.''
	# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}		# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}
	# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}		# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}

Magent: Bans reach githouse: built, pending deploy (via update-page on MediaWiki MCP Server)

2026-11-08T00:22:28Z

Bans reach githouse: built, pending deploy (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 00:22, 8 November 2026
Line 3:		Line 3:
	== 1. Brakes (minutes; no merge, no deploy) ==		== 1. Brakes (minutes; no merge, no deploy) ==
	{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}		{{Bot_proposes\|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:\|by=Magent}}
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''~~Planned~~, ~~not built yet:~~ githouse also ~~refusing~~ their merge orders while they are banned.''~~\|by=Magent}}~~		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Once maybelle-config#286 and magenta#426 are deployed, githouse also refuses their merge orders while they are banned.''
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}
	# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}		# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}

Magent: The freeze, by its real path (via update-page on MediaWiki MCP Server)

2026-11-08T00:20:42Z

The freeze, by its real path (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 00:20, 8 November 2026
Line 5:		Line 5:
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Planned, not built yet: githouse also refusing their merge orders while they are banned.''\|by=Magent}}		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Planned, not built yet: githouse also refusing their merge orders while they are banned.''\|by=Magent}}
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}
	# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands: <code>~~magenta.sh freeze~~</code>~~''', from your own terminal, over SSH to maybelle as root~~. githouse merges nothing, from anyone, whatever memory-lane says, ~~until~~ root ~~lifts~~ it. ''~~Planned, not built yet~~.''\|by=Magent}}		# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''\|by=Magent}}
	# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}		# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}

Magent: Add the root-only freeze brake (plan section 10) (via update-page on MediaWiki MCP Server)

2026-11-07T23:56:44Z

Add the root-only freeze brake (plan section 10) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 23:56, 7 November 2026
Line 5:		Line 5:
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Planned, not built yet: githouse also refusing their merge orders while they are banned.''\|by=Magent}}		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Planned, not built yet: githouse also refusing their merge orders while they are banned.''\|by=Magent}}
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''\|by=Magent}}
			# {{Bot_proposes\|'''If memory-lane itself may be in someone else's hands: <code>magenta.sh freeze</code>''', from your own terminal, over SSH to maybelle as root. githouse merges nothing, from anyone, whatever memory-lane says, until root lifts it. ''Planned, not built yet.''\|by=Magent}}
	# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}		# {{Bot_proposes\|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.\|by=Magent}}

Magent: Justin chose no second admin (7 Nov) (via update-page on MediaWiki MCP Server)

2026-11-07T23:56:42Z

Justin chose no second admin (7 Nov) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 23:56, 7 November 2026
Line 18:		Line 18:

	== If the key is Justin's ==		== If the key is Justin's ==
	{{Bot_proposes\|That key is root on every server, the only admin, and a merger, so none of the brakes above can be trusted to stop it. What's left is outside the keys: Justin's GitHub account (its own password and second factor), where the org, its members and its deploy keys can be changed; and Hetzner's console, which reaches the servers without SSH. A second admin ~~in MOOD_ADMINS would let someone else pull the brakes in section 1. That's Justin's call~~.\|by=Magent}}		{{Bot_proposes\|That key is root on every server, the only admin, and a merger, so none of the brakes above can be trusted to stop it. What's left is outside the keys: Justin's GitHub account (its own password and second factor), where the org, its members and its deploy keys can be changed; and Hetzner's console, which reaches the servers without SSH. Justin chose no second admin for now (7 Nov).\|by=Magent}}

Magent: Runbook for a compromised key: brakes, removal, what happened (Plan section 10) (via create-page on MediaWiki MCP Server)

2026-11-07T22:58:24Z

Runbook for a compromised key: brakes, removal, what happened (Plan section 10) (via create-page on MediaWiki MCP Server)

New page

{{Bot_proposes|What to do, in order, when someone's SSH key, or a device signed in with it, may be in someone else's hands. Brakes first, then removal, then a look at what happened. Why it's in this order: [[Cryptograss:Moods/ramp/Plan]], section 10.|by=Magent}}

== 1. Brakes (minutes; no merge, no deploy) ==
{{Bot_proposes|An admin (MOOD_ADMINS: today only justin) does these from their own terminal:|by=Magent}}
# {{Bot_proposes|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. ''Planned, not built yet: githouse also refusing their merge orders while they are banned.''|by=Magent}}
# {{Bot_proposes|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. ''Planned: githouse merges nothing during AZ5.''|by=Magent}}
# {{Bot_proposes|'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.|by=Magent}}

== 2. Removal (a merge and redeploys) ==
# {{Bot_proposes|Take their <code>ssh_pubkey</code> out of <code>people</code> in maybelle-config's <code>hunter/ansible/inventory.yml</code>, and their name out of <code>githouse_mergers</code> if it's there. Make the pull request, then merge it with GitHub's button or <code>magenta.sh merge</code>.|by=Magent}}
# {{Bot_proposes|Redeploy hunter and maybelle. That removes their key from the servers, from Moods' allowed_signers and from githouse's merge_signers.|by=Magent}}

== 3. What happened ==
* {{Bot_proposes|The merges since the key could have been taken: <code>git log --first-parent --since=… production</code> (and <code>main</code>) in each repository, and on maybelle <code>/mnt/persist/githouse/git/.merges/</code> and <code>githouse.log</code> for orders signed in their name.|by=Magent}}
* {{Bot_proposes|pickipedia and arthel run the Jenkinsfile of whatever merged into <code>production</code> within minutes. Read Jenkins' runs since then.|by=Magent}}
* {{Bot_proposes|Their pushes: the branches under their name in githouse's <code>refs/heads/</code>, and in the ramp (under ▾).|by=Magent}}
* {{Bot_proposes|Then <code>magenta.sh AZ5 --lift</code>, if it was pulled.|by=Magent}}

== If the key is Justin's ==
{{Bot_proposes|That key is root on every server, the only admin, and a merger, so none of the brakes above can be trusted to stop it. What's left is outside the keys: Justin's GitHub account (its own password and second factor), where the org, its members and its deploy keys can be changed; and Hetzner's console, which reaches the servers without SSH. A second admin in MOOD_ADMINS would let someone else pull the brakes in section 1. That's Justin's call.|by=Magent}}

← Older revision		Revision as of 16:38, 10 November 2026
Line 1:		Line 1:
	~~{{Bot_proposes\|~~What to do, in order, when someone's SSH key, or a device signed in with it, may be in someone else's hands. Brakes first, then removal, then a look at what happened. Why it's in this order: [[Cryptograss:Moods/ramp/Plan]], section 10.~~\|by=Magent}}~~		What to do, in order, when someone's SSH key, or a device signed in with it, may be in someone else's hands. Brakes first, then removal, then a look at what happened. Why it's in this order: [[Cryptograss:Moods/ramp/Plan]], section 10.

	== 1. Brakes (minutes; no merge, no deploy) ==		== 1. Brakes (minutes; no merge, no deploy) ==
	~~{{Bot_proposes\|~~An admin (MOOD_ADMINS: today only justin) does these from their own terminal:~~\|by=Magent}}~~		An admin (MOOD_ADMINS: today only justin) does these from their own terminal:
	# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. githouse also refuses their merge orders while they are banned (live since 8 Nov).		# {{Bot_proposes\|'''<code>magenta.sh kick <name> --all --ban</code>''' signs out every device of theirs and bars their key from signing in to Moods. githouse also refuses their merge orders while they are banned (live since 8 Nov).
	# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. githouse merges nothing during AZ5 (live since 8 Nov).		# {{Bot_proposes\|'''If you're unsure who, or how far it went: <code>magenta.sh AZ5</code>.''' Everyone is signed out, the Moods are locked and no runner wakes anyone. githouse merges nothing during AZ5 (live since 8 Nov).
	# ~~{{Bot_proposes\|~~'''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''~~\|by=Magent}}~~		# '''If memory-lane itself may be in someone else's hands, freeze merging''': as root on maybelle, <code>touch /mnt/persist/githouse/etc/frozen</code>. githouse merges nothing, from anyone, whatever memory-lane says. To lift it, as root, <code>rm</code> the same file. A redeploy leaves it in place. ''Live once maybelle-config#286 is deployed; <code>magenta.sh freeze</code> is planned as a wrapper.''
	# ~~{{Bot_proposes\|~~'''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.~~\|by=Magent}}~~		# '''GitHub''': remove them from the org at https://github.com/orgs/cryptograss/people. Until githouse is how merges happen, an org member's session can merge on GitHub.

	== 2. Removal (a merge and redeploys) ==		== 2. Removal (a merge and redeploys) ==
	# ~~{{Bot_proposes\|~~Take their <code>ssh_pubkey</code> out of <code>people</code> in maybelle-config's <code>hunter/ansible/inventory.yml</code>, and their name out of <code>githouse_mergers</code> if it's there. Make the pull request, then merge it with GitHub's button or <code>magenta.sh merge</code>.~~\|by=Magent}}~~		# Take their <code>ssh_pubkey</code> out of <code>people</code> in maybelle-config's <code>hunter/ansible/inventory.yml</code>, and their name out of <code>githouse_mergers</code> if it's there. Make the pull request, then merge it with GitHub's button or <code>magenta.sh merge</code>.
	# ~~{{Bot_proposes\|~~Redeploy hunter and maybelle. That removes their key from the servers, from Moods' allowed_signers and from githouse's merge_signers.~~\|by=Magent}}~~		# Redeploy hunter and maybelle. That removes their key from the servers, from Moods' allowed_signers and from githouse's merge_signers.

	== 3. What happened ==		== 3. What happened ==
	* ~~{{Bot_proposes\|~~The merges since the key could have been taken: <code>git log --first-parent --since=… production</code> (and <code>main</code>) in each repository, and on maybelle <code>/mnt/persist/githouse/git/.merges/</code> and <code>githouse.log</code> for orders signed in their name.~~\|by=Magent}}~~		* The merges since the key could have been taken: <code>git log --first-parent --since=… production</code> (and <code>main</code>) in each repository, and on maybelle <code>/mnt/persist/githouse/git/.merges/</code> and <code>githouse.log</code> for orders signed in their name.
	* ~~{{Bot_proposes\|~~pickipedia and arthel run the Jenkinsfile of whatever merged into <code>production</code> within minutes. Read Jenkins' runs since then.~~\|by=Magent}}~~		* pickipedia and arthel run the Jenkinsfile of whatever merged into <code>production</code> within minutes. Read Jenkins' runs since then.
	* ~~{{Bot_proposes\|~~Their pushes: the branches under their name in githouse's <code>refs/heads/</code>, and in the ramp (under ▾).~~\|by=Magent}}~~		* Their pushes: the branches under their name in githouse's <code>refs/heads/</code>, and in the ramp (under ▾).
	* ~~{{Bot_proposes\|~~Then <code>magenta.sh AZ5 --lift</code>, if it was pulled.~~\|by=Magent}}~~		* Then <code>magenta.sh AZ5 --lift</code>, if it was pulled.

	== If the key is Justin's ==		== If the key is Justin's ==
	~~{{Bot_proposes\|~~That key is root on every server, the only admin, and a merger, so none of the brakes above can be trusted to stop it. What's left is outside the keys: Justin's GitHub account (its own password and second factor), where the org, its members and its deploy keys can be changed; and Hetzner's console, which reaches the servers without SSH. Justin chose no second admin for now (7 Nov).~~\|by=Magent}}~~		That key is root on every server, the only admin, and a merger, so none of the brakes above can be trusted to stop it. What's left is outside the keys: Justin's GitHub account (its own password and second factor), where the org, its members and its deploy keys can be changed; and Hetzner's console, which reaches the servers without SSH. Justin chose no second admin for now (7 Nov).