Re: CFB supported in Windows Mobile 5 ?
- From: walterwkh@xxxxxxxxxxx
- Date: Sun, 30 Dec 2007 09:40:44 -0800 (PST)
Thanks Laszlo, actually I tried, the only valid option for the padding
is PKCS5_PADDING. All other options are invalid, including "0". Yes,
padding and mode of operation are independent, but CFB should have no
padding, so I guess it is not supported in Windows Mobile. I tried in
Windows Mobile 6 and it gives the same result. But MSDN said it is
supported from CE 3.0....
On 12月29日, 上午1時21分, lelteto <lelt...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Padding and mode of operation are independent. If you want no padding, you
should try to set "no padding" via CryptSetKeyParam(KP_PADDING) with DWORD=0
- before you start using the key. The default is padding with PKCS5_PADDING.
(Don't know if it's supported in Windows Mobile.)
Laszlo Elteto
SafeNet, Inc.
"walter...@xxxxxxxxxxx" wrote:
I am using Windows Mobile 5 and AES 128 bit block cipher with 128 bit
key. I found that the ciphertext are always padded no matter which
chaining mode I choose in CryptSetKeyParam. Is CFB supported in
Windows CE 5.0 ?- 隱藏被引用文字 -
- 顯示被引用文字 -
.
- References:
- CFB supported in Windows Mobile 5 ?
- From: walterwkh
- CFB supported in Windows Mobile 5 ?
- Prev by Date: CFB supported in Windows Mobile 5 ?
- Next by Date: RE: accessing SIGNER_ATTR_AUTHCODE structure from C++
- Previous by thread: CFB supported in Windows Mobile 5 ?
- Index(es):