User:Wtv-411/Smart Card - Revision history

Wtv-411: Final touches and fixes

2023-08-05T20:50:22Z

Final touches and fixes

← Older revision		Revision as of 16:50, 5 August 2023
Line 5:		Line 5:
	----		----

	Smart ~~Cards~~ were used on the WebTV and first-generation MSN TV service to take the user to a site, set up ISP options, etc. They were rarely utilized, and were removed on the MSN TV 2.		Smart cards were used on the WebTV and first-generation MSN TV service to take the user to a site, set up ISP options, etc. They were rarely utilized, and were removed on the MSN TV 2.

	WebTV/MSN TV boxes support smart cards that are compliant with the [https://en.wikipedia.org/wiki/ISO/IEC_7816 ISO-7816 standard]. Smart cards can hold up to 122 bytes of data.		WebTV/MSN TV boxes support smart cards that are compliant with the [https://en.wikipedia.org/wiki/ISO/IEC_7816 ISO 7816 standard]. Smart cards can hold up to 122 bytes of data.

	== Inserting a smart card ==		== Inserting a smart card ==
	When a smart card is inserted into the WebTV/MSN TV receiver, it will show a message on the screen with the smart card name and a progress bar. In the background, the box will contact the URL from the <code>wtv-smartcard-inserted-url</code> header sent from headwaiter, which is usually <code>wtv-smartcard:/insert</code>. The box will <code>POST</code> the raw data read from the card to the URL. While official clients can supposedly send the smart card data raw, it has only been documented to send the data as a Base64 encoded string ~~with~~ every 4 ~~bytes~~ swapped:		When a smart card is inserted into the WebTV/MSN TV receiver, it will show a message on the screen with the smart card name and a progress bar. In the background, the box will contact the URL from the <code>wtv-smartcard-inserted-url</code> header sent from headwaiter, which is usually <code>wtv-smartcard:/insert</code>. The box will <code>POST</code> the raw data read from the card to the URL. While official clients can supposedly send the smart card data raw, it has only been documented to send the data as a Base64 encoded string that has every 4-byte block of data byte swapped:

	<pre>		<pre>
Line 34:		Line 34:
	WebTV/MSN TV smart cards use a proprietary format to store data. There are two known versions of the format that WebTV Networks developed: version 1 and version 2. The only smart card known to be produced for WebTV boxes (the Sony smart card bundled with Sony WebTV Plus units) uses the version 2 format, though.		WebTV/MSN TV smart cards use a proprietary format to store data. There are two known versions of the format that WebTV Networks developed: version 1 and version 2. The only smart card known to be produced for WebTV boxes (the Sony smart card bundled with Sony WebTV Plus units) uses the version 2 format, though.

	Thanks to internal WebTV pages from a "smart card factory" service containing JavaScript that directly handled writing in both formats, these formats have been able to be reverse engineered to varying degrees of success. This page will ~~currently~~ only cover the version 2 smart card format ~~though~~, since that is the format we have the most information on.		Thanks to internal WebTV pages from a "smart card factory" service containing JavaScript that directly handled writing in both formats, these formats have been able to be reverse engineered to varying degrees of success. This page will only cover the version 2 smart card format for the time being, since that is the format we have the most information on.

	=== Version 2 ===		=== Version 2 ===
Line 94:		Line 94:

	==== Known TLVs ====		==== Known TLVs ====
	TLVs will be listed by their type code.		Below is a list of TLVs known to be used by the version 2 smart card format. TLVs will be listed by their type code.

	===== "t" (Title) =====		===== "t" (Title) =====
	* Description: Specifies a title to ~~give~~ the smart card. Optional, but has to precede all other TLVs. This TLV can '''not''' be present in deregistration smart cards		* Description: Specifies a title to set for the smart card. Optional, but has to precede all other TLVs. This TLV can '''not''' be present in deregistration smart cards
	* Value: The title for the smart card		* Value: The title for the smart card

Line 104:		Line 104:
	* Value: A byte for the version number (either <code>1</code> for version 1 Affinity data or <code>2</code> for version 2 Affinity data), followed by the actual data.		* Value: A byte for the version number (either <code>1</code> for version 1 Affinity data or <code>2</code> for version 2 Affinity data), followed by the actual data.
	** For version 2 Affinity data: The format is the program code, a tab character (0x09), and the enrollment code		** For version 2 Affinity data: The format is the program code, a tab character (0x09), and the enrollment code
	** For version 1 Affinity data: Just the enrollment code ~~is added~~		** For version 1 Affinity data: Just the enrollment code

	===== "G" (Go To data) =====		===== "G" (Go To data) =====
Line 177:		Line 177:
	\|-		\|-
	\| TLV #2 Type		\| TLV #2 Type
	\| </code>G</code> (Go to)		\| <code>G</code> (Go to)
	\|-		\|-
	\| TLV #2 Length		\| TLV #2 Length

Wtv-411: /* Format */ Remove TODO

2023-08-05T19:55:58Z

Format: Remove TODO

← Older revision		Revision as of 15:55, 5 August 2023
Line 185:		Line 185:
	\| "i999999" (Server-side numeric ID 999999 - pointed to <nowiki>http://www.svalue.com</nowiki> on the original server)		\| "i999999" (Server-side numeric ID 999999 - pointed to <nowiki>http://www.svalue.com</nowiki> on the original server)
	\|}		\|}

	~~'''TODO'''~~
	<!-- G�i appears to stand for "Go To ID", which is the ID for the Go To card. The ID has a corresponding URL that is stored on the server. If the ID is unknown, then a message about the Smart Card being expired or not yet active is sent to the client. The reasoning for this approach appears to be due to the size limit of Smart Cards (around 25 bytes) and so malicious cards can't be spread around. -->		<!-- G�i appears to stand for "Go To ID", which is the ID for the Go To card. The ID has a corresponding URL that is stored on the server. If the ID is unknown, then a message about the Smart Card being expired or not yet active is sent to the client. The reasoning for this approach appears to be due to the size limit of Smart Cards (around 25 bytes) and so malicious cards can't be spread around. -->

