updates
This commit is contained in:
parent
6bd5d87e40
commit
7443e4f34c
@ -26,8 +26,16 @@ are reset after we know how licensing process is working.
|
|||||||
|
|
||||||
# Docs
|
# Docs
|
||||||
|
|
||||||
|
> Current status: We're searching for a method to decrypt the Private-Key
|
||||||
|
> stored in [`DLS_SI_CERTIFICATE`](doc/database/3-after-upload-license/si_d8c07e4af6a449d0b2dc3faf0e1bf2bd.configuration.json).
|
||||||
|
> Maybe this is our "Key" to sign `config-tokens`. \*
|
||||||
|
|
||||||
Docs and current knowledge can be found in [doc's directory](doc/README.md).
|
Docs and current knowledge can be found in [doc's directory](doc/README.md).
|
||||||
|
|
||||||
|
\* If this is successful, we can try to find a way around this. **I think** we have to completely
|
||||||
|
rebuild the [LicensingFlow](doc/LicensingFlow.md) on our own, to generate a InstanceToken, exchange with Nvidia, upload
|
||||||
|
the License to **our** instance, and with the included certificate and keypair we can fake our licenses.
|
||||||
|
|
||||||
# Official Docs
|
# Official Docs
|
||||||
|
|
||||||
- https://docs.nvidia.com/license-system/latest/index.html
|
- https://docs.nvidia.com/license-system/latest/index.html
|
||||||
|
Loading…
Reference in New Issue
Block a user