From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 10/11 v5] package/freerdp: install server key and certificate
Date: Sun, 22 Feb 2015 15:01:25 +0100 [thread overview]
Message-ID: <20150222140125.GC4016@free.fr> (raw)
In-Reply-To: <20150222144502.0c6b4ddf@free-electrons.com>
Thomas, All,
On 2015-02-22 14:45 +0100, Thomas Petazzoni spake thusly:
> On Sun, 22 Feb 2015 14:16:23 +0100, Yann E. MORIN wrote:
>
> > Yup, I forgot it.
> >
> > But now I wonder what those should be: 0644 or 0600 ?
>
> I was also unsure, and that's why I decided to not add the '-m' myself,
> and open up the discussion. Is it problematic if a non-root user has
> access to this key and certificate?
Well, I don't think so. am not 100% sure about this either.
However, know that those key and cert are already highly public: they
*are* in the FreeRDP repository (i.e. they are not generated at build
time).
So, there is no real security concern about that pair, and I would be
tempted to leave them at 0644.
However, I believe the user should be responsible about providing their
own set of key+cert (and thus set the appropriate permissions on them).
I said in the help text of Weston:
By default, Buildroot installs such files in /etc/freerdp/server/
so you may want to change them in a post-build script or a rootfs
overlay.
So, thanks to your comment, I noticed a few issues, now:
- the key+cert are only installed when FreeRDP server is installed,
so we're missing them when onlt the lib is installed. Damn smartin
who made me change to that situation! :-]
- the comment about the keys should be moved to the FreeRDP option.
I'll provide follow-up patches soon.
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-02-22 14:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 22:36 [Buildroot] [PATCH 0/11 v5] weston: new freerdp backend (branch yem/freerdp) Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 01/11 v5] package/freerdp: bump version Yann E. MORIN
2015-03-04 11:02 ` Thomas Petazzoni
2015-03-04 17:51 ` Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 02/11 v5] package/freerdp: conditionally build gstreamer support Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 03/11 v5] package/freerdp: conditionally build support for libXi Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 04/11 v5] package/freerdp: conditionally build support for libXrender Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 05/11 v5] package/freerdp: avoid development warning Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 06/11 v5] package/freerdp: do not forcibly depend on X.Org Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 07/11 v5] package/freerdp: move architecture-specific block Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 08/11 v5] package/freerdp: add options to enable/disable server and/or client Yann E. MORIN
2015-02-22 11:48 ` Thomas Petazzoni
2015-02-22 13:14 ` Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 09/11 v5] package/freerdp: also install to staging Yann E. MORIN
2015-02-21 22:36 ` [Buildroot] [PATCH 10/11 v5] package/freerdp: install server key and certificate Yann E. MORIN
2015-02-22 11:47 ` Thomas Petazzoni
2015-02-22 13:16 ` Yann E. MORIN
2015-02-22 13:45 ` Thomas Petazzoni
2015-02-22 14:01 ` Yann E. MORIN [this message]
2015-02-21 22:36 ` [Buildroot] [PATCH 11/11 v5] package/weston: add support for the RDP compositor Yann E. MORIN
2015-02-22 11:13 ` [Buildroot] [PATCH 0/11 v5] weston: new freerdp backend (branch yem/freerdp) Thomas Petazzoni
2015-02-22 11:47 ` Thomas Petazzoni
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=20150222140125.GC4016@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.