Wtv-411: /* Version 2 */

2023-08-05T19:55:31Z

Version 2

← Older revision		Revision as of 15:55, 5 August 2023
Line 64:		Line 64:
	\|}		\|}

	TLVs are simple structures that store data under a specified type. ~~They~~ can ~~technically~~ hold up to 256 bytes of data~~, and~~ follow this format:		TLVs are simple structures that store data under a specified type. While constrained by the 122-byte limit for smart cards, they can theoretically hold up to 256 bytes of data. TLVs follow this format:

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! Field		! Field
	! ~~Type~~		! Length
	! Description		! Description
	\|-		\|-
	\| Type		\| Type
	\| ~~uint8~~		\| 1 byte
	\| Type code		\| Type code
	\|-		\|-
	\| Length		\| Length
	\| ~~uint8~~		\| 1 byte
	\| 8-bit length of value		\| 8-bit length of value
	\|-		\|-
	\| Value		\| Value
	\| ~~Byte array~~		\| Variable
	\| Variable length value data		\| Variable length value data
	\|}		\|}
Line 150:		Line 150:
	\|}		\|}

	==== Example ====		==== Format Example ====
	The following example shows a break down of the data from an official Sony WebTV Plus smart card, which uses the version 2 smart card format and is a "Go to" card. The card would have originally sent to the service a site ID of 999999, which would redirect the user to the Sony-operated site <nowiki>http://www.svalue.com</nowiki> (no longer run by Sony).		The following example shows a break down of the data from an official Sony WebTV Plus smart card, which uses the version 2 smart card format and is a "Go to" card. The card would have originally sent to the service a site ID of 999999, which would redirect the user to the Sony-operated site <nowiki>http://www.svalue.com</nowiki> (no longer run by Sony).

Wtv-411: /* Inserting a smart card */

