- Posts: 1
- Joined: Fri May 16, 2025 11:07 pm
- Real Name: Paul Kerrigan
Fri May 16, 2025 11:17 pm
It's great that Blackmagicdesign have added some level of security to the product with two tiers of user (admin and standard), and with read/write security per user per share - kudos. It's a pity that it still requires the proprietary admin tool rather than a web interface, but at least that's reliable.
Two issues:
1. whatever implementation of SMB is being used by 1.6 (and 1.6.1) it would be great to have the full details. Since this upgrade, the 'Hybrid Backup Sync' tool on QNAP is no longer able to mount shares on the Cloud Pod. I've tested with new users/rights etc- and it absolutely won't connect under 1.6 or 1.6.1, but continues to connect happily to Windows servers, Synology and Terramaster NAS. While it could be an implementation issue on the QNAP side, it does rather look more likely to be the Cloud Pod ((Synology also unable to connect to the cloud Pod, haven't tried from the terramaster.
Rollback to 1.5 and all works - albeit insecurely.
2. Certificates - the implementation of certificates (and reference to SSL instead of TLS) is not ideal. Firstly, it insists on the ".local" name, which is ...not great and secondly/more importantly, it doesn't work; once a new cert is signed by our internal CA and then uploaded/accepted by the cloud pod, the 'setup' management tool is no longer able to access it, giving an error about SSL - despite having the CA installed at machine and user levels as a trusted root authority AND this same CA's certs working fine for countless other devices on the same client PC.
Am happy to do any testing that might help
Two issues:
1. whatever implementation of SMB is being used by 1.6 (and 1.6.1) it would be great to have the full details. Since this upgrade, the 'Hybrid Backup Sync' tool on QNAP is no longer able to mount shares on the Cloud Pod. I've tested with new users/rights etc- and it absolutely won't connect under 1.6 or 1.6.1, but continues to connect happily to Windows servers, Synology and Terramaster NAS. While it could be an implementation issue on the QNAP side, it does rather look more likely to be the Cloud Pod ((Synology also unable to connect to the cloud Pod, haven't tried from the terramaster.
Rollback to 1.5 and all works - albeit insecurely.
2. Certificates - the implementation of certificates (and reference to SSL instead of TLS) is not ideal. Firstly, it insists on the ".local" name, which is ...not great and secondly/more importantly, it doesn't work; once a new cert is signed by our internal CA and then uploaded/accepted by the cloud pod, the 'setup' management tool is no longer able to access it, giving an error about SSL - despite having the CA installed at machine and user levels as a trusted root authority AND this same CA's certs working fine for countless other devices on the same client PC.
Am happy to do any testing that might help