Dan Creswell wrote:
Hi Peter,
On 4 August 2011 03:43, Peter Firmstone wrote:
Dan, you're wise and I respect your view.
Thank you equally be careful how much wiseness you attribute to me and
thus how much respect you give me - nobody is perfect! :)
Security matters to me because
Hi Peter,
On 4 August 2011 03:43, Peter Firmstone wrote:
> Dan, you're wise and I respect your view.
>
Thank you equally be careful how much wiseness you attribute to me and
thus how much respect you give me - nobody is perfect! :)
> Security matters to me because I plan to deploy over insecure
The big issues, are always about "security" as a starting point.
And it's hard to manage security without some pre-established
settings. What do we all think about a "default" security
configuration (such as binding to localhost, asserting a download
permission and using SSL) that fall o
Dan, you're wise and I respect your view.
Security matters to me because I plan to deploy over insecure networks.
Luckily security is mostly complete, Bob Scheifler's team achieved what
they set out to do, a very difficult task I might add. But this takes
skill on the application developers p
Gregg Wonderly wrote:
On 8/2/2011 3:15 AM, Dan Creswell wrote:
How will an administrator know when their djinn has reached equilibrium?
Answer: Probably by observation rather than providing a guaranteed
time period.
Next question: Do your interfaces support the administrator need to
understa
On 8/3/2011 3:08 PM, Dan Creswell wrote:
I recall Waldo saying some time ago that systems get harder and harder
to do as you in order from:
(1) Single-thread single machine.
(2) Multi-thread single machine.
(3) Multi-machine.
(4) Multi-machine with security.
On that basis, I'm tempted to say we
I recall Waldo saying some time ago that systems get harder and harder
to do as you in order from:
(1) Single-thread single machine.
(2) Multi-thread single machine.
(3) Multi-machine.
(4) Multi-machine with security.
On that basis, I'm tempted to say we should make our lives easier by
setting so
On 8/2/2011 3:15 AM, Dan Creswell wrote:
How will an administrator know when their djinn has reached equilibrium?
Answer: Probably by observation rather than providing a guaranteed time period.
Next question: Do your interfaces support the administrator need to
understand their djinn's behaviou
ServiceRegistrar,
which is authenticated before code is downloaded.
3. The node then registers a RemotePolicy with the registrar and
awaits policy configuration by an authenticating administration
client (the local RemotePolicy service must also be authenticated
by the client).
4. The
ed having a logging service, to log SecurityException's,
however the difficulty is one change could cause an avalanche of
logging, a self inflicted denial of service.
Perhaps an AdminLog, that could be obtained through administrable, I'm
not sure.
It would be possible to have a pseudo Re
How will an administrator know when their djinn has reached equilibrium?
Answer: Probably by observation rather than providing a guaranteed time period.
Next question: Do your interfaces support the administrator need to
understand their djinn's behaviour?
On 2 August 2011 01:52, Peter Firmstone
Just get some feedback on this potential remote policy service. The
main intent here is to provide a secure centralised policy administrator
to simplify java security policy management for a djinn group. Note
this is new work, so it doesn't yet support encrypted policy files.
I've used code
12 matches
Mail list logo
