From owner-freebsd-current@freebsd.org  Tue Nov 17 22:25:36 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D77AA31D92
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 17 Nov 2015 22:25:36 +0000 (UTC)
 (envelope-from dan_partelly@rdsor.ro)
Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10])
 by mx1.freebsd.org (Postfix) with ESMTP id C84401FF9;
 Tue, 17 Nov 2015 22:25:34 +0000 (UTC)
 (envelope-from dan_partelly@rdsor.ro)
Received: from [192.168.1.101] (unknown [79.119.24.18])
 by mail.rdsor.ro (Postfix) with ESMTP id EEE2B1F844;
 Wed, 18 Nov 2015 00:25:33 +0200 (EET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues?
From: Dan Partelly <dan_partelly@rdsor.ro>
In-Reply-To: <29711.1447778554@chaos>
Date: Wed, 18 Nov 2015 00:25:32 +0200
Cc: Julian Elischer <julian@freebsd.org>,
 freebsd-current@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <61FE0B8E-37C3-4654-90BC-7A4F2EB3FFDB@rdsor.ro>
References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro>
 <564AED8B.4080809@freebsd.org>
 <AAB7C093-5065-4102-80B2-FB10A3D441D8@rdsor.ro> <29711.1447778554@chaos>
To: "Simon J. Gerraty" <sjg@juniper.net>
X-Mailer: Apple Mail (2.3096.5)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 22:25:36 -0000

It=E2=80=99s not about the fronted. That would have to be replaced most =
likely=20
The most useful part IMO is the permission engine itself, and maybe some=20=

other parts too but without insight into implementation I am not able to=20=

judge that. =20

You could IPC key value-data into the security engine describing =
arbitrary commands,
, have the request validated, user right checked, then passed to a =
command execution=20
system (and I use the command  term very loosely, I do not refers to a
utility) =20


> On 17 Nov 2015, at 18:42, Simon J. Gerraty <sjg@juniper.net> wrote:
>=20
> Dan Partelly <dan_partelly@rdsor.ro> wrote:
>>  Juniper can further help FreeBSD by donating the code of their
>>  system management daemon and their fine granularity permissions
>=20
> At the cost of i18n etc?
> The Junos UI is totally data driven, syntax is verified term by term
> (since depending on your permissions some terms simply do not exist =
for
> you).   Such a model cannot be successfully translated to other
> languages where the order of verbs and nouns differ for example.
>=20
> Everything I've read on the topic suggests that messages must be
> translated on at least phrase if not sentence granularity for =
reasonable
> results, and that just doesn't fit our UI.
> Thus enhancement requests for i18n are politely rejected.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"