Files
web/frontend/public/articles/tls-proxy-legacy-rescue.html
T
carlitosbondandClaude Sonnet 5 c9dc9617bd Add TLS proxy article, expand blog content, harden Grafana config
- Add new post/article: How a Small TLS Proxy Saved a Mobile Security
  Launch From a One-Year Delay, with matching OG/meta share page
- Mark tls-proxy-legacy-rescue article as visible and expand lessons
  learned section
- Add homelab and entertainment posts (Optiplex, survival sandboxes)
  to articles.js
- Harden Grafana: memory limits, rotated admin password, secure
  cookies, brute-force protection

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-05 21:19:58 +00:00

40 lines
2.4 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>How a Small TLS Proxy Saved a Mobile Security Launch From a One-Year Delay — Carlos Lugo</title>
<meta name="description" content="A legacy provisioning system couldn't speak modern TLS to a new security API. Here's how a lightweight reverse proxy closed the gap in days, not a year." />
<!-- Open Graph (LinkedIn, Facebook) -->
<meta property="og:type" content="article" />
<meta property="og:title" content="How a Small TLS Proxy Saved a Mobile Security Launch From a One-Year Delay" />
<meta property="og:description" content="A legacy provisioning system couldn't speak modern TLS to a new security API. Here's how a lightweight reverse proxy closed the gap in days, not a year." />
<meta property="og:url" content="https://carloselugo.com/articles/tls-proxy-legacy-rescue.html" />
<meta property="og:image" content="https://carloselugo.com/images/profile_rev2.png" />
<meta property="og:site_name" content="Carlos Lugo" />
<!-- Twitter/X card (harmless to include, some tools reuse it) -->
<meta name="twitter:card" content="summary" />
<meta name="twitter:title" content="How a Small TLS Proxy Saved a Mobile Security Launch From a One-Year Delay" />
<meta name="twitter:description" content="A legacy provisioning system couldn't speak modern TLS to a new security API. Here's how a lightweight reverse proxy closed the gap in days, not a year." />
<meta name="twitter:image" content="https://carloselugo.com/images/profile_rev2.png" />
<link rel="canonical" href="https://carloselugo.com/#article-tls-proxy-legacy-rescue" />
<!-- Human visitors get redirected straight into the real article on the SPA. -->
<meta http-equiv="refresh" content="0; url=/#article-tls-proxy-legacy-rescue" />
<script>window.location.replace('/#article-tls-proxy-legacy-rescue');</script>
<style>
body { font-family: -apple-system, BlinkMacSystemFont, sans-serif; background:#faf9f5; color:#201e1d;
display:flex; align-items:center; justify-content:center; min-height:100vh; margin:0; }
a { color:#ec3013; }
</style>
</head>
<body>
<noscript>
<p>Redirecting… If nothing happens, <a href="/#article-tls-proxy-legacy-rescue">read the article here</a>.</p>
</noscript>
</body>
</html>