OmaDm - Revision history

RodWhitby: /* OmaDm -set_domain */

2011-07-08T08:27:22Z

OmaDm -set_domain

RodWhitby: /* OmaDm -client */

2011-07-08T05:14:34Z

OmaDm -client

RodWhitby: /* OmaDm -syncdata */

2011-07-08T05:00:23Z

OmaDm -syncdata

RodWhitby: /* OmaDm -set_domain */

2011-07-08T04:57:43Z

OmaDm -set_domain

RodWhitby: /* OmaDm -set_domain */

2011-07-08T04:56:07Z

OmaDm -set_domain

RodWhitby at 04:53, 8 July 2011

2011-07-08T04:53:15Z

RodWhitby at 04:47, 8 July 2011

2011-07-08T04:47:42Z

RodWhitby at 04:38, 8 July 2011

2011-07-08T04:38:38Z

RodWhitby at 04:19, 8 July 2011

2011-07-08T04:19:19Z

RodWhitby at 04:12, 8 July 2011

2011-07-08T04:12:38Z

← Older revision		Revision as of 08:27, 8 July 2011
Line 104:		Line 104:

	Examination of a normal device indicates that the "domain" file normally has the contents "ps.palmws.com" (with no terminating newline character), resulting in a "https://ps.palmws.com/palmcsext/swupdateserver" value in the DmTree.xml files.		Examination of a normal device indicates that the "domain" file normally has the contents "ps.palmws.com" (with no terminating newline character), resulting in a "https://ps.palmws.com/palmcsext/swupdateserver" value in the DmTree.xml files.
		+
		+	The "domain" file is written by UpdateDaemon each time it starts, based on the "locationHost" system preference.

	== OmaDm -client ==		== OmaDm -client ==

← Older revision		Revision as of 05:14, 8 July 2011
Line 106:		Line 106:

	== OmaDm -client ==		== OmaDm -client ==
		+
		+	Calling "OmaDm -client" updates some authentication values in DmTree.xml and creates the following files in the SessionFiles directory:
		+
		+	client_server.xml
		+	component_list
		+	dmhttps.header
		+	server_client.xml

← Older revision		Revision as of 05:00, 8 July 2011
Line 82:		Line 82:

	The template for DmTree.xml can be found in /usr/share/omadm/DmTree.xml and is populated with the information gained from reading all the input data sources.		The template for DmTree.xml can be found in /usr/share/omadm/DmTree.xml and is populated with the information gained from reading all the input data sources.
		+
		+	It seems that "OmaDm -syncdata" is additive, replicating the package-related contents in the DmTree.xml files each time it is called.

	== OmaDm -revert_tree ==		== OmaDm -revert_tree ==

@@ Line 101: / Line 101: @@
 Creating a "domain" file and then running "OmaDm -set_domain" results in the contents of the "domain" file being used to generate the PalmOMADMAcc.AppAddr.SrvAddr.Addr node contents (with "https://" prepended and "/palmcsext/swupdateserver" appended to it).
-Examination of a normal device indicates that the "domain" file normally has the contents "ps.palmws.com", resulting in a "https://ps.palmws.com/palmcsext/swupdateserver" value in the DmTree.xml files.
+Examination of a normal device indicates that the "domain" file normally has the contents "ps.palmws.com" (with no terminating newline character), resulting in a "https://ps.palmws.com/palmcsext/swupdateserver" value in the DmTree.xml files.
 == OmaDm -client ==

← Older revision		Revision as of 04:56, 8 July 2011
Line 100:		Line 100:

	Creating a "domain" file and then running "OmaDm -set_domain" results in the contents of the "domain" file being used to generate the PalmOMADMAcc.AppAddr.SrvAddr.Addr node contents (with "https://" prepended and "/palmcsext/swupdateserver" appended to it).		Creating a "domain" file and then running "OmaDm -set_domain" results in the contents of the "domain" file being used to generate the PalmOMADMAcc.AppAddr.SrvAddr.Addr node contents (with "https://" prepended and "/palmcsext/swupdateserver" appended to it).
		+
		+	Examination of a normal device indicates that the "domain" file normally has the contents "ps.palmws.com", resulting in a "https://ps.palmws.com/palmcsext/swupdateserver" value in the DmTree.xml files.
		+
		+	== OmaDm -client ==

@@ Line 1: / Line 1: @@
 This page will document knowledge about OmaDm.  Note that some previous research of the over-the-wire behaviour of OmaDm has been done at [[Update_Service_Trace]].
