/**
 * Security Messages
 * Issue #179: Reverse proxy authentication recommendation
 * Issue #331: Updated to include --auth option
 * Shared warning constants for CLI commands (DRY principle)
 *
 * [SF-002] GitHub URLs imported from github-links.ts (DRY)
 */
/**
 * Warning message displayed when CM_BIND=0.0.0.0 and --auth is not enabled
 * Used by: init.ts, start.ts, daemon.ts
 * Issue #331: Added --auth as a recommended option
 */
export declare const REVERSE_PROXY_WARNING: string;
/**
 * Approval prompt shown before a public Cloudflare Quick Tunnel is created
 * (Issue #1937, R9 — design §6.4).
 *
 * Lives here, beside {@link REVERSE_PROXY_WARNING}, because it is the same kind
 * of statement: "this next step puts the machine somewhere it was not". Keeping
 * the two together is also what stops the wording from drifting into the
 * orchestrator, where a future refactor could quietly reword or skip it.
 *
 * The Provider never prints this. Selection and approval are the orchestrator's
 * responsibility (§6.2): a prompt inside a Provider would have to re-derive
 * interactive-vs-not per Provider, and its answer would be invisible to the
 * caller that has to honour `--yes`.
 */
export declare const QUICK_TUNNEL_APPROVAL_WARNING: string;
/** The yes/no question asked after {@link QUICK_TUNNEL_APPROVAL_WARNING}. */
export declare const QUICK_TUNNEL_APPROVAL_QUESTION = "Create a public Cloudflare Quick Tunnel now?";
/**
 * Refusal shown when approval cannot be asked for (no TTY) and `--yes` is absent.
 *
 * Defaulting to "yes" here would make a scripted invocation publish the machine
 * without anyone having said so, which is why this path is a CONFIG_ERROR
 * rather than a prompt-less approval.
 */
export declare const QUICK_TUNNEL_APPROVAL_REQUIRED = "Creating a public Quick Tunnel requires explicit approval. Re-run with --yes to approve it, or use --provider tailscale.";
//# sourceMappingURL=security-messages.d.ts.map