Quote
soju - 2023-01-08 4:23 AM
Compiler bundled with WEC7 (cl.exe 15.00.20720 for MIPS) doesn't allow targetting to WinCE 4.00 or prior. I won't make a build for 4.00 or earlier.
Hey, I'm very sorry about that - I was just attempting to see if I could somehow assist in testing to help figure out what happened with DutchComputerKid's device.
Quote
watamario15 - 2023-01-09 1:06 AM
Quote
soju - 2023-01-08 7:23 PM
Compiler bundled with WEC7 (cl.exe 15.00.20720 for MIPS) doesn't allow targetting to WinCE 4.00 or prior. I won't make a build for 4.00 or earlier.
I think you could build nPOPuk and OpenSSL with Visual C++ 6.0 with CE 2.11 SDK, right? In that case, could you build using it again? Although it had a resource issue it's easy to mitigate by just adding a resource manually. I suspect the current MIPS issue is caused by using some OS features that DutchComputerKid's device doesn't have. As in, if it lacks some libraries or has wrong CPU, OS will notify the issue when you try to launch and doesn't open at all.
To the best of my knowledge, when soju used the 2.11 SDK was simply to restore the lack of UI buttons in nPOPuk in one of the betas - I don't believe the 2.11 SDK was ever used to compile OpenSSL per se
Quote
C:Amie - 2022-12-18 2:44 AM
Quote
soju - 2022-12-18 1:30 AM
Thank you for really helpful investigation.
It is implied that CryptAcquireContextW, and CryptReleaseContext, CryptGenRandom are commonly not available prior WinCE 3.0 by source code comment in OpenSSL0.9.8zh.
--
(crypto/rand/rand.win.c)
# if defined(OPENSSL_SYS_WINCE)
# if defined(_WIN32_WCE) && _WIN32_WCE>=300
/*
* Even though MSDN says _WIN32_WCE>=210, it doesn't seem to be available
* in commonly available implementations prior 300...
*/
{
BYTE buf[64];
/* poll the CryptoAPI PRNG */
/* The CryptoAPI returns sizeof(buf) bytes of randomness */
if (CryptAcquireContextW(&hProvider, NULL, NULL, PROV_RSA_FULL,
--
However, assuming torch is usign WinCE 4.2 device (NEC MobilePro 900), those implementation can be in its coredll.dll?
To confirm that, you can put attached coredll.dll in the same directory with nPOPuk.exe and execute it. I guess it will run. The coredll.dll will be removed once the test is done.
https://www.dropbox.com/sh/9xmy7e32ldn44ap/AAB4k6dl6Vs7xsKqYx5gFmwja?dl=0
I can check whether there are those implementations in your system installed coredll.dll if you share it.
Wouldn't be the first time MSDN was wrong, but it might be platform specific. A full H/PC should be MAXALL, but older devices may have been ROM constrained. The MP900 was certainly MAXALL.
This was an earlier post which I believe is of reference in regards to OpenSSL and its required API functions for the different Windows CE versions.
Thus in summary:
soju is working on getting OpenSSL 3.0 functional on Windows CE 4.0 +
gjcoram is working on getting OpenSSL 1.1.1 functional on Windows CE 2.11 +
Either way, when both are finished, we'll have a much higher baseline than OpenSSL 0.9.x
Edited by torch 2023-01-09 3:19 PM
