pub struct RelayProfile {Show 15 fields
pub id: String,
pub label: String,
pub relay_url: String,
pub user_id: String,
pub device_id: String,
pub hostname: String,
pub encryption_key: String,
pub device_private_key: String,
pub credential_version: u64,
pub token: String,
pub machine_id: String,
pub email: String,
pub identity_provider: String,
pub display_name: String,
pub key_pending: bool,
}Fields§
§id: String§label: String§relay_url: String§user_id: String§device_id: String§hostname: String§encryption_key: String§device_private_key: String§credential_version: u64§token: String§machine_id: StringStable per-machine identifier (opaque hash). Used by the relay to
recognize repeat sign-ins from the same machine and reuse a single
device row instead of creating duplicates. Empty for legacy configs;
backfilled on next save via client_core::machine::stable_machine_id.
email: StringVerified email address returned by the OAuth provider at login time. Empty for legacy configs or when the provider did not return a verified email.
identity_provider: StringOAuth identity provider used for the most recent login (“google” or “github”). Empty for legacy configs.
display_name: StringEffective display name. Set by the user via cinch auth set-name or
the desktop settings UI; falls back to the OAuth-fetched name on
login if the user hasn’t overridden it. Empty for legacy configs.
key_pending: boolMirrors Config::key_pending. See that field’s doc comment for the
full semantics. Defaults to false so configs written by pre-fix
builds — where a fresh AES key was always generated locally —
continue to look “ready” on disk, and only newly-installed devices
(after the fix lands) opt into the pending-key flow.
Implementations§
Trait Implementations§
Source§impl Clone for RelayProfile
impl Clone for RelayProfile
Source§fn clone(&self) -> RelayProfile
fn clone(&self) -> RelayProfile
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more