Publish and Subscribe Security policies problem

Login to reply to this topic.
Wed, 2008-07-23 08:15
Joined: 2007-11-07
Forum posts: 17

I am having some issues with TSecurityPolicy object which i am passing while defining a property.

_LIT_SECURITY_POLICY_S0( KAllowSetPolicy, 0x2000FC04 );
_LIT_SECURITY_POLICY_S1( KAllowReadPolicy, 0x2000FC05, ECapabilityTCB );

errVal=RProperty::Define(KUidActiveSS, KSEPropertyType, RProperty::EInt,
                        KAllowReadPolicy, KAllowSetPolicy);

and my ::Attach() and ::Define() is working fine but later I am getting KERN EXE 3.
This is happening only when I use to restrict Read policy, if I am using KAllowAllPolicy its working fine but i don't want that.

_LIT_SECURITY_POLICY_PASS( KAllowAllPolicy );
errVal=RProperty::Define(KUidActiveSS, KSEPropertyType, RProperty::EInt,
                        KAllowAllPolicy , KAllowSetPolicy);

Please help me....


Wed, 2008-07-23 11:52
Joined: 2007-08-29
Forum posts: 295
Re: Publish and Subscribe Security policies problem

Hi cheers,

This link will be helpful to you.

http://www.newlc.com/forum/damn-kern-exec-3-device


Thanks & Regards
Ram

Symbian OS 9.1,S60 3rd edition MR,and Carbide.C++

Thu, 2008-07-24 07:05
Joined: 2007-11-07
Forum posts: 17
Re: Publish and Subscribe Security policies problem

Hi Sahu,

Can you please let me know how i can restrict a dll from reading any published property or any other way I can achieve the same without using TSecurityPolicy.

Cheers,
Reeju

Tue, 2008-07-29 10:37
Joined: 2007-11-07
Forum posts: 17
Re: Publish and Subscribe Security policies problem

Using vendorID and Capabilites I am able to restrict external entities to read published properties.
I used :

IMPORT_C TSecurityPolicy(TVendorId aVendorId, TCapability aCap1=ECapability_None, TCapability aCap2=ECapability_None, TCapability aCap3=ECapability_None);

and

static IMPORT_C TInt Define(TUid aCategory, TUint aKey, TInt aAttr, const TSecurityPolicy &aReadPolicy, const TSecurityPolicy &aWritePolicy, TInt aPreallocated=0);

  • Login to reply to this topic.