• AVR Freaks

Hot!Harmony V3 - Web Net Server - WolfSSL generated code broken

Author
XorLor
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2009/10/23 00:17:05
  • Location: 0
  • Status: offline
2019/09/12 10:48:23 (permalink)
0

Harmony V3 - Web Net Server - WolfSSL generated code broken

The pic32mz_ef_sk project from the web_net_server_nvm_mpfs folder does not compile after generating the code using Harmony V3. The project is unmodified. Many errors from the wolfssl generated code. Any suggestions?
 
Using all the latest versions:
MPLABX V5.25
MPLAB XC32 V2.30
net package v3.4.0
 
Errors:
../src/third_party/wolfssl/src/internal.c:2134:37: error: 'sha512_mac' undeclared (first use in this function)
../src/third_party/wolfssl/src/internal.c:2137:37: error: 'sha384_mac' undeclared (first use in this function)
../src/third_party/wolfssl/src/internal.c:2140:37: error: 'sha256_mac' undeclared (first use in this function)
../src/third_party/wolfssl/src/internal.c:2144:37: error: 'sha_mac' undeclared (first use in this function)
../src/third_party/wolfssl/src/internal.c:4625:9: error: implicit declaration of function 'wc_DhCheckPubValue' [-Werror=implicit-function-declaration]
../src/third_party/wolfssl/src/ssl.c:17078:9: error: implicit declaration of function 'wc_GetPubX509' [-Werror=implicit-function-declaration]
asn.h
../src/third_party/wolfssl/src/ssl.c:4499:15: error: 'Signer' has no member named 'selfSigned'
../src/third_party/wolfssl/src/ssl.c:12624:22: error: 'VERIFY_SKIP_DATE' undeclared (first use in this function)
 
 
 
#1

4 Replies Related Threads

    Luca Pascarella
    Starting Member
    • Total Posts : 73
    • Reward points : 0
    • Joined: 2007/05/28 00:53:17
    • Location: The Netherlands
    • Status: offline
    Re: Harmony V3 - Web Net Server - WolfSSL generated code broken 2019/09/12 23:30:38 (permalink)
    5 (1)
    Same issue for me.
     
    The preconfigured web_net_server_nvm_mpfs compiles but when launch Harmony 3 Configurator to regenerate source code the compilation fails. 
    Seems like a misalignment between net and wolf repos.
    #2
    boatbodger
    Starting Member
    • Total Posts : 53
    • Reward points : 0
    • Joined: 2011/03/27 15:39:07
    • Location: 0
    • Status: offline
    Re: Harmony V3 - Web Net Server - WolfSSL generated code broken 2019/10/14 09:07:48 (permalink)
    0
    Similar errors here, mostly regarding missing fields in the definition of the X509 structure.  I suspect this is due to combinations of the feature flags requested, but really don't fancy my chances of sorting this out without diving deep into the wolfssl sources.
     
    As a mattor of information, the source tree for wolfssl is pretty inpenetrable.  The folder 'wolfssl' contains a folder also called 'wolfssl' And I wonder if that is how it is meant to be.  Or not.  Similarly, the folder wolfssl contains a folder wolfcrypt, and a folder of the same name appears in wolfssl/wolfssl.
    A file called ssl.h appears five times in the source tree with sizes ranging from 977 bytes to 381kB.
     
    I'm sure somebody knows how it all works, but I certainly don't :(
    post edited by boatbodger - 2019/10/14 09:14:17
    #3
    BillP
    Super Member
    • Total Posts : 337
    • Reward points : 0
    • Joined: 2014/09/28 07:53:35
    • Location: CA
    • Status: offline
    Re: Harmony V3 - Web Net Server - WolfSSL generated code broken 2019/10/14 15:45:59 (permalink)
    0
    I believe somewhere I saw a notice that Hv3 does not yet support wolfSSL.  If so, Hv3 should not allow you to activate it.  I have found a couple of the demos that work in Hv2 do not work in Hv3. 
    #4
    boatbodger
    Starting Member
    • Total Posts : 53
    • Reward points : 0
    • Joined: 2011/03/27 15:39:07
    • Location: 0
    • Status: offline
    Re: Harmony V3 - Web Net Server - WolfSSL generated code broken 2019/10/14 15:56:44 (permalink)
    0
    I'd be very happy to use the (lighter weight)LibCrypto, but that's not showing up in the MHC.
    FWIW I have managed to 'hack' WolfSSL so it will compile, and I *think* it is working, but I'm now struggling with MPFS/HTTP, which is a completely different story...
     
    UPDATE: I have attached a DIFF file for the changes I had to make to internal.c to get it to compile.
    post edited by boatbodger - 2019/10/15 00:16:20
    #5
    Jump to:
    © 2019 APG vNext Commercial Version 4.5