The algorithm description does not specify the Unicode encoding of the input password.

Specify the Unicode encoding (e.g UTF-16BE, UTF-16LE, etc.)

DocumentProtection
Pg. 1158 Section 2.15.1.28

te

Proposed Disposition of DIS 29500 Comment BR-0006 (Modified: 2008-01-03) Agreed; the following changes will be made to make this assumption explicit in each algorithm: Part 4, ยง2.15.1.28, page 1,158, line 15: First, the UTF-16 encoded password shall be hashed using the following algorithm . The following steps assume that all words are unsigned, the word size is two bytes, and that bit-level SHL/SHR operations shift in the direction of the highest-order and lowest-order bit, respectively. [Example: 0x61 SHR 1 is 0xC2, as 01100001 shifted one position in the direction of its highest-order bit is 11000010. end example] : Similar Comments: CL-0091 , CO-0098 , CZ-0053 , DE-0088 , GB-0220 , GH-0009 , GR-0027 , IN-0075 , IR-0013 , MY-0021 , PT-0039 , US-0052 , UY-0017 , VE-0018

Tag and Go

No Comments

Sorry, the comment form is closed at this time.

  • Argentina (1)
  • Australia (30)
  • Austria (1)
  • Belgium (1)
  • Brazil (64)
  • Bulgaria (3)
  • Canada (79)
  • Chile (217)
  • China (1)
  • Colombia (237)
  • Czech Republic (75)
  • Denmark (168)
  • Ecma (76)
  • Ecuador (1)
  • Finland (15)
  • France (592)
  • Germany (162)
  • Ghana (12)
  • Greece (113)
  • India (82)
  • Iran (58)
  • Ireland (12)
  • Israel (33)
  • Italy (2)
  • Japan (82)
  • Jordan (1)
  • Kenya (81)
  • Malaysia (23)
  • Malta (5)
  • Mexico (7)
  • New Zealand (54)
  • Norway (12)
  • Peru (10)
  • Philippines (7)
  • Poland (4)
  • Portugal (118)
  • Singapore (2)
  • South Africa (17)
  • South Korea (25)
  • Spain (1)
  • Switzerland (19)
  • Thailand (1)
  • Tunisia (3)
  • Turkey (1)
  • UK (635)
  • Uruguay (18)
  • USA (288)
  • Venezuela (73)