2023-08-05T19:44:11Z

Inserting a smart card

← Older revision		Revision as of 15:44, 5 August 2023
Line 26:		Line 26:
	<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO -> Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>		<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO -> Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>

	The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> service aren't well known, what is known is that the server will redirect the box to a website specified by the smart card if it is a "Go To" card, and send an error page is the data is invalid.		The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> service aren't well known, what is known is that the server will redirect the box to a website specified by the smart card if it is a "Go To" card, and send an error page if the data is invalid.

	In some cases, the box will send an error header (e.g: "error=-68") if something goes wrong.		In some cases, the box will send an error header (e.g: "error=-68") if something goes wrong.

Wtv-411: /* Inserting a smart card */

2023-08-05T19:43:44Z

Inserting a smart card

← Older revision		Revision as of 15:43, 5 August 2023
Line 26:		Line 26:
	<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO -> Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>		<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO -> Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>

	The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> aren't well known, what is known is that the server will redirect the box to ~~the~~ website if the smart card ~~data~~ is ~~for~~ a "Go To" card and send an error page is the data is invalid.		The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> service aren't well known, what is known is that the server will redirect the box to a website specified by the smart card if it is a "Go To" card, and send an error page is the data is invalid.

	In some cases, the box will send an error header (e.g: "error=-68") if something goes wrong.		In some cases, the box will send an error header (e.g: "error=-68") if something goes wrong.

Wtv-411: Refine more stuff

2023-08-05T19:18:40Z

Refine more stuff

