Hey,
This list currently has a low enough volume that I think that it
fulfills that role (and others) just fine. We average less than one
email a day, and many discussion threads are relevant to a larger
audience at this point.
I'm a bit reserved when it comes to making a new list for announcements
only, because it generally is extremely hard to see whether it actually
contributes and whether people actually read it, since it contains
typically one-way communication only.
But, I'll keep it in consideration.
Auke
On 06/30/2017 04:47 AM, Gustavo Sverzut Barbieri wrote:
> Hi Auke,
>
> Since clr updates are automatic and hidden there is usually no way to
> present such messages in updates like done in other systems. What about
> a clr-update mailing or at least clr-announce, some kind of low volume
> list that users would subscribe, eventually mirrored on some RSS
>
> On Thu, Jun 29, 2017 at 7:52 PM, Auke Kok <auke-jan.h.kok(a)intel.com
> <mailto:auke-jan.h.kok(a)intel.com>> wrote:
>
>
> All,
>
> We've long had root logins disabled on clearlinux, but we've
> inadvertently left SSHD to allow root login with certificates/keys for a
> while. This will be disabled in the future as well and all root logins,
> certificate or password based authentication or not, will be refused by
> default in ClearLinux by sshd.
>
> If you are using SSH keys to log in as root to ClearLinux machines, I
> suggest you stop doing so and instead rely on unprivileged accounts (and
> use sudo), even if you are using keys. If you had installed and used
> keys yourself, you may lose that access in future updates.
>
> For most ClearLinux systems, the change has no impact, since ClearLinux
> does not ship keys nor do I suspect anyone is using keys to log in as
> root. If you are however using this feature for automation, you can use
> an sshd_config option (`PermitRootLogin prohibit-password`) to allow
> this in again.
>
> Cheers,
>
> Auke
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org <mailto:Dev(a)lists.clearlinux.org>
> https://lists.clearlinux.org/mailman/listinfo/dev
> <https://lists.clearlinux.org/mailman/listinfo/dev>
>
>
>
>
> --
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> --------------------------------------
> MSN, GTalk, FaceTime: barbieri(a)gmail.com <mailto:barbieri(a)gmail.com>
> Skype: gsbarbieri
> Mobile: +55 (16) 99354-9890
All,
We've long had root logins disabled on clearlinux, but we've
inadvertently left SSHD to allow root login with certificates/keys for a
while. This will be disabled in the future as well and all root logins,
certificate or password based authentication or not, will be refused by
default in ClearLinux by sshd.
If you are using SSH keys to log in as root to ClearLinux machines, I
suggest you stop doing so and instead rely on unprivileged accounts (and
use sudo), even if you are using keys. If you had installed and used
keys yourself, you may lose that access in future updates.
For most ClearLinux systems, the change has no impact, since ClearLinux
does not ship keys nor do I suspect anyone is using keys to log in as
root. If you are however using this feature for automation, you can use
an sshd_config option (`PermitRootLogin prohibit-password`) to allow
this in again.
Cheers,
Auke
Signed-off-by: Simental Magana, Marcos <marcos.simental.magana(a)intel.com>
---
Documentation[1] mentions to check $ man swupd for more information about
swupd, but we don't ship man pages.
[1]-https://clearlinux.org/documentation/clear-linux/how-to/swupd/run.html
This commit adds the documentation package to include man pages
in the os-core-update bundle.
bundles/os-core-update | 1 +
1 file changed, 1 insertion(+)
diff --git a/bundles/os-core-update b/bundles/os-core-update
index 3285611..b491c3f 100644
--- a/bundles/os-core-update
+++ b/bundles/os-core-update
@@ -15,6 +15,7 @@ gzip-bin
pacrunner
pigz-bin
swupd-client
+swupd-client-doc
swupd-client-extras
swupd-overdue
tar-bin
--
2.13.1
Hi,
I have a use case where we want to run a *System Container* which resembles
a full blown OS. I found that LXC is the perfect fit for this. I tried to
use the rootfs from a LXC container to run under cc-oci-runtime however I
found that cc-oci-runtime starts its own init process (hyperstart) instead
of systemd. Is it possible to use systemd with clear containers?
Thanks,
-Syed
