How to enable encrypt()/decrypt() to produce the same result in 16 and 32 bits version? So far I noticed a 16-bit decrypt() can't correctly decrypt a string encrypted by a 32-bit encrypt().
Any help is much appreciated as it's quite urgent.
TIA.
Hua,
We are going to review this issue as soon as possible.
We are actually at Holland providing a FWPPC seminar but today we will look for some free time to review it
Thanks Antonio. Appreciate it 
Hua,
We have tested it in both 16 and 32 bits and the results are the same.
Could you please provide a sample where the encrypted result is different ? thanks
#include "FiveWin.ch"
function Main()
local oDlg, oIco, cId := "SUPERVISOR"
DEFINE ICON oIco FILE "..\icons\fivewin.ico"
DEFINE DIALOG oDlg TITLE "I am a DialogBox" COLOR "W+/B" ;
ICON oIco
@ 3, 5 BUTTON "Run module" SIZE 40, 12 ;
ACTION winexec("exe16.exe "+encrypt(trim(cId)) )
ACTIVATE DIALOG oDlg CENTERED
return nil#include "fivewin.ch"
function main16(cID)
default cId := ""
msginfo(decrypt(trim(cID)))
return nilHua,
Thats risky: the encrypted result may contain embedded zeroes that the application initialization may not properly parse.
Better write the encrypted text to a file and read that file from the 16 bits EXE
Hua,
>Better write the encrypted text to a file and read that file from the 16 bits EXE
If you do this, don't forget to securely erase the file after reading it. I don't mean to just delete it, but to write dummy data to it multiple times before deleting it.
James
Antonio, James, thanks for the feedback and input. It never occur to me that passing encrypted string as I was doing could be problematic as the string length stays the same in exe32 and exe16.
Hua,
I don't know if this will work, but you could try:
@ 3, 5 BUTTON "Run module" SIZE 40, 12 ;
ACTION winexec([exe16.exe ]+["]+encrypt(trim(cId))+["] )
Enclosing the passed parameter in quotes may fix any problems with spaces in cID.
James
@ 3, 5 BUTTON "Run module" SIZE 40, 12 ;
ACTION winexec("exe16.exe "+cmimeenc(encrypt(trim(cId))) )msginfo(trim(decrypt(cmimedec(cId))))Hua,
>Thanks for the idea James. I just find it odd that if both the above samples are compiled in 16-bit I do get the expected string i.e. SUPERVISOR.
Granted that does seem odd. Are you using the same versions of FW and FWH? Perhaps there was a change in the versions that is causing the problem rather than 16bit vs 32bit.
James
James,
There have not been changes in functions Encrypt() and Decrypt() source code. Its easy to check that their results are compatible, so Hua problem has to be something else. Maybe something related to calling 16 bits from 32 bits.
James wrote:
@ 3, 5 BUTTON "Run module" SIZE 40, 12 ;
ACTION winexec([exe16.exe ]+["]+encrypt(trim(cId))+["] )
James wrote:
Granted that does seem odd. Are you using the same versions of FW and FWH? Perhaps there was a change in the versions that is causing the problem rather than 16bit vs 32bit.
Hence my reluctance to touch anything that's working fine so I left my 16-bit programs with FW16. I doubt there was a change, if there was, a lot more people would've been affected.AlexSchaft wrote:
Another trick I use where high (>127) ascii and low(<32) can be tricky is to mime encode the strings