NetBurner Community Forum

I copied it from 3.4.0 it build successfully now.

Since the compcode.exe utility in the /nburn/pcbin directory was already removed by the IT antivirus in version 3.5.0 and 3.5.3, and I have versions 3.3.3 to 3.4.0 installed, could I simply copy the utility from the other version to avoid reinstalling 3.5.0? Or is the compcode.exe utility version ...

It turns out that our IT department has blocked the compcode.exe. They reached out to me for more specific details about this executable

I installed the latest version 3.5.3 and recreated the same TCP/TCPServerSimple example, but I'm encountering the same compcode error, albeit with a different error code: 126 that is permission denied.

I suspect that the path /cygdrive/c/nburn/pcbin/compcode might be incorrect, but I have no idea ...

I am using NANO and Eclipse 3.5.0 (not command line) on Windows, and I am encountering the exact same issue described in this post: https://forum.embeddedethernet.com/viewtopic.php?p=13875&hilit=compcode#p13875 . Despite following all the suggestions in the post, I haven't been able to resolve the ...

using NANO and 3.5.0. It seems that SSH key-based authentication is not yet supported

In my research on SSH so far, apart from password authentication, I understand that an SSH server can authenticate a client using the client’s public key installed on the server.

I reviewed the example ssh ...

I use the default ECC. However there's a HAVE_ECC defined in the \nburn\libraries\include\crypto\platform\NANO54415, my guess is if you commented it out, it will default to RSA. But I didn't test with RSA

with further troubleshoot, I found that was caused by the signature algorithm mismatch with the public key algorithm in the certificate.
Since it's a self signed certificate , the two algorithms in the cert need to be the same, either RSA or ECC.
If a cert was signed by a CA, the signature ...

This reminds me when I first play with SSL a few years ago that having the same problem with 2.9.3. I forget how it get solved, but I think it has to do with subject alternate name.

same to the second problem in the post below
viewtopic.php?t=3055

also if I add a compile server cert and key into the SSH example instead of using the onboard generated cert and key, and that cause the SshAccept function fail and return an error code 304 which is SSH_ERROR_BAD_KEY.
The cert and key are created by OpenSSL and compile into cpp file using ...