<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>https</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/1040/feed"/>
    <updated>2026-09-17T09:38:06+00:00</updated>
    <id>https://links.biapy.com/guest/tags/1040/feed</id>
            <entry>
            <id>https://links.biapy.com/links/12686</id>
            <title type="text"><![CDATA[Slim]]></title>
            <link rel="alternate" href="https://slim.sh/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12686"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Local HTTPS Domains, Tunnels &amp;amp; Dev Environment Toolkit.
Give your localhost a local or public URL.

Turn localhost:3000 into https://app.test with path routing, HTTPS, HMR support, or get a public url without deployment. 

- [Slim @ GitHub](https://github.com/kamranahmedse/slim).

Related contents:

- [Slim - HTTPS local et tunnels publics, tout en un @ Korben :fr:](https://korben.info/slim-https-local-et-tunnels-publics-tout-en-un.html).]]>
            </summary>
            <updated>2026-05-14T09:01:31+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12221</id>
            <title type="text"><![CDATA[portless]]></title>
            <link rel="alternate" href="https://port1355.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12221"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Named .localhost URLs for Development.
Replace port numbers with stable, named local URLs. For humans and agents. 

Portless replaces port numbers with stable, named .localhost URLs for local development. For humans and agents.

- [Portless @ GitHub](https://github.com/vercel-labs/portless).]]>
            </summary>
            <updated>2026-03-20T14:00:59+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11261</id>
            <title type="text"><![CDATA[acme2certifier]]></title>
            <link rel="alternate" href="https://github.com/grindsa/acme2certifier" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11261"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[ACME Proxy enhancing your existing Certificate Authority Infrastructure.

acme2certifier is a development project aimed at creating an ACME protocol proxy. Its primary goal is to enable ACME services for CA servers that do not natively support this protocol.

Related contents:

- [Déploiement et usage de acme2certifier sous Kubernetes avec une PKI Microsoft @ MyPrivateL@B :fr:](https://www.myprivatelab.tech/acme2certifier).]]>
            </summary>
            <updated>2025-12-16T15:55:28+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1148</id>
            <title type="text"><![CDATA[sslh]]></title>
            <link rel="alternate" href="https://github.com/yrutschle/sslh" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1148"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A ssl/ssh multiplexer.

Applicative Protocol Multiplexer (e.g. share SSH and HTTPS on the same port).

sslh accepts connections on specified ports, and forwards them further based on tests performed on the first data packet sent by the remote client.

Probes for HTTP, TLS/SSL (including SNI and ALPN), SSH, OpenVPN, tinc, XMPP, SOCKS5, are implemented, and any other protocol that can be tested using a regular expression, can be recognised. A typical use case is to allow serving several services on port 443 (e.g. to connect to SSH from inside a corporate firewall, which almost never block port 443) while still serving HTTPS on that port.

Related contents:

- [Tunneling corporate firewalls for developers @ FrostKimi&amp;#039;s Secrets](https://blog.frost.kiwi/tunneling-corporate-firewalls/).]]>
            </summary>
            <updated>2025-08-28T19:07:51+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1496</id>
            <title type="text"><![CDATA[Warpgate]]></title>
            <link rel="alternate" href="https://github.com/warp-tech/warpgate" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1496"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Smart SSH, HTTPS and MySQL bastion that requires no additional client-side software.]]>
            </summary>
            <updated>2025-08-28T20:05:22+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3616</id>
            <title type="text"><![CDATA[HTTPS-PORTAL]]></title>
            <link rel="alternate" href="https://github.com/SteveLTN/https-portal" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3616"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A fully automated HTTPS server powered by Nginx, Let&amp;#039;s Encrypt and Docker.

HTTPS-PORTAL is a fully automated HTTPS server powered by Nginx, Let&amp;#039;s Encrypt and Docker. By using it, you can run any existing web application over HTTPS, with only one extra line of configuration.]]>
            </summary>
            <updated>2025-08-29T01:59:16+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4616</id>
            <title type="text"><![CDATA[shcheck]]></title>
            <link rel="alternate" href="https://github.com/santoru/shcheck" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4616"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A basic tool to check security headers of a website]]>
            </summary>
            <updated>2025-08-29T04:46:48+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/7077</id>
            <title type="text"><![CDATA[MiniCA]]></title>
            <link rel="alternate" href="https://github.com/jsha/minica" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/7077"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[minica is a small, simple CA intended for use in situations where the CA operator also operates each host where a certificate will be used. It automatically generates both a key and a certificate when asked to produce a certificate. It does not offer OCSP or CRL services. Minica is appropriate, for instance, for generating certificates for RPC systems or microservices.]]>
            </summary>
            <updated>2025-08-29T11:38:19+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/7761</id>
            <title type="text"><![CDATA[Hitch TLS proxy]]></title>
            <link rel="alternate" href="https://hitch-tls.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/7761"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Hitch is a libev-based high performance SSL/TLS proxy by Varnish Software.]]>
            </summary>
            <updated>2025-08-29T13:31:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/8125</id>
            <title type="text"><![CDATA[Let&amp;#039;s Encrypt]]></title>
            <link rel="alternate" href="https://letsencrypt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/8125"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Let’s Encrypt is a new Certificate Authority:
It’s free, automated, and open.

Related contents:

- [ACME, a brief history of one of the protocols which has changed the Internet Security @ Brocas&amp;#039; Blog](https://blog.brocas.org/2025/12/01/ACME-a-brief-history-of-one-of-the-protocols-which-has-changed-the-Internet-Security/).
- [Nouveauté Let’s Encrypt : Certbot génère enfin des certificats TLS pour vos adresses IP ! @ IT-Connect :fr:](https://www.it-connect.fr/nouveaute-lets-encrypt-certbot-genere-enfin-des-certificats-tls-pour-vos-adresses-ip/).
- [Let’s Encrypt c’est cool, mais il est seul au monde @ Le blog de Seboss666 :fr:](https://blog.seboss666.info/2026/06/lets-encrypt-cest-cool-mais-il-est-seul-au-monde/).]]>
            </summary>
            <updated>2026-06-17T05:53:05+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/8859</id>
            <title type="text"><![CDATA[ssl/ssh multiplexer]]></title>
            <link rel="alternate" href="http://www.rutschle.net/tech/sslh.shtml" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/8859"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[sslh accepts connections on specified ports, and forwards them further based on tests performed on the first data packet sent by the remote client.]]>
            </summary>
            <updated>2025-08-29T16:34:15+00:00</updated>
        </entry>
    </feed>
