Remco Burema 34eac462bd More authentication, since printer-API call-responses can include user-info. ... The new regulations make a decent amount of sense -- but just because we agree with them doesn't mean we'd implemented this yet. Anyway, information wich can be used to personally identify people should be kept behind (virtual) locks and bars. The new firmware will only allow certain operations _after_ a request has been made to the .../auth/request endpoint, and someone in the physical vicinity (of the printer) has pressed ALLOW on a popup (with the application and name of the requester shown, on the printers' UI). After that, _as long as you put the relevant Authorization Digest in your HTTP headers_ (and use at least SHA-256), you may proceed to make other requests without the printer-server flipping out with a FORBIDDEN error. The current commit _should_ also still work with printers that still have old (well, current I guess...) firmware -- but I didn't test that yet. CURA-12624		2025-09-10 10:22:59 +02:00
..
__init__.py	Restructure codebase - part 1	2019-07-26 15:07:52 +02:00
ClusterApiClient.py	More authentication, since printer-API call-responses can include user-info.	2025-09-10 10:22:59 +02:00
LocalClusterOutputDevice.py	Fix local cloud printing for um printers	2023-11-27 13:47:08 +01:00
LocalClusterOutputDeviceManager.py	Fix typo	2022-08-30 13:11:42 +02:00
SendMaterialJob.py	Don't sync invisible materials	2023-09-07 13:48:36 +02:00
ZeroConfClient.py	Fix error log spam.	2021-02-26 21:56:33 +01:00