DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH v2 3/3] force HTTPS for logins
Date: Wed, 13 Dec 2017 16:44:52 +0100	[thread overview]
Message-ID: <20171213154452.1552-3-thomas@monjalon.net> (raw)
In-Reply-To: <20171213154452.1552-1-thomas@monjalon.net>

Patchwork and bugzilla should be used with HTTPS
to avoid clear-text password login.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 dev.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/dev.html b/dev.html
index 8f6db8d..a539eae 100644
--- a/dev.html
+++ b/dev.html
@@ -42,11 +42,11 @@
 	<p>Anyone is welcome to contribute.
 	<p>The collaboration is based on <a href="/browse/">git</a>
 	and <a href="/ml/archives/dev">emails</a>.
-	Coming patches are listed in <a href="/dev/patchwork">patchwork</a>.
+	Coming patches are listed in <a href="https://dpdk.org/dev/patchwork">patchwork</a>.
 	<p>Planned features are listed in the <a href="/dev/roadmap">roadmap</a>
 	and integrated during a <a href="/dev/roadmap#cycle">cycle started by a merge window</a>.
 	<p>Bugs are open in <a
-	href="/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla</a>.
+	href="https://dpdk.org/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla</a>.
 
 	<h3 id="licenses">Licenses</h3>
 	<p>Main code is BSD licensed and Linux kernel related parts are naturally licensed under the GPL.
@@ -126,7 +126,7 @@
 	in <a href="/dev/patchwork">patchwork</a> with status <em>"New"</em>.
 	So they are visible in the default view (filter <em>"Action Required"</em>).
 	<p>Access to management of his own patches is granted
-	after <a href="/dev/patchwork/register">registration</a>.
+	after <a href="https://dpdk.org/dev/patchwork/register">registration</a>.
 	The status may be manually updated to <em>"RFC"</em>,
 	<em>"Changes Requested"</em>, <em>"Superseded"</em> or <em>"Rejected"</em>.
 	After sending a new version of a patch, developers should set
@@ -137,7 +137,7 @@
 	with a <a href="/dev/patchwork/help/pwclient/">pwclient</a> command line.
 
 	<h3 id="bugzilla">Contribute by finding or fixing bugs</h3>
-	<p>There is a <a href="/tracker/">bug tracker</a> where
+	<p>There is a <a href="https://dpdk.org/tracker/">bug tracker</a> where
 	anybody can notify a bug to the community, and follow the resolution.
 	<p>A notification is sent to dev@dpdk.org for every new bug.
 	The fixes must be sent and discussed on the mailing list.
-- 
2.15.0

  parent reply	other threads:[~2017-12-13 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 22:46 [dpdk-web] [PATCH] switch CDN to HTTPS Thomas Monjalon
2017-12-13 15:44 ` [dpdk-web] [PATCH v2 1/3] force HTTPS for downloads Thomas Monjalon
2017-12-13 15:44   ` [dpdk-web] [PATCH v2 2/3] support HTTPS Thomas Monjalon
2017-12-13 15:52     ` Mcnamara, John
2017-12-13 15:44   ` Thomas Monjalon [this message]
2017-12-13 15:52     ` [dpdk-web] [PATCH v2 3/3] force HTTPS for logins Mcnamara, John
2017-12-13 15:51   ` [dpdk-web] [PATCH v2 1/3] force HTTPS for downloads Mcnamara, John
2017-12-13 15:52   ` Thomas Monjalon

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=20171213154452.1552-3-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=web@dpdk.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;
as well as URLs for NNTP newsgroup(s).