Feature request: GUI to prepare pkcs12 certificate + priv_key to aid in RPC calls #14493
weaklysubjective
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Chia's use case and applications are vast. Most apps built on Chia Ecosystem will need access to the node and wallet to make smart contract decisions , be it tipping app, gaming app, or apps with time lock contracts for other use case. The way Chia works today, there isn't a proper native wallet app for the myriad of platforms and operating systems on which gaming apps can be built.
It is best most apps are built to make use of the solid foundation of the Chia Native Wallet via RPC. For security reasons it is not wise to open Wallet ports to the internet and thus all RPC calls are contained within the Local Network of the user. While it is a breeze to install the Chia app, whether it is the CLI only version, Wallet only version or the full node version, it is not that intuitive to code the RPC calls. This document along with the provided example attempts to make it easier to use chia rpc in languages other than python and over a Local Network. To make this possible, as indicated in the title, a built-in feature to make the keys available for cut and paste , upon user completing a passphrase challenge, would be very welcome.
To access Chia services using HTTPS and RPC, such as the Wallet service or Node service, users must use their private certificate and key when making web requests. These certificates and keys can be found in the '.chia' directory under the user's 'home' directory if the Chia client software is installed correctly.
The use of the term 'private key' in this context is misleading as private keys in cryptography are typically associated with identity. However, in this context, it refers to the requirement that Chia requires all RPC services to present a valid certificate via SSL/HTTPS before being allowed to use the service. For more information, see the C# Net5.0 implementation for details.
Please keep in mind that the client wallet should not be exposed and its ports should not be open for public access in most cases."
If implemented this feature will make easier to cut and paste CA pkcs12 (cert + private), node pkcs12(cert+private) , and wallet pkcs12(cert+private) , as three separate 'pfx' files. This makes onboarding easier and even for the moderately experienced , this makes Chia GUI that much more user-friendly.
Beta Was this translation helpful? Give feedback.
All reactions