NQjj:UdZddlmZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl ZddlZddlZddlmZddlmZmZmZmZddlmZmZmZmZddlm Z m!Z!ej"e#Z$dZ%d e%Z&d e%d Z'd Z(d Z)ee*e*e*fZ+iZ,de-d<dZ.dWdZ/ee.e/Z0de-d<dXdYdZ1dZdZ2ddd[d"Z3d\d#Z4d\d$Z5dd%d]d'Z6d^d+Z7d_d.Z8d`d0Z9dad4Z:dbd7Z;dcd9ZdId/bin/bws`` on first use. Hermes pins one version (``_BWS_VERSION``) and downloads the matching asset from the official GitHub Releases page, verifying the SHA-256 against the release's published checksum file. * The access token is stored in ``~/.hermes/.env`` as ``BWS_ACCESS_TOKEN`` (or whatever name the user picked in ``secrets.bitwarden.access_token_env``). This is the one bootstrap secret — every other provider key can live in Bitwarden. * Pulling secrets is a single ``bws secret list --output json`` call. We cache the result in-process for ``cache_ttl_seconds`` so back-to-back ``hermes`` invocations don't hammer the API. * Failures NEVER block Hermes startup. Missing binary, no network, expired token, etc. all emit a one-line warning and continue with whatever credentials ``.env`` already had. The module is intentionally subprocess-driven rather than going through the ``bitwarden-sdk-secrets`` Python package: one cross-platform binary is easier to lazy-install than a wheels-with-Rust-extension dependency. ) annotationsN)Path)DictListOptionalTuple) CachedFetch DiskCache FetchResultis_valid_env_name) ErrorKind SecretSourcez2.0.0z;https://github.com/bitwarden/sdk-sm/releases/download/bws-vzbws-sha256-checksums-z.txt<zDict[_CacheKey, _CachedFetch]_CACHEzbws_cache.json cache_key _CacheKeyreturnstrc"|\}}}|d|d|S)z:Serialize a cache key to a stable string for JSON storage.|)rtoken_fp project_id server_urls B/home/alina/.hermes/hermes-agent/agent/secret_sources/bitwarden.py_cache_key_strr`s*'0$Hj* 2 2 2 2j 2 22)key_serializerr _DISK_CACHE home_pathOptional[Path]rc6t|S)zReturn the disk cache path under hermes_home/cache/. Thin wrapper over the shared DiskCache, kept for tests and any direct callers; falls back to `$HERMES_HOME` / `~/.hermes` when home is None. )r pathr!s r_disk_cache_pathr&ks   I & &&rc(ddlm}|dz S)z9Where Hermes stores its managed binaries. Profile-aware.rget_hermes_homebin)hermes_constantsr)r(s r_hermes_bin_dirr,ys'000000 ?  u $$rFinstall_if_missingr.boolc|ttz }|r!tj|tjr|St jd}|rt|S|rB tS#t$r&}t d|Yd}~dSd}~wwxYwdS)uRReturn a path to a usable ``bws`` binary, or None. Resolution order: 1. ``/bin/bws`` (our managed copy — preferred) 2. ``shutil.which("bws")`` (system PATH) When ``install_if_missing`` is True and neither resolves, this calls :func:`install_bws` to download and verify the pinned version. bwszbws auto-install failed: %sN) r,_platform_binary_nameexistsosaccessX_OKshutilwhichr install_bws Exceptionloggerwarning)r.managedsystemexcs rfind_bwsr@s"7"9"99G~~BIgrw77 \% F F|| ==     NN8# > > >44444  4s; B B9B44B9c8tjdkrdndS)NWindowszbws.exer1)platformr>rrrr2r2s ))Y6699EArctj}tj}|dkr dtdS|dkr|dvrdnd}d|d tdS|d kr|dvrdnd}d } t jd d gdddt j}d|j|j zvrd}n#tt j f$rYnwxYwd|d|dtdStd|d|)uMap (uname, arch, libc) → the upstream asset filename. Asset names follow Rust's target triple convention. Linux defaults to gnu (glibc); we switch to musl only if ldd --version says so. Darwinzbws-macos-universal-z.ziprB)arm64aarch64rGx86_64zbws-z-pc-windows-msvc-Linuxgnulddz --versionT)capture_outputtexttimeoutstdinmuslz-unknown-linux--z+Unsupported platform for bws auto-install:  ) rCr>machinelower _BWS_VERSION subprocessrunDEVNULLstdoutstderrOSErrorTimeoutExpired RuntimeError)r>rTarchlibcress r_platform_asset_namerbsm _  F  &&((G 9l8888 #';;;yy?d??\???? #';;;yy . $# ( C#*sz188::::23    D DdDD4DD,DDDD HfHHwHH  s7A CCC)forcercc \t}|dd|tz }|r|s|St }t d|}t dt }tjd5}t|}||z }|t z } t d|t||t|| t| |} t|} | | krt!d|d| d | t#j|5} t'| t} t)| | |}d d d n #1swxYwYtjt-|d \}}t/j|t3j||t/j|t8jt8jzt8jzt8j zt8j!zt8j"zt8j#zt/j$||d d d n #1swxYwYt d tJ||S)uZDownload, verify, and install the pinned ``bws`` binary. Returns the path to the installed executable. Raises on any failure (network, checksum, extraction) — callers in the auto-install path catch these; the user-facing ``hermes secrets bitwarden setup`` surface lets them propagate so the wizard can show a clear error. T)parentsexist_ok/z hermes-bws-)prefixzDownloading %szChecksum mismatch for z : expected z, got Nz.bws_)dirrhzInstalled bws %s at %s)&r,mkdirr2r3rb_BWS_RELEASE_BASE_BWS_CHECKSUM_NAMEtempfileTemporaryDirectoryrr;info_http_download_expected_sha256 _sha256_filerUr^zipfileZipFile_pick_zip_member_safe_extract_membermkstemprr4closer7copy2chmodstatS_IRUSRS_IWUSRS_IXUSRS_IRGRPS_IXGRPS_IROTHS_IXOTHreplacerV)rcbin_dirtarget asset_name asset_url checksum_urltmpdirtmpzip_path checksum_pathexpectedactualzfmember extractedfdstageds rr9r9sG MM$M... ,.. .F }}u %''J$33z33I'>>*<>>L  $M : : :$#f6ll#00  $i000y(+++|]333#M:>>h'' >>  v||~~ - -555$55,255  _X & & >"%b*?*A*ABBF -R==I  > > > > > > > > > > > > > > >%#g,,wGGG F   Y'''   L4< '$, 6l !\ *l !\ *   66"""I$#$#$#$#$#$#$#$#$#$#$#$#$#$#$#L KK(,??? Ms8CJ.F JF JF CJJJurldestNonectj|ddi} tj|t5}t |d5}t j||dddn #1swxYwYddddS#1swxYwYdS#tjj $r}td|d||d}~wwxYw)Nz User-Agentz hermes-agent)headers)rOwbzFailed to download : ) urllibrequestRequesturlopen_BWS_DOWNLOAD_TIMEOUTopenr7 copyfileobjerrorURLErrorr^)rrreqrespfr?s rrprpsd . |^.L M MCH ^ # #C1F # G G ,4dD!! ,Q"4+++ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , < HHH=====>>CGHs_&B# BA>2 B>B BB B B#BB#BB##C7C  C checksum_filerc0|dd}|D]Q}|}t |dkr|d|kr |dcSRt d|d|j) zParse the upstream ``bws-sha256-checksums-X.Y.Z.txt`` file. Format is the standard ``sha256sum`` output: `` ``, one per line. utf-8r)encodingerrorsrLrzNo checksum entry for z in ) read_text splitlinesstripsplitlenr^name)rrrNlinepartss rrqrqs  " "GI " F FD!! ""$$ u::??uRyJ668OOO EEE1CEE  rr$ctj}t|d5tfddD]}|| dddn #1swxYwY|S)Nrbc.dS)Ni)read)rsrz_sha256_file..$s!&&--rr)hashlibsha256riterupdate hexdigest)r$hchunkrs @rrrrr!sA dD  Q////55  E HHUOOOO  ;;==s,AA"%A"rzipfile.ZipFile binary_namecfd|D}|s0tdd|ddd|t|dS) zFind the binary inside the upstream zip. Historically the archive has been flat (``bws`` at the root) but we tolerate a top-level directory just in case upstream changes. cRg|]#}|ddk!|$S)rgr)r).0nrs r z$_pick_zip_member../s2NNNaggcll2.>+.M.M!.M.M.MrzCould not find z% inside downloaded archive (members: Nz...))keyr)namelistr^sortr)rr candidatess ` rruru)s ONNNR[[]]NNNJ   1k 1 1rr* 1 1 1   OOO a=rrdest_dirctj|}tjtj||} tj||g|k}n#t $rd}YnwxYw|r||krt d|d|||t|S)aMExtract a single archive member, refusing path traversal. ``ZipFile.extract`` will happily honour member names containing ``../`` or absolute paths, letting a malicious archive write outside ``dest_dir`` (a "zip-slip"). We resolve the would-be target and confirm it stays within ``dest_dir`` before extracting. Fz*Refusing to extract unsafe archive member z%: it escapes the extraction directory) r4r$realpathjoin commonpath ValueErrorr^extractr)rrr dest_rootr containeds rrvrv:s  **I W  bgll9f== > >FG&& 6':;;yH    )++ 3 3 3 3   JJvy!!! <<s%B BBtokenctj|dddS)uESHA-256 prefix used as a cache key — never logged, never displayed.rN)rrencoder)rs r_token_fingerprintrZs3 >%,,w// 0 0 : : < /cache/bws_cache.json`` (for back-to-back CLI invocations). Both share the same TTL. Pass ``home_path`` so disk cache lookups find the right directory in tests / non-standard installs; otherwise we fall back to ``$HERMES_HOME`` / ``~/.hermes``. Raises :class:`RuntimeError` for fatal conditions (missing binary, auth failure, unparseable output). Callers in the env_loader path catch this and emit a single warning; callers in the user-facing setup wizard let it propagate. zBitwarden access token is emptyzBitwarden project_id is emptyrNTr-ubws binary not available — auto-install failed and `bws` is not on PATH. Install manually from https://github.com/bitwarden/sdk-sm/releases or re-run `hermes secrets bitwarden setup`.)secrets fetched_at) r^rrgetis_freshrr rr@ _run_bws_list _CachedFetchtimewrite)rrrrrrr!rcached disk_cachedr1rwarningsentrys rfetch_bitwarden_secretsr_sb@ ><=== <:;;;#L11:z?ORPI +I&&  &foo&788 &>2% %!&&y2CYOO  "!,F9 &* *  5H555C { 0   &c<ZPPGX TY[[ A A AEF9J)U,=yIII H rr1ct|dd|ddg}tj}||d<|dd|r||d< t j||d d tt j }nP#t j $r}td td |d}~wt$r}td ||d}~wwxYw|j dkrX|j p|jpddd}td|j d|dd|j} | sidgfS t#j| } n*#t"j$r}td||d}~wwxYwt)| t*s$tdt-| ji} g} | D]} t)| t0s| d}| d}t)|trt)|tsmt5|s| d|d|| |<| | fS)Nsecretlistz--outputjsonBWS_ACCESS_TOKENNO_COLOR1BWS_SERVER_URLT)envrMrNrOrPzbws timed out after zs fetching secretszfailed to invoke bws: rrz bws exited rz'bws returned no output (empty project?)zbws returned non-JSON output: zbws returned unexpected shape: rvaluezSkipping secret z: not a valid env-var name)rr4environcopy setdefaultrWrX_BWS_RUN_TIMEOUTrYr]r^r\ returncoder[rZrrrloadsJSONDecodeError isinstancertype__name__dictr_is_valid_env_nameappend)r1rrrcmdrprocr?errrawpayloadrritemrrs rrrs s88Xvz:v FC *//  C*CNN:s### + * D~ $$      $ G#3 G G G    DDD9C99::CD !{/dk/R6688@@LL 8$/ 8 8S#Y 8 8    +    C ?=>>>L*S//  LLLACAABBKL gt $ $  Fd7mm.D F F   !GH  $%%  hhuoo!!#s## :eS+A+A  !#&&  OOD3DDD     H s<)BCB)) C6C  CE**F9F  Fr)access_token_envroverride_existingr auto_installrr!enabledrrrr ct}|s|Stj|d} | s d|d|_|S|s d|_|St |} | |_| d|_|S t| || |||\} } n-#t$r } t| |_|cYd} ~ Sd} ~ wwxYw| |_ |j | | D]\}}||kr|j|&|s:tj|r|j|b|tj|<|j||S) u8Pull secrets from BSM and set them on ``os.environ``. This is the function ``load_hermes_dotenv()`` calls after the .env files have loaded. It is intentionally defensive — any failure returns a :class:`FetchResult` with ``error`` set; it never raises. ``server_url`` selects the Bitwarden region or self-hosted endpoint (e.g. ``https://vault.bitwarden.eu`` for EU Cloud). Empty string means use ``bws``'s default (US Cloud). Parameters mirror the ``secrets.bitwarden.*`` config keys so the caller can just splat the dict in. r&secrets.bitwarden.enabled is true but 3 is not set. Run `hermes secrets bitwarden setup`.Msecrets.bitwarden.project_id is empty. Run `hermes secrets bitwarden setup`.r-Nhbws binary not available and auto-install is disabled. Run `hermes secrets bitwarden setup` to install.rrrrrr!)r r4rrrrr@ binary_pathrr^rrrextenditemsskippedr applied)rrrrrrrr!resultrrrrr?rrs rapply_bitwarden_secretsr s0]]F  :>>"2B77==??L  >5E > > >    4    6 6 6FF ~ ?    3%!/!     3xx  FN O8$$$mmoo # # U " " " N ! !# & & &   RZ^^C%8%8  N ! !# & & &  3c"""" MsB C%C:CCcBeZdZdZdZdZdZdZdd Zdd Z dd Z ddZ dS)BitwardenSourceuBitwarden Secrets Manager as a registered secret source. Thin adapter over the module's fetch machinery. ``fetch()`` only *fetches* — precedence, override semantics, conflict warnings, and the ``os.environ`` writes are the orchestrator's job (see ``agent.secret_sources.registry.apply_all``). Bitwarden is a **bulk** source: it injects every secret in the configured BSM project, so explicit per-var bindings from mapped sources (e.g. the 1Password ``env:`` map) outrank it. bitwardenzBitwarden Secrets Managerbulkr1cfgrrr/crtt|to|ddS)NrT)r/rrr)selfr%s rrz!BitwardenSource.override_existing[s0 JsD))Pcgg6I4.P.PQQQrcd}t|tr$t|dp|}t |hS)Nrr)rrrr frozenset)r'r% token_envs rprotected_env_varsz"BitwardenSource.protected_env_varsbsI& c4  FCGG$677D9EEI)%%%rc @ddddddddddd dd d dd d dd dddS)Nz Master switchF) descriptiondefaultz0Env var holding the machine-account access tokenrzBSM project UUIDrz!Disk+memory cache TTL; 0 disablesrz&BSM values overwrite .env/shell valuesTz#Auto-download the pinned bws binaryz0Region / self-hosted endpoint (empty = US Cloud))rrrrrrrr)r's r config_schemazBitwardenSource.config_schemahs'65IIQ-!!+=LLB"" H"" E R'   rr!rr c dt|tr|ni}t}t|dpd}t j|d}|sd|d|_tj |_ |St|dpd}|sd|_tj |_ |St|dd }t| }||_|d |_tj|_ |S t!|d d } n#t"t$f$rd} YnwxYw t'|||| t|ddpd|\} } nN#t($rA} t| |_t+t| |_ |cYd} ~ Sd} ~ wwxYw| |_|j| |S)NrrrrrrrrTr-rrrgr@rr)rrr rrr4rrrr NOT_CONFIGURED error_kindr/r@rBINARY_MISSINGr TypeErrorrrr^_classify_bws_errorrrr) r'r%r!rrrrrrttlrrr?s rfetchzBitwardenSource.fetchsYT**2ccsww'9::P>PQQz~~&6;;AACC  B9IBBB L!* 8F M..4"55  8 L!* 8F MCGGND99:: \:::# >C L!* 8F M  3S99::CC:&   CCC   7)%"%sww|R88>B??EEGG# !!! GXX   s88FL 3CHH = =F MMMMMM  !x((( s15#EE/.E/3A G H  6HH H N)r%rrr/)r%r)rr)r%rr!rrr ) r __module__ __qualname____doc__rlabelshapeschemerr+r/r7rrrr"r"Is   D 'E E FRRRR&&&&     4777777rr"messager c(|dvr tjSdvsdvr tjSt fddDr tjSt fddDr tjStjS)zABest-effort mapping of bws failure text onto the shared taxonomy.z timed outzbinary not availablezfailed to invokec3 K|]}|vV dSNrrtoklowereds r z&_classify_bws_error..s? E Ec3'> E E E E E Er) unauthorizedz invalid tokenz access token401403c3 K|]}|vV dSrArrBs rrEz&_classify_bws_error..s7 : :c3'> : : : : : :r)network connectionresolvedownloaddns)rUr TIMEOUTr3any AUTH_FAILEDNETWORKINTERNAL)r>rDs @rr5r5smmooGg  ((,>',I,I''  E E E E&D E E EEE%$$  : : : :&9 : : :::!   rcltt|dS)zClear in-process AND disk caches. Tests can pass ``home_path`` to scope the disk cleanup to a tmpdir. Without it we fall back to the same default resolution as the cache writer itself. N)rclearr r%s r_reset_cache_for_testsrVs+ LLNNNi     r)rrrrrA)r!r"rr)rr)r.r/rr")rr)rcr/rr)rrrrrr)rrrrrr)r$rrr)rrrrrr)rrrrrrrr)rrrr)rrrrrr"rrrr/rrr!r"rr)r) r1rrrrrrrrr)rr/rrrrrr/rrrr/rrr!r"rr )r>rrr )r!r"rr)Cr: __future__rrrloggingr4rCr7r{rWrmr urllib.errorrurllib.requestrspathlibrtypingrrrragent.secret_sources._cacher rr r r ragent.secret_sources.baser r getLoggerrr;rVrkrlrrrrr__annotations___DISK_CACHE_BASENAMErr r&r,r@r2rbr9rprqrrrurvrrrr r"r5rVrrrrbs:#"""""    ............ >=======  8 $ $ Q,PP@\??? #sC- (*****(3333 #  '''''%%%%,16BBBB((((V"'::::::zHHHH     "@BBBB"" $@@@@@@HFHEEEEE`/#" $RRRRRRtppppplpppf    *!!!!!!!r