← Older revision		Revision as of 15:18, 5 August 2023
Line 7:		Line 7:
	Smart Cards were used on the WebTV and first-generation MSN TV service to take the user to a site, set up ISP options, etc. They were rarely utilized, and were removed on the MSN TV 2.		Smart Cards were used on the WebTV and first-generation MSN TV service to take the user to a site, set up ISP options, etc. They were rarely utilized, and were removed on the MSN TV 2.

	WebTV/MSN TV boxes support smart cards that are compliant with the ISO-7816 standard. Smart cards can hold up to 122 bytes of data.		WebTV/MSN TV boxes support smart cards that are compliant with the [https://en.wikipedia.org/wiki/ISO/IEC_7816 ISO-7816 standard]. Smart cards can hold up to 122 bytes of data.

	== Inserting a smart card ==		== Inserting a smart card ==
Line 32:		Line 32:
	== Format ==		== Format ==
	<!-- TODO: Redo this entire section to be less sucky - add proper technical info on smart card format and discuss more types -->		<!-- TODO: Redo this entire section to be less sucky - add proper technical info on smart card format and discuss more types -->
	WebTV/MSN TV smart cards use a proprietary format to store data. There are two known versions of the format that WebTV Networks developed: version 1 and version 2. The only smart card known to be produced for WebTV boxes (the Sony smart card bundled with Sony ~~INT-W200 Internet Terminals~~) uses the version 2 format, though.		WebTV/MSN TV smart cards use a proprietary format to store data. There are two known versions of the format that WebTV Networks developed: version 1 and version 2. The only smart card known to be produced for WebTV boxes (the Sony smart card bundled with Sony WebTV Plus units) uses the version 2 format, though.

	Thanks to internal WebTV pages from a "smart card factory" service containing JavaScript that directly handled writing in both formats, these formats have been able to be reverse engineered to varying degrees of success. This page will currently only cover the version 2 smart card format though, since that is the format we have the most information on.		Thanks to internal WebTV pages from a "smart card factory" service containing JavaScript that directly handled writing in both formats, these formats have been able to be reverse engineered to varying degrees of success. This page will currently only cover the version 2 smart card format though, since that is the format we have the most information on.
Line 108:		Line 108:
	===== "G" (Go To data) =====		===== "G" (Go To data) =====
	* Description: Data that defines a website the smart card will make the box access. The wtv-smartcard service would have taken care of redirecting the client to the specified site if it existed. Required for "Go To" smart cards		* Description: Data that defines a website the smart card will make the box access. The wtv-smartcard service would have taken care of redirecting the client to the specified site if it existed. Required for "Go To" smart cards
	* Value: A byte for the type of website to be accessed (<code>i</code> - Server-side numeric ID that will be translated by the WebTV/MSN TV service, <code>h</code> - HTTP URL, <code>s</code> - HTTPS URL), followed by a numeric ID if the type is <code>i</code>, or the direct URL for the site without the "http(s)://" prefix.		* Value: A byte for the type of website to be accessed (<code>i</code> - Server-side numeric ID that will be translated by the WebTV/MSN TV service, <code>h</code> - HTTP URL, <code>s</code> - HTTPS URL), followed by a numeric ID if the type is <code>i</code>, or the direct URL for the site without the "http(s)://" prefix otherwise

	===== "O" (OpenISP) =====		===== "O" (OpenISP) =====
	* Description: Data for setting up a predefined custom ISP to connect to WebTV/MSN TV with. Required for OpenISP smart cards		* Description: Data for setting up a predefined custom ISP to connect to WebTV/MSN TV with. Required for OpenISP smart cards
	* Value: "1", followed by the ISP data separated with a tab character (0x09)		* Value: The character "1", followed by the ISP data separated with a tab character (0x09)

	ISP information structure:		ISP information structure:
Line 151:		Line 151:

	==== Example ====		==== Example ====
	The following example shows a break down of the data from an official Sony ~~INT-W200~~ smart card, which uses the version 2 smart card format and is a "Go to" card. The card would have originally sent to the service a site ID of 999999, which would redirect the user to the Sony-operated site <nowiki>http://svalue.com</nowiki> (no longer run by Sony).		The following example shows a break down of the data from an official Sony WebTV Plus smart card, which uses the version 2 smart card format and is a "Go to" card. The card would have originally sent to the service a site ID of 999999, which would redirect the user to the Sony-operated site <nowiki>http://www.svalue.com</nowiki> (no longer run by Sony).

	{\| class="wikitable"		{\| class="wikitable"
Line 159:		Line 159:
	\|-		\|-
	\| Version		\| Version
	\| "2" (0x32)		\| <code>2</code> (0x32)
	\|-		\|-
	\| Type		\| Type
	\| "G" (Go to)		\| <code>G</code> (Go to)
	\|-		\|-
	\| CRC		\| CRC
Line 168:		Line 168:
	\|-		\|-
	\| TLV #1 Type		\| TLV #1 Type
	\| "t" (Title)		\| <code>t</code> (Title)
	\|-		\|-
	\| TLV #1 Length		\| TLV #1 Length
Line 177:		Line 177:
	\|-		\|-
	\| TLV #2 Type		\| TLV #2 Type
	\| "G" (Go to)		\| </code>G</code> (Go to)
	\|-		\|-
	\| TLV #2 Length		\| TLV #2 Length
Line 183:		Line 183:
	\|-		\|-
	\| TLV #2 Value		\| TLV #2 Value
	\| "i999999" (Server-side numeric ID 999999 - ~~points~~ to <nowiki>http://svalue.com</nowiki> on the original server)		\| "i999999" (Server-side numeric ID 999999 - pointed to <nowiki>http://www.svalue.com</nowiki> on the original server)
	\|}		\|}

Wtv-411: /* Version 2 */

2023-08-05T19:02:56Z

Version 2

← Older revision		Revision as of 15:02, 5 August 2023
Line 57:		Line 57:
	\| 0x02		\| 0x02
	\| 1 byte		\| 1 byte
	\| CRC value. This is an optional field and a value of 0xff can be specified to make WebTV/MSN TV ignore the CRC		\| CRC value. This is an optional field and a value of 0xff can be specified to make WebTV/MSN TV ignore the CRC. The actual algorithm used for this CRC is currently unknown
	\|-		\|-
	\| 0x03		\| 0x03

Wtv-411: Add section to mention SaveToSmartCard client command

2023-08-05T18:59:31Z

Add section to mention SaveToSmartCard client command

← Older revision		Revision as of 14:59, 5 August 2023
Line 9:		Line 9:
	WebTV/MSN TV boxes support smart cards that are compliant with the ISO-7816 standard. Smart cards can hold up to 122 bytes of data.		WebTV/MSN TV boxes support smart cards that are compliant with the ISO-7816 standard. Smart cards can hold up to 122 bytes of data.

	== ~~Service Side~~ ==		== Inserting a smart card ==
	When a smart card is inserted into the WebTV/MSN TV receiver, it will show a message on the screen with the smart card name and a progress bar. In the background, the box will contact the URL from the <code>wtv-smartcard-inserted-url</code> header sent from headwaiter, which is usually <code>wtv-smartcard:/insert</code>. The box will <code>POST</code> the raw data read from the card to the URL. While official clients can supposedly send the smart card data raw, it has only been documented to send the data as a Base64 encoded string with every 4 bytes swapped:		When a smart card is inserted into the WebTV/MSN TV receiver, it will show a message on the screen with the smart card name and a progress bar. In the background, the box will contact the URL from the <code>wtv-smartcard-inserted-url</code> header sent from headwaiter, which is usually <code>wtv-smartcard:/insert</code>. The box will <code>POST</code> the raw data read from the card to the URL. While official clients can supposedly send the smart card data raw, it has only been documented to send the data as a Base64 encoded string with every 4 bytes swapped:

Line 188:		Line 188:
	'''TODO'''		'''TODO'''
	<!-- G�i appears to stand for "Go To ID", which is the ID for the Go To card. The ID has a corresponding URL that is stored on the server. If the ID is unknown, then a message about the Smart Card being expired or not yet active is sent to the client. The reasoning for this approach appears to be due to the size limit of Smart Cards (around 25 bytes) and so malicious cards can't be spread around. -->		<!-- G�i appears to stand for "Go To ID", which is the ID for the Go To card. The ID has a corresponding URL that is stored on the server. If the ID is unknown, then a message about the Smart Card being expired or not yet active is sent to the client. The reasoning for this approach appears to be due to the size limit of Smart Cards (around 25 bytes) and so malicious cards can't be spread around. -->

			== Client-Side ==

			WebTV and MSN TV boxes have the ability to write to compatible smart cards inserted into their smart card slot. This is done with the client command <code>client:SaveToSmartCard?data={data}</code>, with <code>{data}</code> being the raw smart card data, which can be URL encoded if necessary.

Wtv-411: /* Service Side */

2023-08-05T18:50:57Z

Service Side

← Older revision		Revision as of 14:50, 5 August 2023
Line 24:		Line 24:
	</pre>		</pre>

	<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO~~</code>~~ -> ~~<code>~~Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>		<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO -> Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>

	The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> aren't well known, what is known is that the server will redirect the box to the website if the smart card data is for a "Go To" card and send an error page is the data is invalid.		The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> aren't well known, what is known is that the server will redirect the box to the website if the smart card data is for a "Go To" card and send an error page is the data is invalid.

Wtv-411: /* Service Side */

2023-08-05T18:50:24Z

Service Side

← Older revision		Revision as of 14:50, 5 August 2023
Line 23:		Line 23:
	/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO		/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO
	</pre>		</pre>

			<code>/fkMTtAd552bhZFIlVHbHcEI5kTa5kTO==QO</code> -> <code>Mkf/dAtTb255IFZhbHVlIEcHaTk5OTk5OQ==</code>

	The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> aren't well known, what is known is that the server will redirect the box to the website if the smart card data is for a "Go To" card and send an error page is the data is invalid.		The server will unswap the bytes, decode the data into its raw binary form, and then parse it as smart card data to determine what to do with it. While the specifics of the <code>wtv-smartcard</code> aren't well known, what is known is that the server will redirect the box to the website if the smart card data is for a "Go To" card and send an error page is the data is invalid.