From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [psa] various server software upgrades
Date: Sun, 6 Dec 2015 22:42:29 +0100 [thread overview]
Message-ID: <20151206214229.GE4023@free.fr> (raw)
In-Reply-To: <20151202073542.GY23754@vapier.lan>
Hello Mike,
On 2015-12-02 02:35 -0500, Mike Frysinger spake thusly:
> the busybox.net software has been languishing for quite a long time,
> so i gave it a strong kick today. just about every piece of software
> has been upgraded on the box including bugzilla. my various testing
> looks like it still works, but if you guys notice anything weird, feel
> free to let me know.
Yes, I've noticed that buildroot.org has switched to https with:
Strict-Transport-Security: max-age=63072000; includeSubDomains
Unfortunately, we do have subdomains that are not https-enabled, and are
on another machine:
http://autobuild.buildroot.org/
But now, because of https-sts, this sub-domain is no longer reachable.
To be noted, once a browser has seen the hsts settings once, it will keep
them for how long it has been specified, that is 63072000 seconds in our
case, which is about 730 days, or 2 years.
Which means anyone that has visited buildroot.org will be blocked from
the sub-domains for the next two years (unles sthey switch to https
too).
What can we do about this?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-12-06 21:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 7:35 [Buildroot] [psa] various server software upgrades Mike Frysinger
2015-12-02 7:58 ` Lionel Orry
2015-12-02 8:43 ` Peter Korsgaard
2015-12-02 9:25 ` Nikolay Dimitrov
2015-12-02 9:28 ` Nikolay Dimitrov
2015-12-02 17:31 ` Mike Frysinger
2015-12-02 18:38 ` Nikolay Dimitrov
2015-12-06 21:42 ` Yann E. MORIN [this message]
2015-12-06 22:00 ` Peter Korsgaard
2015-12-07 1:55 ` Mike Frysinger
2015-12-07 6:34 ` Peter Korsgaard
2015-12-07 18:51 ` Mike Frysinger
2015-12-07 20:37 ` Peter Korsgaard
2015-12-07 21:55 ` Mike Frysinger
2015-12-07 22:16 ` Peter Korsgaard
2015-12-07 22:54 ` Mike Frysinger
2015-12-07 23:02 ` Yann E. MORIN
2015-12-07 23:22 ` Mike Frysinger
2015-12-08 7:52 ` Peter Korsgaard
2015-12-08 16:40 ` Mike Frysinger
2015-12-08 16:43 ` Peter Korsgaard
2015-12-08 17:27 ` Mike Frysinger
2015-12-08 7:50 ` Peter Korsgaard
2015-12-08 0:17 ` Mike Frysinger
2015-12-08 7:55 ` Peter Korsgaard
2015-12-08 16:38 ` Mike Frysinger
2015-12-07 8:00 ` Peter Korsgaard
2015-12-07 8:23 ` Peter Korsgaard
2015-12-07 18:52 ` Mike Frysinger
2015-12-07 19:57 ` Mike Frysinger
2015-12-07 19:59 ` Yann E. MORIN
2015-12-07 23:52 ` Mike Frysinger
2015-12-07 20:42 ` Peter Korsgaard
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=20151206214229.GE4023@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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