- **Part**: - --> doc
- **Comment**:
Apparently the README.ACCESS_CONTROL needs a clarification.
---
** [tickets:#1121] imm access control change at build time didnot reflect in
attribute change**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Mon Sep 22, 2014 07:35 AM UTC by surender khetavath
**Last Updated:** Mon Sep 22, 2014 07:35 AM UTC
**Owner:** nobody
changeset : 5697
According to README.ACCESS_CONTROL:
"At build time the default access control mode can be changed (to ENFORCING)
after the configure step by adding to config.h:
#define IMM_ACCESS_CONTROL_MODE 2"
Followed the README and added the above #def to config.h
After bringup of opensaf the change didnot reflect in the attribute.
immlist opensafImm=opensafImm,safApp=safImmService
opensafImm SA_NAME_T
opensafImm=opensafImm (21)
longDnsAllowed SA_UINT32_T 0 (0x0)
authorizedGroup SA_STRING_T <Empty>
accessControlMode SA_UINT32_T 0 (0x0)
SaImmAttrImplementerName SA_STRING_T OpenSafImmPBE
SaImmAttrClassName SA_STRING_T OpensafImm
SaImmAttrAdminOwnerName SA_STRING_T IMMLOADER
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
