Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

DoH and client authentication

  • 3 odgovora
  • 2 imaju ovaj problem
  • 2 prikaza
  • Posljednji odgovor od fjsw

I’m trying to use my own DoH server with Firefox. It works fine basically but if I enable client authentication on it, DoH seems to fail. Since It’s difficult to create ip address based access filtering for remote mobile users, I want to add some user authentication feature to my DoH session.

Does current DoH client of Firefox support “TLS client certificate” or “HTTP header” authentication?

I’m trying to use my own DoH server with Firefox. It works fine basically but if I enable client authentication on it, DoH seems to fail. Since It’s difficult to create ip address based access filtering for remote mobile users, I want to add some user authentication feature to my DoH session. Does current DoH client of Firefox support “TLS client certificate” or “HTTP header” authentication?

Svi odgovori (3)

1. From packet dump in my environment, Firefox DoH client sent no client certificate back to the DoH server.

  1. DoH Session

Secure Sockets Layer

   TLSv1.2 Record Layer: Handshake Protocol: Multiple Handshake Messages
       Content Type: Handshake (22)
       Version: TLS 1.2 (0x0303)
       Length: 44
       Handshake Protocol: Certificate
           Handshake Type: Certificate (11)
           Length: 3
           Certificates Length: 0  <<===== NULL
       :
       :
  1. Normal session (from firefox URL bar)

Secure Sockets Layer

   TLSv1.2 Record Layer: Handshake Protocol: Multiple Handshake Messages
       Content Type: Handshake (22)
       Version: TLS 1.2 (0x0303)
       Length: 1913
       Handshake Protocol: Certificate
           Handshake Type: Certificate (11)
           Length: 1352
           Certificates Length: 1349   <<===== (valid client certificate)
          :
          :

2. Regarding HTTP header auth, DoH server (nginx on frontend) generated logs something like "no user/password was provided for basic authentication"....


Does anyone have tried to authenticate Firefox DoH user to prevent your DoH server from being an open resolver?

Is this something your own making or from whom software/hardware are you using this from? If not yours did you contact their support on this issue since firefox AFAIK isn't a server software?

Izmjenjeno od WestEnd

Sorry for the confusion, My DoH server is nginx and DoH client is firefox.