My 2 cents: Only on the local node :-).
Thanks,
Ramesh.
On 9/23/2014 2:33 PM, surender khetavath wrote:
> ------------------------------------------------------------------------
>
> *[tickets:#1128] <http://sourceforge.net/p/opensaf/tickets/1128>
> access control feature is valid across nodes?*
>
> *Status:* unassigned
> *Milestone:* 4.3.3
> *Created:* Tue Sep 23, 2014 09:03 AM UTC by surender khetavath
> *Last Updated:* Tue Sep 23, 2014 09:03 AM UTC
> *Owner:* nobody
>
> As per README.ACCESS_CONTROL
> ""
> - members of the same primary groups as the IMM service itself
> (normally other
> processes of the opensaf middleware)
> ""
>
> Here other processes of opensaf mean the processes on the same node?
> Or should the enforcement be applicable for other
> processes(middleware) on diff node?
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because
> [email protected] is subscribed to
> https://sourceforge.net/p/opensaf/tickets/
> <https://sourceforge.net/p/opensaf/tickets>
>
> To unsubscribe from further messages, a project admin can change
> settings at https://sourceforge.net/p/opensaf/admin/tickets/options.
> Or, if this is a mailing list, you can unsubscribe from the mailing list.
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Opensaf-tickets mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
---
** [tickets:#1128] access control feature is valid across nodes?**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Tue Sep 23, 2014 09:03 AM UTC by surender khetavath
**Last Updated:** Tue Sep 23, 2014 09:03 AM UTC
**Owner:** nobody
As per README.ACCESS_CONTROL
""
- members of the same primary groups as the IMM service itself (normally other
processes of the opensaf middleware)
""
Here other processes of opensaf mean the processes on the same node?
Or should the enforcement be applicable for other processes(middleware) on diff
node?
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
