ThomasWaldmann wrote:
https://en.wikipedia.org/wiki/Internationalized_domain_name

Python: encode/decode with ‘idna’.

ThomasWaldmann wrote:
later add 2factor auth, TOTP, QR-Code rendering.

ThomasWaldmann wrote:
after clicking the link in the activation email, it tells to login there:

http://www.nsupdate.info/accounts/activate/complete/

but the login link points to:

http://www.nsupdate.info/accounts/activate/complete/

which is obviously wrong...

ThomasWaldmann wrote:
for the dnstools log output, we should log the useragent.

in general, we should log the IP.

ThomasWaldmann wrote:
if one HAD a ipv6 connection and visited the web UI, it'll put the ipv6addr into the session (so it can display it on the UI).

if you later revisit the web UI without ipv6 connectivity, it will still show the outdated ipv6addr from the session.

(of course this can also happen with the ipv4 address under similar circumstances)

ThomasWaldmann wrote:
optional / later:

like dnsomatic.com, something like a hub for dyndns2 requests: one in, multiple out.

ThomasWaldmann wrote:
could show whether the nameservers are up

could show some stats (user, host count)

requests per second

....

ThomasWaldmann wrote:
minimum length, etc.

ThomasWaldmann wrote:

ThomasWaldmann wrote:
My fritzbox 6360 from "Kabel BW" (Fritz!OS 05.50) can only handle 1 URL.

if one enters 2 URLs, separated by a space, this happens:

2013-09-30 12:51:21 [15897] [DEBUG] GET /nic/update%20http:/ipv6.nsupdate.info/nic/update

It works correctly with 1 URL, so documentation should get updated to first try 1 URL only and the 2 URLs for fritz boxes.

If it works ok for 1, and does 404 (see fritzbox log) for 2, it can't handle 2.

ThomasWaldmann wrote:
what, why, who?

fair use, privacy (informal)

contact

asmaps wrote:
write a page with instructions how to configure most common routers.

Could be the success_page after generating a new update_secret (with prebuild urls etc)

ThomasWaldmann wrote:
maybe a ?

ThomasWaldmann wrote:
optional, needs generalizing the target nameserver / key / zone from 1 to N

maybe move nameservers / keys / zones from config to database.

also, UI changes to select the zones.

like HOST.USERNAME.nsupdate.info

enables SSO for username's sites using domain cookies. ;)

spam bots might register users (and after email roundtrip) add hosts/domains.

different solutions to avoid that come to mind:

• use recaptcha (owned by google) - privacy / UX / accessibility?
• use akismet?
• use honeypot?

ThomasWaldmann wrote:
what's that?

2013-09-30 02:23:01 [15897] [DEBUG] GET /overview/
2013-09-30 02:23:02 [15896] [DEBUG] Ignoring EPIPE

ThomasWaldmann wrote:
AVM documents that 2 Update URLs can be entered, separated by a space, but it definitely is NOT implemented for:

FritzBox 6360 (Kabel BW) Fritz!OS 05.50

The (one) update request the service is receiving looks like:

/nic/update%20http:/ipv6.nsupdate.info/nic/update

I contacted AVM Support about this, let's see what happens.

ThomasWaldmann wrote:
if someone visits the service via http, encourage using it via https - without enforcing it.

ThomasWaldmann wrote:
so people can use a bookmark to update hosts (or just click a link to immediately update).

separate links for v4 / v6.

if hostnames are orphaned (not updated any more, for a long time), have some means to remove them from dns and database.

same for users who did not use the service for a longer time (and didn't update hosts either).

ThomasWaldmann wrote:
similar to manual browser ip-update, but supported by javascript that runs in a loop and checks the IP addresses every N minutes, detects changes and uses the update api service url to update the dns when the IP(s) change.

could use http basic auth or form based login or reuse admin session.

shows the update results codes somehow on the UI.

ThomasWaldmann wrote:
document why update-secret is (salted) sha1 (speed / load) and why admin login pw is a much stronger method (django default?).

ThomasWaldmann wrote:

document usage with DNSSEC, add a configuration example, useful links, ...

ThomasWaldmann wrote:
dynamic, templated help (like showing configs for the user, with hostname, password, etc. already in place): should stay in django templates

static help, like FAQ should go into sphinx docs and linked from UI.
it is easier to update there than in html templates.

we can link to the sphinx docs from either footer or a minimal help page.

where will sphinx docs get hosted?

include it, so it is statically served on same site?

put it on rtd? versioning?

ThomasWaldmann wrote:
the screenshots on the home view are nicely rotated, so you see them all like in a slideshow.

They are rather small and if you want to see them in original size you click on them.

But: you don't get to a big screenshot rotation then, but just to an individual image.

additionally, users might get confused as the screenshots also include the navigation in the image (but the working navigation is gone), so they might click on non-working navigation and get lost.

Some users may want to use rather short term sessions (cookie gets deleted on browser close) while other may want to stay logged in if they close and reopen the browser.

ThomasWaldmann wrote:
they offer a little metadata including CDN information, additional to the static files, all installable via pypi.

ThomasWaldmann wrote:
e.g. where it logs to (piwik.thelabmill.de).

also, it seems to use domain cookies, please check whether issue #38 is relevant here.

also, how can we access the statistics there?

ThomasWaldmann wrote:

ThomasWaldmann wrote:
for http, to avoid http proxies.

ThomasWaldmann wrote:
this is what you get:
"""
Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.
"""

We should warn the user early that it won't work without cookies.

ThomasWaldmann wrote:
maybe in javascript, show the value in the input field.

as it is saved as salted-sha1, it can't be shown after submission.

ThomasWaldmann wrote:
whatever we had to deal with manually that is not in the repo yet: nginx, bind, ...

ThomasWaldmann wrote:
it just shows "good x.x.x.x" afterwards.

normal users will wonder and be a bit lost.

ajax request maybe?

ThomasWaldmann wrote:
notfqdn

nohost

numhost

abuse

dnserr

911

ThomasWaldmann wrote:
one needs to:

disable dyndns in the fritzbox (uncheck that "use dynamic dns"), apply

re-enable it again, apply

Then it sends an update.

It might be good or nochg, depending on what we have in DNS.

ThomasWaldmann wrote:

jluebbe wrote:

asmaps wrote:

"abuse" api result code should be used for this.

Samuirai wrote:
default is 60. create a user changeable field in a range.

ThomasWaldmann wrote:

ThomasWaldmann wrote:
similar to issue #29 but the nameserver / zones / key is not for general use, but only for the use of its owner.

should be implemented after #29.

ThomasWaldmann wrote:
we only use single host cookies, this issue just serves as a warning:

if we would use domain cookies like for ".nsupdate.info", all hosts in that domain would be able to read and write these cookies. our sites, but also users' sites.

spellcheck, check params

ThomasWaldmann wrote:
from foo import * - don't use without good reason.

ThomasWaldmann wrote:
e.g. login view

autofocus html5 attribute - but how to get it in there?

Samuirai wrote: