You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HTTPS would make PrusaLinks authentication secure as the credentials would be encrypted.
Secure namespaces like .dev would work to access to 3D printer. I use a .dev domain locally. At least Google Chrome does not allow http access on secure namespaces.
In an IoT vlan without internet access Prusa Connect would be no alternative.
Expected functionality
The certchain and private key could be imported from the USB flash drive. Alternatively they cloud stay stored on the flash drive and be loaded on boot since when HTTPS support is desired one would upload via HTTPS anyway.
If there is no user provided (trusted) certificate there should be a untrusted one generated.
The text was updated successfully, but these errors were encountered:
Printer model
MK4S
Describe the feature
HTTPS would make PrusaLinks authentication secure as the credentials would be encrypted.
Secure namespaces like .dev would work to access to 3D printer. I use a .dev domain locally. At least Google Chrome does not allow http access on secure namespaces.
In an IoT vlan without internet access Prusa Connect would be no alternative.
Expected functionality
The certchain and private key could be imported from the USB flash drive. Alternatively they cloud stay stored on the flash drive and be loaded on boot since when HTTPS support is desired one would upload via HTTPS anyway.
If there is no user provided (trusted) certificate there should be a untrusted one generated.
The text was updated successfully, but these errors were encountered: