at_client_cli 1.0.0
at_client_cli: ^1.0.0 copied to clipboard
The Atsign Protocol for Dart command-line programs, daemons and servers - CLIBase, and the at_activate and at_register tools.
1.0.0 #
- docs: Upgrading to at_client 4.0 takes an app from at_client 3 to 4.
- feat:
at_activate approvewarns when it approves a request made at the legacy key exchange on an atSign that publishes a namespace key: the approval conveys none of the atSign's namespace keys, and revoking it with theat_activate revokecommand it prints and requesting again at--posture pqReadyconveys them. - feat: a
CLIBaseprogram that cannot reach the atServer names the atDirectory address and what failed. - feat: a
CLIBaseprogram whose keyfile holds no credential, as a denial, a cancel or an expiry leaves it, says so on stderr and stops at once. - feat: a
CLIBaseprogram shows the SDK's warnings on stderr by default, such as a notification it could not decrypt;-vshows the rest. - feat:
at_register, andat_activate onboardwithout-c, ask the registrar with the API key inAT_REGISTRAR_API_KEYwhen it is set, and otherwise with a built-in key, so both work without it. A key that is set but holds a character an HTTP header cannot carry is refused before anything is sent. - feat: a program built on
CLIBasewhose keyfile still holds only its enrollment request waits for the approval, as at_activate does, and then runs, rather than throwing. - feat: instances of a program that share a keyfile opened through
CliKeys.fileFor, asCLIBaseopens it, retrofit it one at a time. - feat: at_client_cli is at_onboarding_cli and at_cli_commons in one package:
CLIBase, the at_activate and at_register tools, and the library behind them.AtActivate.mainandAtRegister.mainrun the tools inside another program. - feat:
package:at_client_cli/at_client_cli.dartis the only SDK import a command-line program needs: it re-exports at_client's native API, the Hive, SQLite and in-memory stores, at_client's mixins (AtClientInvitations,EnrollmentUpdater),RegistrarServiceand the io logging handlers. - feat:
CliKeys.fileForandCliKeys.storageForare the keyfile and local store a command-line program keeps for an atSign, ready for at_client'sAtsign.activate,openandenroll. - feat:
lookUpsFor(rootDomain)gives a program that opens its own client the connectionsCLIBasemakes, through a proxy when the root domain names one (proxy:host:port). - feat:
createAtClientopens a command's client from its keyfile, syncing nothing, as at_activate's commands do. It takes at_onboarding_cli 2.0.0-rc8's parameters, so a program that called it there compiles unchanged. - breaking:
AtOnboardingService,AtOnboardingPreference,OnboardingUtil,AuthKeyType,MySyncProgressListener,EnrollmentDetails,PrintAllArgParserUsageand theAtOnboardingExceptionfamily are not carried over. A program opens its client withCLIBaseorAtsign.open; the README's migration table names what replaces each. - breaking:
CLIBase'spreferenceis anAtClientPreference. - breaking:
CLIBasetakes no-d/--legacy-root-domain, so use-r/--root-server, andCLIBase.createArgsParserandfromCommandLineArgstake noaddLegacyRootDomainArg.at_activate's-dis still the device name. The tools take no--hashingAlgoType, which did nothing. - breaking:
CLIBasetakes nodownloadDir, which nothing read. - breaking:
CLIBasethrowsAtCredentialRefusedExceptionfor every refusal andSecondaryNotFoundExceptionfor an atSign the atDirectory does not know;SecondaryServerConnectivityExceptionnow means only an outage. - fix: on Windows,
standardAtClientStorageDirreturns its directory underTEMPrather than overflowing the stack. - fix:
at_activate autogoes on listening after an enrollment request it cannot read or act on, which it reports on stderr, until it has approved as many as it was asked to. - fix: with debug logging on, a registrar request is logged by its URL and response status, never by its body.
- fix:
RegistrationFlow.start, and soRegister.main, throw anAtClientExceptionwhen the registrar refuses a step. - fix: at_activate's
--mcasets how many times a command tries to connect, three seconds apart; the default of 10 waits about 30 seconds. - fix: at_register exits with at_activate's non-zero code, instead of 0, when the activation after registration fails.
- fix: at_register confirms a verification code the registrar accepts with a follow-up at once, so the third code accepted still gets the CRAM key. A registrar that asks again to confirm a confirmed code ends the registration with exit 4.
- fix: the at_activate Dockerfile builds from the repo root on Dart 3.
- fix: at_register exits 5, not 4, after three refused verification codes, and asks for no fourth code.