Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://infosec.exchange/users/ryanc/statuses/111986363898137861">Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Saturday, 24-Feb-2024 21:05:06 JST</a><a href="https://infosec.exchange/@ryanc" title="ryanc@infosec.exchange"><img src="https://gnusocial.jp/avatar/174285-48-20231204225121.webp" width="48" height="48" alt="Ryan Castellucci :nonbinary_flag:" style="position: absolute; left: 0; top: 0;">Ryan Castellucci :nonbinary_flag:</a></section><article><p>For some reason, the fact that this works seems kinda cursed.</p><p>Using nginx to reverse proxy every device in a subnet based on wildcard DNS and certificate.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2756077#notice-5464793">In conversation</a><time datetime="2024-02-24T21:05:06+09:00" title="Saturday, 24-Feb-2024 21:05:06 JST">about 9 months ago</time> <span>from <span><a href="https://infosec.exchange/@ryanc/111986363898137861" rel="external" title="Sent from infosec.exchange via ActivityPub">infosec.exchange</a></span></span><a href="https://infosec.exchange/@ryanc/111986363898137861">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/2300086">screenshot with syntax highlightingserver {
  listen 198.51.100.1:443 ssl http2;
  # matches device-N.int.example.net where N is a number from 2 to 254
  server_name ~^device-(?&lt;octet&gt;[2-9]|[1-9][0-9]|1[0-9][0-9]2[0-4][0-9]|25[0-4])[.]int[.]example[.]net$;  ssl_certificate     /etc/ssl/chain/int.example.net.cer;
  ssl_certificate_key /etc/ssl/private/int.example.net.key;  location / {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $host;
    proxy_pass http://198.51.100.$octet;    proxy_cache off;
    proxy_cache_valid 404 5s;
    proxy_cache_valid 301 308 5m;
    proxy_cache_valid any 1m;
  }
}</a></label><br><a href="https://media.infosec.exchange/infosec.exchange/media_attachments/files/111/986/341/927/321/160/original/4cf24e26fe6b4cc1.png" rel="external">https://media.infosec.exchange/infosec.exchange/media_attachments/files/111/986/341/927/321/160/original/4cf24e26fe6b4cc1.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Saturday, 24-Feb-2024 21:05:06 JST Ryan Castellucci :nonbinary_flag:
For some reason, the fact that this works seems kinda cursed.
Using nginx to reverse proxy every device in a subnet based on wildcard DNS and certificate.
In conversationabout 9 months ago from infosec.exchangepermalink
Attachments
1. screenshot with syntax highlighting server { listen 198.51.100.1:443 ssl http2; # matches device-N.int.example.net where N is a number from 2 to 254 server_name ~^device-(?<octet>[2-9]|[1-9][0-9]|1[0-9][0-9]2[0-4][0-9]|25[0-4])[.]int[.]example[.]net$; ssl_certificate /etc/ssl/chain/int.example.net.cer; ssl_certificate_key /etc/ssl/private/int.example.net.key; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_pass http://198.51.100.$octet; proxy_cache off; proxy_cache_valid 404 5s; proxy_cache_valid 301 308 5m; proxy_cache_valid any 1m; } }
  https://media.infosec.exchange/infosec.exchange/media_attachments/files/111/986/341/927/321/160/original/4cf24e26fe6b4cc1.png

Public

Embed Notice

HTML Code

Corresponding Notice