Project

General

Profile

Actions

Bug #8782

closed

Custom dyndns issue: username and password is not sent

Added by Alexis Bezverkhyy almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
Start date:
08/14/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

I tried to use a custom DynDNS provider, one that I host myself but whose API is a clone of dyndns.org and I was surprised to see that the username and the password are not sent in the HTTP request.

After comparing code for different dyndns providers it seems that only "custom" has CURLAUTH_ANY set. When I removed this flag, everything started to work.

I opened a pull-request to fix this issue: https://github.com/pfsense/pfsense/pull/3970


Files

screen.png (171 KB) screen.png Constantine Kormashev, 08/19/2018 11:27 AM
packetcapture.cap (1.43 KB) packetcapture.cap Constantine Kormashev, 08/19/2018 11:27 AM
Actions #1

Updated by Jim Pingle almost 4 years ago

  • Category set to Dynamic DNS
  • Status changed from New to Feedback
  • Target version set to 2.4.4
  • % Done changed from 0 to 100
  • Affected Version set to All
  • Affected Architecture All added
  • Affected Architecture deleted ()

PR Merged

Actions #2

Updated by Constantine Kormashev almost 4 years ago

Can see creds in HTTP request:

Packets in .cap file

Actions #3

Updated by Jim Pingle almost 4 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF