`gjjUdZddlmZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl ZddlZddlZddlmZddlmZmZmZmZddlmZmZmZmZddlm Z m!Z!ejDe#Z$dZ%d e%Z&d e%d Z'd Z(d Z)ee*e*e*fZ+iZ,de-d<dZ.d1dZ/ee.e/Z0de-d<d2d3dZ1d4dZ2ddd5dZ3d6dZ4d6dZ5ddd7dZ6d8dZ7d9dZ8d:d Z9d;d!Z: dd(Z= d? d@d)Z>d*d&dd$d%d&dd+ dAd,Z?Gd-d.e!Z@dBd/ZAd2dCd0ZBy)DuBBitwarden 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 SecretSourcez2.0.0z;https://github.com/bitwarden/sdk-sm/releases/download/bws-vzbws-sha256-checksums-z.txt<zDict[_CacheKey, _CachedFetch]_CACHEzbws_cache.jsonc"|\}}}|d|d|S)z:Serialize a cache key to a stable string for JSON storage.|) cache_keytoken_fp project_id server_urls Q/root/.hermes/venv/lib/python3.12/site-packages/agent/secret_sources/bitwarden.py_cache_key_strr`s%'0$Hj*Zq Aj\ 22)key_serializerr _DISK_CACHEc,tj|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. )rpath home_paths 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(ys0  u $$rFinstall_if_missingcPttz }|jr&tj|tj r|St jd}|r t|S|r tSy#t$r }tjd|Yd}~yd}~wwxYw)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"99G~~BIIgrww7 \\% F F| =    NN8# > s1 A<< B%B  B%c8tjdk(rdSdS)NWindowszbws.exer,)platformr9rrrr-r-s )Y69AEArc tj}tjj}|dk(r dtdS|dk(r|dvrdnd}d|d tdS|d k(rp|dvrdnd}d } t j d d gdddt j}d|j|jzjvrd}d|d|dtdStd|d|#tt jf$rYr9machinelower _BWS_VERSION subprocessrunDEVNULLstdoutstderrOSErrorTimeoutExpired RuntimeError)r9rOarchlibcress r_platform_asset_namer]s4 __ F &&(G &l^488 #';;ydV,\N$?? #';;y .. $# (( C#**szz188::dV?4&,tDD  5fXQwiH  223   s0AC&&DD)forcec t}|jdd|tz }|jr|s|St }t d|}t dt }tjd5}t|}||z }|t z } tjd|t||t|| t| |} t|} | j| jk7rt!d|d| d | t#j$|5} t'| t} t)| | |}d d d tj*t-|d \}}t/j0|t3j4|t/j6|t8j:t8j<zt8j>zt8j@zt8jBzt8jDzt8jFzt/jH||d d d tjd tJ||S#1swYxYw#1swY3xYw)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_)dirrczInstalled bws %s at %s)&r(mkdirr-r.r]_BWS_RELEASE_BASE_BWS_CHECKSUM_NAMEtempfileTemporaryDirectoryrr6info_http_download_expected_sha256 _sha256_filerPrYzipfileZipFile_pick_zip_member_safe_extract_membermkstempstrr/closer2copy2chmodstatS_IRUSRS_IWUSRS_IXUSRS_IRGRPS_IXGRPS_IROTHS_IXOTHreplacerQ)r^bin_dirtarget asset_name asset_url checksum_urltmpdirtmpzip_path checksum_pathexpectedactualzfmember extractedfdstageds rr4r4sG MM$M. ,. .F }}u %'J$%Qzl3I'(*<)=>L  $ $M :$#f6l#00  $i0y(+|]3#M:>h' >> v||~ -( 5$:VF85  __X & >"%b*?*ABF -R=I  >%%#g,wG F   Y'   LL4<< '$,, 6ll !\\ *ll !\\ * 66"I$#L KK(,? M- > >#$#$#s&9B)I,""IC6I,I) $I,,I5ctjj|ddi} tjj|t5}t |d5}t j||ddddddy#1swYxYw#1swYyxYw#tjj$r}td|d||d}~wwxYw)Nz User-Agentz hermes-agent)headers)rJwbzFailed to download : ) urllibrequestRequesturlopen_BWS_DOWNLOAD_TIMEOUTopenr2 copyfileobjerrorURLErrorrY)urldestreqrespfr:s rrkrks .. |^.L MCH ^^ # #C1F # G ,4dD! ,Q""4+ , , , , , , , << H0Ru=>CGHsM%B B A?.B 6B?B B  BBBC 4CC c|jdd}|jD]>}|jj}t |dk\s0|d|k(s9|dcSt 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)encodingerrorsrGrzNo checksum entry for z in ) read_text splitlinesstripsplitlenrYname) checksum_filerrIlinepartss rrlrls  " "GI " FD! ""$ u:?uRyJ68O   D1C1C0DE rctj}t|d5tfddD]}|j | ddd|j S#1swY|j SxYw)Nrbc&jdS)Ni)read)rsrz_sha256_file..$s!&&-rr)hashlibsha256riterupdate hexdigest)rhchunkrs @rrmrm!siA dD Q/5 E HHUO  ;;= ;;=s &A!!A9c|jDcgc]}|jdd|k(s|}}|s#td|d|jddd|jt|d Scc}w) 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. rbrzCould not find z% inside downloaded archive (members: Nz...))keyr)namelistrrYsortr)r binary_namen candidatess rrprp)s  [[]Naggcl2.>+.M!NJN k]+r*+4 1  OOO a=Os A6A6ctjj|}tjjtjj||} tjj ||g|k(}|r||k(rt d|d|j||t|S#t $rd}Y@wxYw)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/rrealpathjoin commonpath ValueErrorrYextractr)rrdest_dir dest_rootr containeds rrqrq:s  *I WW  bggll9f= >FGG&& 6':;yH  )+8 C2 3  JJvy! <  s$B55 CCcltj|jdjddS)uESHA-256 prefix used as a cache key — never logged, never displayed.rN)rrencoder)tokens r_token_fingerprintrZs* >>%,,w/ 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 emptyrTr)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) rYrrgetis_freshrrrr; _run_bws_list _CachedFetchtimewrite) access_tokenrrrrrr!rcached disk_cachedr,rwarningsentrys rfetch_bitwarden_secretsr_s@ <== :;;#L1:z?ORPII& foo&78>>2% %!&&y2CYO  "!,F9 &&* *  5H5C { 0  &c<ZPGX TYY[ AEF9)U,=yI H rct|dd|ddg}tjj}||d<|j dd|r||d< t j ||d d tt j }|jdk7rZ|jxs|jxsdjj!dd}td|jd|dd|jj} | sidgfS t#j$| } t)| t*s!tdt-| j.i} g} | D]|} t)| t0s| j3d}| j3d}t)|trt)|tsWt5|s| j7d|dx|| |<~| | fS#t j$r}td td |d}~wt$r}td ||d}~wwxYw#t"j&$r}td||d}~wwxYw)Nsecretlistz--outputjsonBWS_ACCESS_TOKENNO_COLOR1BWS_SERVER_URLT)envrHrIrJrKzbws 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)rsr/environcopy setdefaultrRrS_BWS_RUN_TIMEOUTrTrXrYrW returncoderVrUrrrloadsJSONDecodeError isinstancertype__name__dictr_is_valid_env_nameappend)r,rrrcmdrprocr:errrawpayloadrritemrrs rrrsh s8Xvz:v FC **// C*CNN:s#  * D~~ $$$   !{{/dkk/R668@@L$//*"S#YK 8   ++   C =>>>L**S/ gt $-d7m.D.D-E F  !GH $% hhuo!#s#:eS+A !#& OO"3')CD     H Y  $ $"#3"44F G   D3C59:CD"   L;C5ABKLs<-GH H)G== H HH I3IIr)access_token_envroverride_existingr auto_installrr!ct}|s|Stjj|dj } | s d|d|_|S|s d|_|St |} | |_| d|_|S t| || |||\} } | |_ |jj| | jD]\}}||k(r|jj!|'|s;tjj|r|jj!|d|tj|<|j"j!||S#t$r} t| |_|cYd} ~ Sd} ~ wwxYw) 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 r/rrrrr; binary_pathrrYrsrrextenditemsskippedrapplied)enabledrrrrrrr!resultrrrrr:rrs rapply_bitwarden_secretsrs0]F  ::>>"2B7==?L 45E4FG> >    4    6FF ~ ?    3%!/!  FN OO8$mmo # U " " NN ! !# &  RZZ^^C%8 NN ! !# &  3c" # M) 3x  s6E E7E2,E72E7c@eZdZdZdZdZdZdZd dZd dZ d dZ dd Z y )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 Managerbulkr,c\tt|txr|jddS)NrT)boolrrr)selfcfgs rrz!BitwardenSource.override_existing[s' JsD)Pcgg6I4.PQQrczd}t|trt|jdxs|}t |hS)Nrr)rrrsr frozenset)rr token_envs rprotected_env_varsz"BitwardenSource.protected_env_varsbs7& c4 CGG$67D9EI)%%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)rs r config_schemazBitwardenSource.config_schemahs^'65IQ-!+=LB" H" E R'  rc t|tr|ni}t}t|j dxsd}t j j |dj}|s"d|d|_tj|_ |St|j dxsd}|sd|_tj|_ |St|j dd }t| }||_|d |_tj|_ |S t!|j d d } t'|||| t|j ddxsdj|\} } | |_|j.j1| |S#t"t$f$rd} YwwxYw#t($r5} t| |_t+t| |_ |cYd} ~ Sd} ~ wwxYw)Nrrrr r rr rTr)r rrgr@rr )rrr rsrr/rrrr NOT_CONFIGURED error_kindrr;rBINARY_MISSINGfloat TypeErrorrrrY_classify_bws_errorrrr) rrr!rrrrrrttlrrr:s rfetchzBitwardenSource.fetchsT*csww'9:P>PQzz~~&6;AAC 89I8JKBB L!* 8 8F M.4"5 8 L!* 8 8F MCGGND9: \:# >C L!* 8 8F M  3S9:C  7)%"%sww|R8>B?EEG# ! GX!x( ':& C  s8FL 3CH =F M s0F8?F2F/.F/2 G0;*G+%G0+G0N)rrreturnr)rr)r/r)rrr!rr/r ) r __module__ __qualname____doc__rlabelshapeschemerr!r%r.rrrrrIs2  D 'E E FR&  47rrc,|jdvrtjSdvsdvrtjSt fddDrtj St fddDrtj StjS)zABest-effort mapping of bws failure text onto the shared taxonomy.z timed outzbinary not availablezfailed to invokec3&K|]}|v ywNr.0toklowereds r z&_classify_bws_error..s Ec3'> E) unauthorizedz invalid tokenz access token401403c3&K|]}|v ywr8rr9s rr=z&_classify_bws_error..s :c3'> :r>)network connectionresolvedownloaddns)rPr TIMEOUTr)any AUTH_FAILEDNETWORKINTERNAL)messager<s @rr,r,smmoGg   (,>',I'''  E&D EE$$$  :&9 ::     rcVtjtj|y)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)rclearrr s r_reset_cache_for_testsrPs LLNi r)r _CacheKeyr/rsr8)r!Optional[Path]r/r)r/r)r*rr/rR)r/rs)r^rr/r)rrsrrr/None)rrrrsr/rs)rrr/rs)rzipfile.ZipFilerrsr/rs)rrTrrsrrr/r)rrsr/rs)rrsrrsrrRrr*rrrrsr!rRr/ Tuple[Dict[str, str], List[str]])r) r,rrrsrrsrrsr/rU)rrrrsrrsrrrr*rrrrsr!rRr/r )rMrsr/r )r!rRr/rS)Cr2 __future__rrrloggingr/r>r2rwrRrhr urllib.errorrurllib.requestrnpathlibrtypingrrrragent.secret_sources._cacher rr r r ragent.secret_sources.baser r getLoggerrr6rQrfrgrrrsrQr__annotations___DISK_CACHE_BASENAMErrr"r(r;r-r]r4rkrlrmrprqrrrrrr,rPrrrras:#    .. >   8 $ B,P-\N$? #sC- (*%*(3 # Y '%,16B(V"':zH  "!$04 @B"" $@@@  @  @  @@@&@HFHE E E.1E?BE%E`/#" $R RR R  R  RRRRRtplpf *!r