Hi Erik, Right now, there's no level over 2.
It is possible that there'll be newer versions for OMA DRM in future. However, right now the CMLA compliance rules only specifies this restriction for devices deploying OMA DRM v2. It doesn't specify anything for v1. So even if and when there's a v3, CMLA may or may not be involved in such requirement specifications, and if it is, this restriction may or may not be the same. It's probably too early to make the generalization "if (drmVersion >= 2)". If that is the case in future, we can always add it later. Thanks for your input! Best regards, Carol. -----Original Message----- From: ext Erik Hodge [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 3:38 PM To: Chen Carol.I (Nokia-TP-MSW/Dallas) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [email protected] Subject: Re: [datatype-dev] CR: OMA DRM v2 files should not be playedoutthrough BT Headset Are there (or might there ever be) OMA DRM levels over 2? If so, the check should be: - if (drmVersion == 2) + if (drmVersion >= 2) Thanks, - Erik [EMAIL PROTECTED] wrote: > Hi Eric, > > The preferences file is not protected, so yes, someone can edit the values in there. However, each time a clip is opened, the DRM version is checked and the preference value updated. So unless he can somehow change the value between the time of the update and the time audio device reads in the value, it should be ok. It's not hacker proof, but just editing the file won't make a difference. > > Changes committed to Head and 210Cays. > > Thanks! > Carol. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of ext Eric > Hyche > Sent: Friday, 07 April, 2006 8:28 AM > To: Chen Carol.I (Nokia-TP-MSW/Dallas); > [EMAIL PROTECTED]; [email protected] > Subject: RE: [datatype-dev] CR: OMA DRM v2 files should not be > playedoutthrough BT Headset > > > > Diff looks good, but I have a question. It looks like the OMA DRM > version is read from the prefs and that if this OMA DRM version != 2, > then the audio is not set as secure and the output is not disabled. > > Are the preferences on Symbian protected in any way? > What would prevent someone from simply editing their preferences and > changing the "OmaDrmVersion" value to something other than 2? > > Eric > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> [EMAIL PROTECTED] >> Sent: Thursday, April 06, 2006 3:54 PM >> To: [EMAIL PROTECTED]; [email protected] >> Subject: [datatype-dev] CR: OMA DRM v2 files should not be played >> outthrough BT Headset >> >> "Nokia submits this code under the terms of a commercial contribution >> agreement with RealNetworks, and I am authorized to contribute this >> code under said agreement." >> >> Modified by: >> [EMAIL PROTECTED] >> >> Reviewed by: >> >> Date: >> 4-5-2006 >> >> Error ID: >> TSW ID=ATEI-6MVRSB >> >> Project: >> Helix plugin for Symbian >> >> Synopsis: >> -- The CMLA compliance rules require that transfer of OMA DRM >> v2 content >> via digital output to the other devices is prevented. >> -- Helix needs to call CAudioOutput::SetSecureOutputL(ETrue) if the >> clip is OMA DRM v2 content. >> -- Change is for both MDF and non-MDF audio devices. >> -- Modified error code handling in InitializeComplete so >> appropriate error is returned. >> -- Added new error status HXR_SET_SECURE_OUT_FAIL to be used when the >> call to SetSecureOutputL leaves with error. It's mapped to >> KErrNotSupported. >> >> Files Modified: >> datatype\mdf\audio\dsp\mdfauddevice.h >> datatype\mdf\audio\dsp\mdfauddevice.cpp >> datatype\mdf\audio\dsp\mdfdevsound.h >> datatype\mdf\audio\dsp\mdfdevsound.cpp >> datatype\mdf\audio\dsp\Umakefil >> >> audio\device\platform\symbian\audsymbian.cpp >> audio\device\platform\symbian\audiosvr\audio_svr.h >> audio\device\platform\symbian\audiosvr\audio_svr.cpp >> audio\device\platform\symbian\audiosvr\mmf\audio_session-mmf.h >> audio\device\platform\symbian\audiosvr\mmf\audio_session-mmf.cpp >> >> client\core\clntcoredll_symbian.pcf >> clientapps\symbianMmf\hxmmfctrlimpl.cpp >> common\include\hxresult.h >> >> Files Added: >> none >> >> Image Size and Heap Use impact: >> minor >> >> Platforms and Profiles Build Verified: >> armv5 / helix-client-s60-mmf-mdf-dsp, helix-client-s60-mmf-basic >> >> Platforms and Profiles Functionality verified: >> armv5 / helix-client-s60-mmf-mdf-dsp >> >> Branch: >> hxclient_2_1_0_cayennes, head >> >> >> <<audio.diff>> <<datatype.diff>> <<rest.diff>> >> >> >> > > > _______________________________________________ > Datatype-dev mailing list > [EMAIL PROTECTED] > http://lists.helixcommunity.org/mailman/listinfo/datatype-dev > > _______________________________________________ > Datatype-dev mailing list > [EMAIL PROTECTED] > http://lists.helixcommunity.org/mailman/listinfo/datatype-dev > _______________________________________________ Audio-dev mailing list [email protected] http://lists.helixcommunity.org/mailman/listinfo/audio-dev
