khronokernel
commented
1 year ago Project now supports both HTTP and HTTPS, however testing HTTPS will need extra work. Currently our self-signed certificate is not valid:
SAPCorp: ERROR! Remote logging failed: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “192.168.50.9” which could put your confidential information at risk."
Currently system relies on a basic, unencrypted TCP/UDP packet for passing data to a remote logging server. As our client may input sensitive information (ex. Medical Info) in areas such as
ReasonRequired, best to add some extra protection especially if a malicious actor may be sniffing network traffic on the client site.Responsible code for current remote logging system
Switching to HTTP/HTTPS also allows for greater stability since we can rely on libraries such as FastAPI which has been proven to be extremely resilient. Should reduce the amount of logic required in our
Privileges-Logging-Server.We'll likely want to also implement a public and private key system, where clients will encrypt the packet using a public key that only the server's private key can decrypt.