Unencrypted System Logs

Feature Request
,
1

At present (1.4.1), system logs can only be exported as an encrypted file for analysis by Snapmaker Support.

  1. The content of these logs is sure to be of interest to experienced users keen to make full use of their U1, maintain it, and perhaps experiment with it. If the data is not human readable, please provide tools to read it.
  2. Being encrypted means users have no visibility of what information they are submitting to Snapmaker, nor what privacy implications there might be.
2 Likes
Firmware Wishlist
2

I agree with you. Other manufacturers also encrypt diagnostic logs, partly to preserve their integrity in the event of warranty disputes. However, I believe that an identically complete version, freely accessible to the user, should always be provided alongside the encrypted file, so users can review exactly what information they are submitting to Snapmaker.

3

OK, so have an encrypted detailed system log and an in-the-clear summary log. But that would still not address the issue of user’s privacy, and we should all be nervous of exporting personal data across national borders.

I, for one, am only using my U1 in LAN mode, and will be very reticent of sending logs to Snapmaker.

4

If you put it that way, depending on the code, even LAN mode could be used to leak data to overseas servers.
If you really don’t want that, your only options are to change your router settings to prevent data from flowing outside your network or to completely cut off access to the outside world.
Indirectly, through invisible program code, this is essentially no different from what you’re concerned about.

The same goes for the apps on your smartphone.

If you download and use any apps on your smartphone, what kind of information is flowing internally is, in the same way, a matter of the developer’s character and ethics.