Are there good reasons NOT to put the serviceDir or ServiceID in the Entry[]?

View: New views
2 Messages — Rating Filter:   Alert me  

Are there good reasons NOT to put the serviceDir or ServiceID in the Entry[]?

by Bryan Thompson-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I am wondering if there are good reasons NOT to disclose certain
information about a service via its Entry[].  For example, its ServiceID
(yes, available from the ServiceItem, but I am thinking of integration
with other systems) or the directory for the persistent state of the
service.  Is it seen as a security problem to do this?

Thanks,

-bryan

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to listserv@...

Re: Are there good reasons NOT to put the serviceDir or ServiceID in the Entry[]?

by Calum Shaw-Mackay :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I think it depends upon what integration you're doing.

I think there is very little need to expose your persistence  
directory, if at all - and yes it could well be a security risk.
Also the ServiceID is pretty jini specific.

If you absolutely need this, I'd expose it through an administration  
interface rather than in the Entry, snd yes the SID is available  
through ServiceItem, which is where I would potentially look at re-
working hte ServiceITem class into your integration rather than just  
the Entry array.

The key information that should be exposed by a service through  
Entries during it's Service Registration, tend to be more along the  
lines of differentiating the service during a search - i.e. I know the  
Space that I put workflow entries is called 'WFLOW' and the one that I  
put errors in for processing and auditing is called 'ERROR' etc, also  
I want a service that's 'running' in Room A on the 2nd floor, or any  
space manufactured by X

Realistically, a lot of other things should not be in the entry list,  
so the best way would be, how do I describe my service to make it  
available to specific searching without exposing too many details

--Calum


On 18 Jan 2009, at 12:39, Bryan Thompson wrote:

> Hello,
>
> I am wondering if there are good reasons NOT to disclose certain
> information about a service via its Entry[].  For example, its  
> ServiceID
> (yes, available from the ServiceItem, but I am thinking of integration
> with other systems) or the directory for the persistent state of the
> service.  Is it seen as a security problem to do this?
>
> Thanks,
>
> -bryan
>
> --------------------------------------------------------------------------
> Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
> Community Web Site:  http://jini.org
> jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
> Unsubscribing:       email "signoff JINI-USERS"  to listserv@...

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to listserv@...