@@ Line 14: / Line 16: @@
   OmaDm -prepare %X
   OmaDm -report_results
 If you doctor and boot a device with the UpdateDaemon and OmaDm binaries disables, you get the following directory contents:
@@ Line 21: / Line 25: @@
   system_settings.info (contains localeCountry and localeLanguage settings)
   tmp (empty directory)
 If you run "OmaDm -syncdata", a couple of files appear:
@@ Line 32: / Line 38: @@
 The OmaDm binary seems to have support for Sprint, bell, ROW, and Verizon only.  We're not sure whether this is a problem for AT&T or other carrier devices, but we'll assume that it is intentional for the moment.
 Note that while "OmaDm -syncdata" can create the DmTree files from scratch, it gives an error if you run it on files with invalid contents:
@@ Line 80: / Line 82: @@
 The template for DmTree.xml can be found in /usr/share/omadm/DmTree.xml and is populated with the information gained from reading all the input data sources.
 Running "OmaDm -set_domain" results in the following errors:

← Older revision		Revision as of 04:47, 8 July 2011
Line 80:		Line 80:

	The template for DmTree.xml can be found in /usr/share/omadm/DmTree.xml and is populated with the information gained from reading all the input data sources.		The template for DmTree.xml can be found in /usr/share/omadm/DmTree.xml and is populated with the information gained from reading all the input data sources.
		+
		+	Running "OmaDm -set_domain" results in the following errors:
		+
		+	[RdmInitCarrier: 423]: Unrecognized carrier ATT
		+	[RdmSetDomain: 506]: Unable to open /var/lib/software/domain
		+	[SetDomain: 376]: RdmSetDomain error
		+
		+	The first is spurious. The second and third indicate that a "domain" file is required. Perhaps the UpdateDaemon binary supplies this file.
		+
		+	Creating a "domain" file and then running "OmaDm -set_domain" results in the contents of the "domain" file being used to generate the PalmOMADMAcc.AppAddr.SrvAddr.Addr node contents (with "https://" prepended and "/palmcsext/swupdateserver" appended to it).

@@ Line 43: / Line 43: @@
 Removing the DmTree.xml file and re-running "OmaDm -syncdata" is enough to regenerate both files.
-An strace on "OmaDm -syncdata" shows that it accesses the following locations:
+An strace on "OmaDm -syncdata" shows that it reads the following locations:
-  /var/log/omadm.log
+  /usr/share/omadm/DmTree.xml
   /etc/prefs/properties/DMCARRIER
   /dev/tokens/DMCARRIER
   /etc/prefs/properties/PalmSN
   /dev/tokens/PalmSN
   /etc/prefs/properties/DMCLoAUTHNAME
   /dev/tokens/DMCLoAUTHNAME
@@ Line 62: / Line 61: @@
   /etc/prefs/properties/DMSVRoNONCE
   /dev/tokens/DMSVRoNONCE
   /etc/prefs/properties/buildNumber
   /etc/palm-build-info
-The /var/log/omadm.log file also shows that the Telephony Interface Layer is accessed to query the platformType, imei, capabilities and version of the cellular subsystem.
+and writes to:
 An OmaDm binary strings examination shows that /usr/share/omadm/none may be a flag file to disable software updates.
@@ Line 74: / Line 78: @@
 So in general, the DmTree.xml files contain authorisation information, a list of currently installed packages (with a build number for each), and possibly cellular provisioning information (need to check this on a CDMA device).

← Older revision		Revision as of 04:19, 8 July 2011
Line 68:		Line 68:

	The /var/log/omadm.log file also shows that the Telephony Interface Layer is accessed to query the platformType, imei, capabilities and version of the cellular subsystem.		The /var/log/omadm.log file also shows that the Telephony Interface Layer is accessed to query the platformType, imei, capabilities and version of the cellular subsystem.
		+
		+	An OmaDm binary strings examination shows that /usr/share/omadm/none may be a flag file to disable software updates.
		+
		+	It seems that the /etc/prefs/properties directory can use used to override the device tokens and build information. This may be handy for other purposes ...
		+
		+	So in general, the DmTree.xml files contain authorisation information, a list of currently installed packages (with a build number for each), and possibly cellular provisioning information (need to check this on a CDMA device).

← Older revision		Revision as of 04:12, 8 July 2011
Line 66:		Line 66:
	/etc/prefs/properties/buildNumber		/etc/prefs/properties/buildNumber
	/etc/palm-build-info		/etc/palm-build-info
		+
		+	The /var/log/omadm.log file also shows that the Telephony Interface Layer is accessed to query the platformType, imei, capabilities and version of the cellular subsystem.