From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 1d32c50e0306b7b9d304bd0037a99252f9e6eb9a
Date: Wed, 07 Jul 2021 09:35:11 +0000 [thread overview]
Message-ID: <4GKZ5q3CYdz2xLW@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3272 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 1d32c50e0306b7b9d304bd0037a99252f9e6eb9a (commit)
from 92a5ad86e7012d1c1c2e7a3446c63c78e3d7abef (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1d32c50e0306b7b9d304bd0037a99252f9e6eb9a
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Tue Jul 6 18:08:29 2021 +0200
ddns.cgi: Fix sanity check logic.
The input validation did not work in the proper way. It allways
reported "No password" when using a provider which supports token and
the token has been given.
This of course is wrong and leaded to unuseable providers.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/ddns.cgi | 32 ++++++++++++++++++++------------
1 file changed, 20 insertions(+), 12 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/ddns.cgi b/html/cgi-bin/ddns.cgi
index e30aa3d4f..0e3ccbe45 100644
--- a/html/cgi-bin/ddns.cgi
+++ b/html/cgi-bin/ddns.cgi
@@ -171,20 +171,28 @@ if (($settings{'ACTION'} eq $Lang::tr{'add'}) || ($settings{'ACTION'} eq $Lang::
$errormessage = $Lang::tr{'invalid domain name'};
}
- # Check if a username has been sent.
- if ($settings{'LOGIN'} eq '') {
- $errormessage = $Lang::tr{'username not set'};
- }
+ # Check if the choosen provider supports token based authentication.
+ if ($settings{'SERVICE'} ~~ @token_provider) {
+ # Check if a token has been given.
+ unless ($settings{'TOKEN'}) {
+ $errormessage = $Lang::tr{'token not set'};
+ }
- # Check if a password has been typed in.
- # freedns.afraid.org does not require this field.
- if (($settings{'PASSWORD'} eq '') && ($settings{'SERVICE'} ne 'freedns.afraid.org') && ($settings{'SERVICE'} ne 'regfish.com')) {
- $errormessage = $Lang::tr{'password not set'};
- }
+ # Automatically set the username to token.
+ $settings{'LOGIN'} = "token";
- # Check if a token has been given for provider which support tokens.
- if (($settings{'SERVICE'} ~~ @token_provider) && ($settings{'TOKEN'} eq '')) {
- $errormessage = $Lang::tr{'token not set'};
+ # A provider without token support has been choosen.
+ } else {
+ # Check if a username has been sent.
+ if ($settings{'LOGIN'} eq '') {
+ $errormessage = $Lang::tr{'username not set'};
+ }
+
+ # Check if a password has been typed in.
+ # freedns.afraid.org does not require this field.
+ if (($settings{'PASSWORD'} eq '') && ($settings{'SERVICE'} ne 'freedns.afraid.org') && ($settings{'SERVICE'} ne 'regfish.com')) {
+ $errormessage = $Lang::tr{'password not set'};
+ }
}
# Go furter if there was no error.
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-07 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4GKZ5q3CYdz2xLW@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox