nanog mailing list archives
Re: Juniper's artificial feature blocking (was legacy /8)
From: Owen DeLong <owen () delong com>
Date: Sun, 4 Apr 2010 18:55:58 -0700
On Apr 4, 2010, at 2:07 PM, James Hess wrote:
On Sun, Apr 4, 2010 at 2:33 PM, Michael Sokolov <msokolov () ivan harhan org> wrote:feature blocking seems to negate that. I mean, how could their disabled-until-you-pay blocking of "premium features" be effective if a user can get to the underlying Unix OS, shell, file system, processes,Probably signed binaries, veriexec with a signature list of allowed executables, proprietary system daemons, hardware drivers, and read-only filesystems. Protections may be in hardware, and you do not have source code. You can in JunOS "start shell user root" as much as you like and get a root shell on various platforms, but some functions are limited.
Most of their license keys are implemented as nag-ware. If you don't mind logs full of "Use of this feature requires a license..." messages, then, it's between you and your lawyers as long as you don't get caught. Owen
Current thread:
- Juniper's artificial feature blocking (was legacy /8) Michael Sokolov (Apr 04)
- Re: Juniper's artificial feature blocking (was legacy /8) James Hess (Apr 04)
- Re: Juniper's artificial feature blocking (was legacy /8) Owen DeLong (Apr 05)
- Re: Juniper's artificial feature blocking (was legacy /8) Stephen Sprunk (Apr 08)
- Re: Juniper's artificial feature blocking (was legacy /8) Rubens Kuhl (Apr 05)
- Re: Juniper's artificial feature blocking (was legacy /8) James Hess (Apr 04)