sj UdZddlmZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl Z ddlZddlZddlZddlZddlmZddlmZmZmZmZddlmZmZmZmZ ddl!m"Z"m#Z#ddl!m$Z$ej%e&Z'd Z(d e(Z)d e(d Z*d Z+dZ,ee-e-e-fZ.iZ/de0d<dZ1dZ2dZ3dZ4dndZ5ee1e5Z6de0d<dodpd Z7dodpd!Z8dqd"Z9d#d$drd'Z:dsd(Z;dsd)Zdvd3Z?dwd5Z@dxd9ZAdyd<ZBdzd>ZCd{dAZDd|dCZEd}dFZFddGd~dJZGddGddNZHddOdPdQdd#ddRdd[ZIdd\ZJ ddd^ZKd_dQd#dOdPdQdd#dd` ddfZLGdgdhe#ZMddkZNdoddlZOdoddmZPdS)uBBitwarden Secrets Manager (`bws` CLI) integration. Hermes pulls API keys from Bitwarden Secrets Manager at process startup so they don't have to live in plaintext in ``~/.hermes/.env``. Design summary -------------- * The ``bws`` binary is auto-installed into ``/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 SecretSource)get_source_environmentz2.0.0z;https://github.com/bitwarden/sdk-sm/releases/download/bws-vzbws-sha256-checksums-z.txt<zDict[_CacheKey, _CachedFetch]_CACHEzbws_cache.jsonzbws_cache.enc.jsonshermes-bws-encrypted-cache-v1 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/agent/.hermes/hermes-agent/agent/secret_sources/bitwarden.py_cache_key_strrfs*'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(qs   I & &&r c:ddlm}||dz tz S)z>Return the encrypted disk cache path under hermes_home/cache/.r)resolve_cache_homecache)agent.secret_sources._cacher*_ENCRYPTED_CACHE_BASENAME)r#r*s r_encrypted_disk_cache_pathr.zs0>>>>>>  i ( (7 25N NNr c(ddlm}|dz S)z9Where Hermes stores its managed binaries. Profile-aware.rget_hermes_homebin)hermes_constantsr1r0s r_hermes_bin_dirr4s'000000 ?  u $$r Finstall_if_missingr6boolc|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) r4_platform_binary_nameexistsosaccessX_OKshutilwhichr install_bws Exceptionloggerwarning)r6managedsystemexcs rfind_bwsrHs"7"9"99G~~BIgrw77 \% F F|| ==     NN8# > > >44444  4s; B B9B44B9c8tjdkrdndS)NWindowszbws.exer9)platformrFrr rr:r:s ))Y6699EAr c  tj}tj}|dkr dtdS|dkr|dvrdnd}d|d tdS|d kr|dvrdnd}d } t jd d gdddddt 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.ziprJ)arm64aarch64rOx86_64zbws-z-pc-windows-msvc-Linuxgnulddz --versionTutf-8replace)capture_outputtextencodingerrorstimeoutstdinmuslz-unknown-linux--z+Unsupported platform for bws auto-install:  ) rKrFmachinelower _BWS_VERSION subprocessrunDEVNULLstdoutstderrOSErrorTimeoutExpired RuntimeError)rFr`archlibcress r_platform_asset_namernsq _  F  &&((G 9l8888 #';;;yy?d??\???? #';;;yy . $#GI ( C#*sz188::::23    D DdDD4DD,DDDD HfHHwHH  s7A CCC)forceroc \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. Tparentsexist_ok/z hermes-bws-)prefixzDownloading %szChecksum mismatch for z : expected z, got Nz.bws_)dirruzInstalled bws %s at %s)&r4mkdirr:r;rn_BWS_RELEASE_BASE_BWS_CHECKSUM_NAMEtempfileTemporaryDirectoryrrCinfo_http_download_expected_sha256 _sha256_filerarjzipfileZipFile_pick_zip_member_safe_extract_membermkstemprr<closer?copy2chmodstatS_IRUSRS_IWUSRS_IXUSRS_IRGRPS_IXGRPS_IROTHS_IXOTHrUrb)robin_dirtarget asset_name asset_url checksum_urltmpdirtmpzip_path checksum_pathexpectedactualzfmember extractedfdstageds rrArAsG 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)r[wbzFailed to download : ) urllibrequestRequesturlopen_BWS_DOWNLOAD_TIMEOUTopenr? copyfileobjerrorURLErrorrj)rrreqrespfrGs rr}r}sd . |^.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. rTrU)rYrZrVrzNo checksum entry for z in ) read_text splitlinesstripsplitlenrjname)rrrXlinepartss rr~r~s  " "GI " F FD!! ""$$ u::??uRyJ668OOO EEE1CEE  r r&ctj}t|d5tfddD]}|| dddn #1swxYwY|S)Nrbc.dS)Ni)read)rsrz_sha256_file..1s!&&--r r )hashlibsha256riterupdate hexdigest)r&hchunkrs @rrr.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)rtr)r).0nrs r z$_pick_zip_member..<s2NNNaggcll2.>+.M.M!.M.M.Mr zCould not find z% inside downloaded archive (members: Nz...))keyr)namelistrjsortr)rr candidatess ` rrr6s ONNNR[[]]NNNJ   1k 1 1rr* 1 1 1   OOO a=r rdest_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) r<r&realpathjoin commonpath ValueErrorrjextractr)rrr dest_rootr containeds rrrGs  **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.rTN)rrencoder)rs r_token_fingerprintrgs3 >%,,w// 0 0 : : < z._read_encrypted_disk_cache..sP   Q!S!! &0C&8&8 q   r r)r.rrrloadsrr'dictrgetrrrrdecryptrrintr"timeitemsrrB)rrr!r#r&rrrrr r rrinnerrinner_fetched_at entry_agetypeds r_read_encrypted_disk_cacher6sx!t %i 0 0D"FFFFFF*T^^W^==>>'4(( 4' 22 ;;y ! !%= = =4 ;;u   / /4SVR001122c'++gr2233443w{{<<<==>> ),==fSkk!! :~44W==   3::g..//%&& 4))I&& 99\22'4((  ;KcSX\0Z0Z 4IKK%(8"9"99 q==I774  $]]__   Ee<=== <:;;;#L11:z?ORPI+&**I&&  &foo&788 &>2% % " T4#) 1# KK&**96GSSK  "!,F9 &* *  5H555C { 0   0)#|ZTT ...*#3s88,,  )"3Y5F!GGG& 2'!-$E'  $c49;;1A#ABBC(-F9% =H#HH7:3xxHHH+%#Q&&#((E%LL)LL$c49;;1A#ABBC(-F9% =N#NN=@XXNNN+ ].^ TY[[ A A AEN q %F9  " N (#)#        " "   i0A9 M M M H s2$C;; H:B H5&H:,BH5.H:4H55H:cx|dd}|s|Sg}|D]_}|}|drn3|dvr2t jdd|}|r||`|rd|n|S)aReduce a bws (Rust color-eyre) error dump to its cause line(s). bws failures look like:: Error: 0: Received error message from server: [400 Bad Request] {"error":"invalid_client"} Location: crates/bws/src/main.rs:108 ... Everything from ``Location:`` on is diagnostic noise for a Hermes user. Keep the numbered cause lines (joined), drop the rest, and fall back to the stripped raw text when the shape is unrecognized. r%)z Location:zBacktrace omittedz Run with )r%zError:z^\d+:\s*z; )rUrr startswithresubappendr)rrXcausesrstrippeds r_summarize_bws_stderrrWs ;;vr " " ( ( * *D  F!! $ $::<<   N O O  E ~ % % 6+r844  $ MM( # # # & 0499V   D0r r9c t|dd|ddg}t}|tjurddlm}|dd}nt |}||d <|d d |r||d < tj ||d d ddttj }nP#tj $r} tdtd| d} ~ wt$r} td| | d} ~ wwxYw|jdkr?t!|jp|jpd} td|jd| dd|j} | sidgfS t)j| } n*#t(j$r} td| | d} ~ wwxYwt/| t0s$tdt3| ji} g}| D]}t/|t s|d}|d}t/|trt/|tsmt9|s|d|d|| |<| |fS)Nsecretlistz--outputrr)build_subprocess_envF) scrub_secretsinherit_profile_homeBWS_ACCESS_TOKENNO_COLOR1BWS_SERVER_URLTrTrU)envrWrXrYrZr[r\zbws timed out after zs fetching secretszfailed to invoke bws: r%z 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)rrr<environtools.environments.localr[r, setdefaultrcrd_BWS_RUN_TIMEOUTrerirjrh returncoderWrgrfrrr+JSONDecodeErrorr'rZtype__name__r-_is_valid_env_namerT)r9rrrcmd source_envr[rbprocrGerrrrrrJitemrrds rrBrBs. s88Xvz:v FC())JRZAAAAAA""USSS:*CNN:s### + * D~  $$      $ G#3 G G G    DDD9C99::CD ! $DK$D4;$D"EE 8$/ 8 8S#Y 8 8    +    C ?=>>>L*S//  LLLACAABBKL gt $ $  Fd7mm.D F F   !GH  $%%  hhuoo!!#s## :eS+A+A  !#&&  OOD3DDD     H s<8+B$$C13C  C1C,,C1E44FFFr^) access_token_envroverride_existingr9 auto_installrr#r;r<enabledrsrtrur c t} |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`.r5Nhbws binary not available and auto-install is disabled. Run `hermes secrets bitwarden setup` to install.rrr8r9rr#r;r<)r r<rer-rrrH binary_pathrNrjrrrJextendr1skippedrTapplied)rvrsrrtr9rurr#r;r<resultrr8rrJrGrrds rapply_bitwarden_secretsrs4]]F  :>>"2B77==??L  >5E > > >    4    6 6 6FF ~ ?    3%!/!$;.O     3xx  FN O8$$$mmoo # # U " " " N ! !# & & &   RZ^^C%8%8  N ! !# & & &  3c"""" MsB C'C<CCcTeZdZdZdZdZdZdZdd Zdd Z dd Z ddZ dfd Z xZ S)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 Managerbulkr9cfgr,rr7crtt|to|ddS)NrtT)r7r'r,r-)selfrs rrtz!BitwardenSource.override_existingis0 JsD))Pcgg6I4.P.PQQQr cd}t|tr$t|dp|}t |hS)Nr^rs)r'r,rr- frozenset)rr token_envs rprotected_env_varsz"BitwardenSource.protected_env_varspsI& c4  FCGG$677D9EEI)%%%r c Nddddddddddd dd dd d dd dddddddddS)Nz Master switchF) descriptiondefaultz0Env var holding the machine-account access tokenr^zBSM project UUIDr%z9Fresh disk+memory cache TTL; 0 disables fresh-cache reuser7z6Encrypted last-good cache for network/timeout fallbackr)rvmax_stale_secondsz&BSM values overwrite .env/shell valuesTz#Auto-download the pinned bws binaryz0Region / self-hosted endpoint (empty = US Cloud))rvrsrr9encrypted_cachertrurr)rs r config_schemazBitwardenSource.config_schemavs'65IIQ-!!+=LLZ"" X$)*   H"" E R5   r r#rr c t|tr|ni}t}t|dpd}t |d}|sd|d|_tj |_ |St|dpd}|sd|_tj |_ |St|dd }t| }||_ |d |_tj|_ |S t|d d } n#t t"f$rd} YnwxYw|d} t| tr| ni} t| dd} t| dd} n#t t"f$rd} YnwxYw t%|||| t|ddpd|| | \} }nv#t&$ri}t||_t)t||_ |j tjkrd|d|jd|_|cYd}~Sd}~wwxYw| |_|j||S)Nrsr^r%rxryrrzruTr5r{r9r7gr@rrvFrrr?rr|z5Bitwarden rejected the machine-account access token (uF) — it was likely revoked, expired, or belongs to another region. ())r'r,r rr-rrrr NOT_CONFIGURED error_kindr7rHr}BINARY_MISSINGr" TypeErrorrrNrjrC AUTH_FAILEDrrJr~)rrr#rrsrrrur8ttl encrypted_cfgencrypted_enabledencrypted_max_stalerrJrGs rfetchzBitwardenSource.fetchsHT**2ccsww'9::P>PQQ-//334DbIIOOQQ  B9IBBB L!* 8F M..4"55  8 L!* 8F MCGGND99:: \:::# >C L!* 8F M  3S99::CC:&   CCC  122 )3M4)H)HP b  !2!29e!D!DEE &"' (9(9:Mq(Q(Q"R"R  :& & & &"%    &  7)%"%sww|R88>B??EEGG#(92E ! ! ! GXX   s88FL 3CHH = =F  I$999G(GG7=|GGG MMMMMM !x((( sD7#EE10E1#G**H?HAI KAK<KKrc|tjtjfvr dSt||S)NuRun `hermes secrets bitwarden token` to paste a fresh access token (create one in the Bitwarden web app: Secrets Manager → Machine accounts → Access tokens). Wrong region? Re-run `hermes secrets bitwarden setup` and pick EU/self-hosted.)r r AUTH_EXPIREDsuper remediation)rrKr __class__s rrzBitwardenSource.remediationsE I)9+AB B BL   ww""4---r )rr,rr7)rr,)rr,)rr,r#rrr )rr,rr)rl __module__ __qualname____doc__rlabelshapeschemertrrrr __classcell__)rs@rrrWs   D 'E E FRRRR&&&&     BIIIIV..........r rmessager 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..s7 : :c3'> : : : : : :r ) unauthorizedz invalid tokenz access token401403invalid_client invalid_grantz400 bad requestc3 K|]}|vV dSrrrs rrz&_classify_bws_error..s7 : :c3'> : : : : : :r )network connectionresolvedownloaddns)rar rEranyrrDINTERNAL)rrs @rrCrCsmmooGg  ((,>',I,I''  : : : :&9 : : :::%$$  : : : :&9 : : :::!   r ctt| t|dS#t t f$rYdSwxYw)aYDrop in-process AND disk caches (plaintext and encrypted). Used after a token rotation (`hermes secrets bitwarden token`) so the next startup fetches fresh with the new credential instead of serving a pull cached under the old token's fingerprint. The encrypted cache is keyed off the old token too, so it must go as well. N)rclearr"r.rrrhr's r clear_cachesrsq LLNNNi    "9--4466666 w '     s!AA-,A-c$t|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)rr's r_reset_cache_for_testsrsr )rrrrr)r#r$rr)rr)r6r7rr$)rr)ror7rr)rrrrrr)rrrrrr)r&rrr)rrrrrr)rrrrrrrr)rrrr)rrrr)rXrrr)rrrrrr) rrrrrrr#r$rr) rrrrr!r"r#r$rr#)rrrrr8r$r9r"r:r7rrr#r$r;r7r<r"rr=)rrrr)r%) r9rrrrrrrrr=)rvr7rsrrrrtr7r9r"rur7rrr#r$r;r7r<r"rr )rrrr )r#r$rr)Qr __future__rrrrloggingr<rKrRr?rrcrzr0 urllib.errorrurllib.requestrpathlibrtypingrrrrr,r rr r r rmagent.secret_sources.baser rr getLoggerrlrCrbrxryrrhrrr__annotations___DISK_CACHE_BASENAMEr-rrrr"r(r.r4rHr:rnrAr}r~rrrrrrrr r6rNrWrBrrrCrrrr rrs*:#"""""     ............ >=======<<<<<<  8 $ $ Q,PP@\??? #sC- (*****(083333 #  '''''OOOOO%%%%,16BBBB((((V"'::::::zHHHH     "@BBBB 1111AAAA++++,!% ??????N!% ------h"" $$)/0GGGGGGT1111DFHOOOOOt/#" $$)/0VVVVVV|S.S.S.S.S.lS.S.S.l6      r