<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cccms/app/controllers/elevations_controller.rb, branch master</title>
<subtitle>[no description]</subtitle>
<id>http://erdgeist.org/gitweb/cccms/atom?h=master</id>
<link rel='self' href='http://erdgeist.org/gitweb/cccms/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://erdgeist.org/gitweb/cccms/'/>
<updated>2026-08-01T00:39:59Z</updated>
<entry>
<title>Show and extend the elevation window</title>
<updated>2026-08-01T00:39:59Z</updated>
<author>
<name>erdgeist</name>
<email>erdgeist@erdgeist.org</email>
</author>
<published>2026-08-01T00:39:59Z</published>
<link rel='alternate' type='text/html' href='http://erdgeist.org/gitweb/cccms/commit/?id=6df48c1413a14516e7ee8919f33fbc13f0141966'/>
<id>urn:sha1:6df48c1413a14516e7ee8919f33fbc13f0141966</id>
<content type='text'>
A banner appears while elevated, counting down in minutes and carrying
extend and drop controls. Three extensions of 30 minutes are allowed, so
the window is at most two hours without a fresh code; a code resets the
budget. The countdown is advisory, the server-side check authoritative, so
it says "expired" rather than vanishing.

The post-login flash tells an admin the timer has started.
</content>
</entry>
<entry>
<title>Require a fresh second factor for user management</title>
<updated>2026-07-31T23:10:35Z</updated>
<author>
<name>erdgeist</name>
<email>erdgeist@erdgeist.org</email>
</author>
<published>2026-07-31T23:10:35Z</published>
<link rel='alternate' type='text/html' href='http://erdgeist.org/gitweb/cccms/commit/?id=f6c1f0f08f031778a491465d35ac694bfcdc12b0'/>
<id>urn:sha1:f6c1f0f08f031778a491465d35ac694bfcdc12b0</id>
<content type='text'>
Administrative actions are gated behind a 30-minute elevation window:
creating and retiring accounts, editing roles, clearing a second factor.
Reading the list is not gated, and content work is untouched.

elevated? is tied to is_admin?, so losing the role closes the window at
once. The window opens when the second factor verifies at login, so an
admin heading straight for user management is already elevated, and closes
on logout with the other session state. Five wrong codes end the session,
mirroring the login challenge.

users#update carries no elevation filter, since self-service reaches it;
the role field is gated in user_params instead and fails closed.
</content>
</entry>
</feed>
