Export or remove the CA#

The Certificates dialog has two more controls beyond trust: Export and Delete. Both controls are available in the Not trusted state and the Trusted state.

Export#

Export writes the GraphDagger CA to a file you can install on another device. A native save dialog asks where to put it.

Use this when you want to:

• Capture HTTPS traffic from a phone, tablet, or other machine on the same network as GraphDagger via Remote Device.
• Install the CA on a colleague's machine for a shared debugging session.
• Keep the CA file alongside a project so anyone can install it.

The file holds the public CA only. The private key never leaves GraphDagger, so nobody can use an exported file to issue rogue certificates anywhere else.

Delete#

Delete removes the CA entirely. The current state goes back to Not generated, and the Generate certificate button reappears.

To reverse this, you must generate a new CA. You cannot reverse it from the device side. Anything that trusted the old CA stops trusting it, because the file is gone. Anything that the old CA signed becomes unverifiable.

Use Delete when:

• You want a clean state to share with a teammate.
• The CA is old and you want to rotate it.
• You stopped using HTTPS interception and want to leave no traces.

What removal affects#

Existing captures stay intact. Future HTTPS interception fails with a missing-certificate error until you generate and trust a new CA.

You also need to update every device that trusted the old CA. Remove trust on each device. You do not have to delete the certificate file by hand.