Re: How to disable httpd's default

2022-01-14 Thread Crystal Kolipe
On Fri, Jan 14, 2022 at 07:50:36PM +, i...@protonmail.com wrote: > > It's not. Put the invalid block first and remove the wildcard block at the > > end. > > It doesn't work. Then the valid domains gets served with the > self-made certificate. It does work. You must have an error in your

Re: How to disable httpd's default

2022-01-14 Thread Crystal Kolipe
On Fri, Jan 14, 2022 at 08:59:00AM -0500, Steven Shockley wrote: > Note that this does not require haproxy to have the client certificates, > since the hostname is transmitted in plaintext with SNI. At the moment, yes, but at some point we might implement ECH...

Re: How to disable httpd's default

2022-01-14 Thread Steven Shockley
On 1/13/2022 6:46 PM, i...@protonmail.com wrote: I would like to avoid httpd giving anything if a user types in the IP address of the server. At first I just made an empty page, which is fine for port 80, but if the user then types https://xxx.xxx.xxx.xxx, then the certificate for a domain

Re: How to disable httpd's default

2022-01-14 Thread Crystal Kolipe
On Fri, Jan 14, 2022 at 05:52:21AM -0700, Anthony J. Bentley wrote: > Crystal Kolipe writes: > > On Fri, Jan 14, 2022 at 01:49:01AM -0700, Anthony J. Bentley wrote: > > > The natural next question would be what leaks when someone accesses the > > > server using a made-up hostname. > > > > By

Re: How to disable httpd's default

2022-01-14 Thread Anthony J. Bentley
Crystal Kolipe writes: > On Fri, Jan 14, 2022 at 01:49:01AM -0700, Anthony J. Bentley wrote: > > The natural next question would be what leaks when someone accesses the > > server using a made-up hostname. > > By 'made-up hostname', I'm assuming that you mean connecting to the server's > IP

Re: How to disable httpd's default

2022-01-14 Thread Crystal Kolipe
On Fri, Jan 14, 2022 at 03:21:03AM -0700, Anthony J. Bentley wrote: > From that I would expect to be able to create server blocks enumerating > valid hostnames, name the last block "*", and specify a self-signed > certificate with a domain name of "invalid". You just commented in another mail in

Re: How to disable httpd's default

2022-01-14 Thread Crystal Kolipe
On Fri, Jan 14, 2022 at 01:49:01AM -0700, Anthony J. Bentley wrote: > Crystal Kolipe writes: > > On Thu, Jan 13, 2022 at 11:46:18PM +, i...@protonmail.com wrote: > > > I would like to avoid httpd giving anything if a user types in the IP > > > address of the server. > > > > > > At first I

Re: How to disable httpd's default

2022-01-14 Thread Anthony J. Bentley
i...@protonmail.com writes: > I would like to avoid httpd giving anything if a user types in the IP > address of the server. httpd.conf(5) says: server name {...} Match the server name using shell globbing rules. This can be an explicit name, www.example.com, or a name

Re: How to disable httpd's default

2022-01-14 Thread Anthony J. Bentley
Crystal Kolipe writes: > On Thu, Jan 13, 2022 at 11:46:18PM +, i...@protonmail.com wrote: > > I would like to avoid httpd giving anything if a user types in the IP > > address of the server. > > > > At first I just made an empty page, which is fine for port 80, but if > > the user then types

Re: How to disable httpd's default

2022-01-13 Thread Crystal Kolipe
On Thu, Jan 13, 2022 at 11:46:18PM +, i...@protonmail.com wrote: > I would like to avoid httpd giving anything if a user types in the IP > address of the server. > > At first I just made an empty page, which is fine for port 80, but if > the user then types https://xxx.xxx.xxx.xxx, then the

Re: How to disable httpd's default

2022-01-13 Thread Yamadaえりな
You can make a rewrite to redirect all defaults to your main site (either https or non-https). ありがとう えりな On Fri, Jan 14, 2022 at 7:59 AM wrote: > I would like to avoid httpd giving anything if a user types in the IP > address of the server. > > At first I just made an empty page, which is