hurufu/nexoid-fat-cpp

NEXO Financial Application for Terminals (FAT) implemented in C++

Hi, I am a programmer.

Current (but not active) project is an implementation of a core of NEXO standards. It's a major evolving specificaiton for payment terminals. I've released it as a free (like in "freedom") and opensource software.

If your interested please contact me using an email from the profile.

nexoid-fat-cpp's Issues

Print stacktrace on exceptions

C++23 has new stack trace library, so I can finally have cross-platform stack traces.

Add boost::archive as an alternative serialisation method

It will be useful to exercise the possibility to change at compile time (or even at runtime) the ability to select different serialization methods. This may be needed in the future eg. due to licensing / performance issues. Code more or less is written with this modularity in mind, but this was never actually tested. The easiest way to exercise it to add very simple to use boost::archive serialization.

Integrate some C++ UT framework

Good starting point: https://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#C++

Optimize multile includes

When you compile with -H option then gcc gives a warning:
Multiple include guards may be useful for:
It warns about potential problems if #includes were reordered if I understood this correctly.

I have to investigate and fix this warning.

Consider making this project public

This project doesn't have any business logic so it's OK to publish it even now, I guess.

Transaction is aborted if done in quick succesion

It looks like if a card validty transaction with card insert event is triggered during payment with manual entry the first transaction is aborted with kernel error after PIN entry

Consider adding support for libtirpc as an RPC implementation

Nice task to play with modularity and adding more protocols to a portfolio.

more info just by reading man 3 rpc or man 3 xdr

Add ASN.1 encoder/decoder from asn1scc project

It would be nice to exercise project modularity by integreting different ASN.1 compiler. Current good candidate is https://github.com/ttsiodras/asn1scc

HAP endpoint implementation

Related to nexui task

Design SCAP envelope for use with SP

Right now communication via SP is done using bare SCAP message, so there is no way to add protocol specific or other tags unrelated to NEXO itself. This additional information isn't very important, but in some cases it might be useful.
Examples.

• id - It may be used to figure out the exact order of messages if they were all received in bulk, eg. when client was disconnected for a long time here
• It may be good to add room for possible data needed for authentication, but this should not be rushed, and authentication should be done only by a proper business use case. Maybe SASL should be used instead.

This task will require changes in multiple modules, but it's better to do it sooner than later