We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

DoH and client authentication

  • 3 replies
  • 2 have this problem
  • 1 view
  • Last reply by fjsw

fjsw
fjsw
more options

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?

All Replies (3)

fjsw
fjsw Question owner
more options

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?

WestEnd
WestEnd
more options

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?

Modified by WestEnd

fjsw
fjsw Question owner
more options

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