hdZddlmZddlZddlZej eZddlZddl Z ddl m Z ddl m Z ddlmZmZmZddlmZmZddlmZmZmZmZmZmZmZmZdd lm Z dd l!m"Z"m#Z#m$Z$m%Z%m&Z&m'Z'm(Z(m)Z)m*Z*m+Z+m,Z,dd l-m.Z.m/Z/gd Z0e1Z2d Z3e4dgZ5e6e7e7e7e3e7Z8dZ9e:ddZ;e4ddgZGdde1Z?Gdde1Z@Gdde@ZAy)z-passlib.context - CryptContext implementation)with_statementN)warn)exc)ExpectedStringErrorExpectedTypeErrorPasslibConfigWarning)get_crypt_handler_validate_handler_name)handlersto_bytes to_unicode splitcommaas_booltimerrng getrandstr) BASE64_CHARS) iteritems num_typesirangePY2PY3unicodeSafeConfigParserNativeStringIOBytesIOunicode_or_bytes_typesnative_string_types)deprecated_methodmemoized_property) CryptContextLazyCryptContext CryptPolicyc|jdrt|jddzS t|S#t$rt|cYSwxYw)z>parse vary_rounds string to percent as [0,1) float, or integer%{Gz?)endswithfloatrstripint ValueErrorvalues Q/var/www/html/Resume-Scraper/venv/lib/python3.12/site-packages/passlib/context.py_coerce_vary_roundsr/*sO ~~cU\\#&'++5z U|s ;AAsalt) min_rounds max_roundsdefault_rounds vary_rounds salt_sizec2t|jd|uS)z3detect if handler is registered or a custom handlerN)r namehandlers r._is_handler_registeredr:Cs W\\4 0G ;;cy)z dummy function patched into handler.needs_update() by _CryptConfig when hash alg has been deprecated for context. T)hashsecrets r._always_needs_updater@Gs r;truncate_errorr4zaThe CryptPolicy class has been deprecated as of Passlib 1.6, and will be removed in Passlib 1.8. ceZdZdZeddZeddZeddZeddZdZ dZ dZ d Z d Z d Zdd Zdd ZddZddZddZddZddZddZddZy)r#a .. deprecated:: 1.6 This class has been deprecated, and will be removed in Passlib 1.8. All of its functionality has been rolled into :class:`CryptContext`. This class previously stored the configuration options for the CryptContext class. In the interest of interface simplification, all of this class' functionality has been rolled into the CryptContext class itself. The documentation for this class is now focused on documenting how to migrate to the new api. Additionally, where possible, the deprecation warnings issued by the CryptPolicy methods will list the replacement call that should be used. Constructors ============ CryptPolicy objects can be constructed directly using any of the keywords accepted by :class:`CryptContext`. Direct uses of the :class:`!CryptPolicy` constructor should either pass the keywords directly into the CryptContext constructor, or to :meth:`CryptContext.update` if the policy object was being used to update an existing context object. In addition to passing in keywords directly, CryptPolicy objects can be constructed by the following methods: .. automethod:: from_path .. automethod:: from_string .. automethod:: from_source .. automethod:: from_sources .. automethod:: replace Introspection ============= All of the informational methods provided by this class have been deprecated by identical or similar methods in the :class:`CryptContext` class: .. automethod:: has_schemes .. automethod:: schemes .. automethod:: iter_handlers .. automethod:: get_handler .. automethod:: get_options .. automethod:: handler_is_deprecated .. automethod:: get_min_verify_time Exporting ========= .. automethod:: iter_config .. automethod:: to_dict .. automethod:: to_file .. automethod:: to_string .. note:: CryptPolicy are immutable. Use the :meth:`replace` method to mutate existing instances. .. deprecated:: 1.6 cpttdztd|tj |||S)aWcreate a CryptPolicy instance from a local file. .. deprecated:: 1.6 Creating a new CryptContext from a file, which was previously done via ``CryptContext(policy=CryptPolicy.from_path(path))``, can now be done via ``CryptContext.from_path(path)``. See :meth:`CryptContext.from_path` for details. Updating an existing CryptContext from a file, which was previously done ``context.policy = CryptPolicy.from_path(path)``, can now be done via ``context.load_path(path)``. See :meth:`CryptContext.load_path` for details. zInstead of ``CryptPolicy.from_path(path)``, use ``CryptContext.from_path(path)`` or ``context.load_path(path)`` for an existing CryptContext. stacklevel_internal_context)r _preambleDeprecationWarningr! from_path)clspathsectionencodings r.rKzCryptPolicy.from_pathsG YMM A  / \%;%;D'F&HI Ir;c|rttdztdttrStt r|t d iStttfstdttfddDsjds|t jS|t jS) acreate a CryptPolicy instance from some source. this method autodetects the source type, and invokes the appropriate constructor automatically. it attempts to detect whether the source is a configuration string, a filepath, a dictionary, or an existing CryptPolicy instance. .. deprecated:: 1.6 Create a new CryptContext, which could previously be done via ``CryptContext(policy=CryptPolicy.from_source(source))``, should now be done using an explicit method: the :class:`CryptContext` constructor itself, :meth:`CryptContext.from_path`, or :meth:`CryptContext.from_string`. Updating an existing CryptContext, which could previously be done via ``context.policy = CryptPolicy.from_source(source)``, should now be done using an explicit method: :meth:`CryptContext.update`, or :meth:`CryptContext.load`. zInstead of ``CryptPolicy.from_source()``, use ``CryptContext.from_string(path)`` or ``CryptContext.from_path(source)``, as appropriate.rDrErGz?source must be CryptPolicy, dict, config string, or file path: c3&K|]}|v ywNr=).0crRs r. z*CryptPolicy.from_source..s/f/sz z ./;:r=)rrIrJ isinstancer#dictr!bytesr TypeErrortypeanystriprQrK)rLrR_warns ` r. from_sourcezCryptPolicy.from_sources,  KK$  3 fk *M  %)?)?@ @FU7O426v,AB B /h/ /v||I7N)A)A&)IJ J)?)?)GH Hr;c`|rttdztdt|dk(r t dt|dk(r|j |ddSi}|D]>}|j |j |djjd @|td i| S) acreate a CryptPolicy instance by merging multiple sources. each source is interpreted as by :meth:`from_source`, and the results are merged together. .. deprecated:: 1.6 Instead of using this method to merge multiple policies together, a :class:`CryptContext` instance should be created, and then the multiple sources merged together via :meth:`CryptContext.load`. zwInstead of ``CryptPolicy.from_sources()``, use the various CryptContext constructors followed by ``context.update()``.rDrErzno sources specifiedFr`TresolverGr=) rrIrJlenr+raupdate_contextto_dictr!)rLsourcesr`kwdsrRs r. from_sourceszCryptPolicy.from_sourcess  66$  3 w<1 34 4 w<1 ??71:U?; ; ]F KKe<EEMMVZM[ \ ]\%9D%9::r;c|jrttdztdnttdztd|g}|r|j ||r|j |t j|dS)zcreate a new CryptPolicy, optionally updating parts of the existing configuration. .. deprecated:: 1.6 Callers of this method should :meth:`CryptContext.update` or :meth:`CryptContext.copy` instead. zXInstead of ``context.policy.replace()``, use ``context.update()`` or ``context.copy()``.rDrEzzInstead of ``CryptPolicy().replace()``, create a CryptContext instance and use ``context.update()`` or ``context.copy()``.Frd) _stub_policyrrIrJextendappendr#rm)selfargsrlrks r.replacezCryptPolicy.replaces    CC$ 3 CC$  3 (  NN4  NN4 ''u'==r;NFc\|jdd}|rBt|tsJ||_|jdd|_|s|r Jd|d|y|r+t |dk7r t d|r t d|d }ttd ztd td i||_y)NrHroFzunexpected args:  rcz%only one positional argument acceptedz&cannot specify positional arg and kwdsrzInstead of constructing a CryptPolicy instance, create a CryptContext directly, or use ``context.update()`` and ``context.load()`` to reconfigure existing CryptContext instances.rDrEr=) poprYr!rirorgr\rrIrJ)rrrsrlcontexts r.__init__zCryptPolicy.__init__1s((.5 g|4 4#DM $ ?D  M4'M Mt9>#$KLL#$LMMAw  $  3 )040DMr;c|jrttdztdnttdztdt |j j S)zreturn True if policy defines *any* schemes for use. .. deprecated:: 1.6 applications should use ``bool(context.schemes())`` instead. see :meth:`CryptContext.schemes`. zMInstead of ``context.policy.has_schemes()``, use ``bool(context.schemes())``.rDrEzoInstead of ``CryptPolicy().has_schemes()``, create a CryptContext instance and use ``bool(context.schemes())``.)rorrIrJboolrischemesrrs r. has_schemeszCryptPolicy.has_schemesJs_    44$ 3 44$  3 DMM))+,,r;c|jrttdztdnttdztd|jj ddS)zreturn iterator over handlers defined in policy. .. deprecated:: 1.6 applications should use ``context.schemes(resolve=True))`` instead. see :meth:`CryptContext.schemes`. zUInstead of ``context.policy.iter_handlers()``, use ``context.schemes(resolve=True)``.rDrEzwInstead of ``CryptPolicy().iter_handlers()``, create a CryptContext instance and use ``context.schemes(resolve=True)``.Trf unconfigured)rorrIrJrir|r}s r. iter_handlerszCryptPolicy.iter_handlers^sa    ::$ 3 ::$  3 }}$$T$EEr;c|jrttdztdnttdztdt |j j |dS)zreturn list of schemes defined in policy. .. deprecated:: 1.6 applications should use :meth:`CryptContext.schemes` instead. zCInstead of ``context.policy.schemes()``, use ``context.schemes()``.rDrEzeInstead of ``CryptPolicy().schemes()``, create a CryptContext instance and use ``context.schemes()``.Tr)rorrIrJlistrir|rrrfs r.r|zCryptPolicy.schemesrsf    ..$ 3 ..$  3 DMM))')MNNr;c|jrttdztdnttdztd |jj ||dS#t $r|rYywxYw)a8return handler as specified by name, or default handler. .. deprecated:: 1.6 applications should use :meth:`CryptContext.handler` instead, though note that the ``required`` keyword has been removed, and the new method will always act as if ``required=True``. zGInstead of ``context.policy.get_handler()``, use ``context.handler()``.rDrEziInstead of ``CryptPolicy().get_handler()``, create a CryptContext instance and use ``context.handler()``.TrN)rorrIrJrir9KeyError)rrr7categoryrequireds r. get_handlerzCryptPolicy.get_handlers~    ..$ 3 ..$  3 ==((xd(K K   sA A.-A.c(tdtdy)arget min_verify_time setting for policy. .. deprecated:: 1.6 min_verify_time option will be removed entirely in passlib 1.8 .. versionchanged:: 1.7 this method now always returns the value automatically calculated by :meth:`CryptContext.min_verify_time`, any value specified by policy is ignored. znget_min_verify_time() and min_verify_time option is deprecated and ignored, and will be removed in Passlib 1.8rDrEr)rrJ)rrrs r.get_min_verify_timezCryptPolicy.get_min_verify_times 23E r;c|jrttdztdnttdztdt |dr |j }|j jj||dS)aLreturn dictionary of options specific to a given handler. .. deprecated:: 1.6 this method has no direct replacement in the 1.6 api, as there is not a clearly defined use-case. however, examining the output of :meth:`CryptContext.to_dict` should serve as the closest alternative. z=``context.policy.get_options()`` will no longer be available.rDrEz<``CryptPolicy().get_options()`` will no longer be available.r7r) rorrIrJhasattrr7ri_config_get_record_options_with_flagrrr7rs r. get_optionszCryptPolicy.get_optionssw    PQ# 3 OP# 3 4 99D}}$$BB4RSTUUr;c|jrttdztdnttdztdt |dr |j }|j j||jS)aBcheck if handler has been deprecated by policy. .. deprecated:: 1.6 this method has no direct replacement in the 1.6 api, as there is not a clearly defined use-case. however, examining the output of :meth:`CryptContext.to_dict` should serve as the closest alternative. zG``context.policy.handler_is_deprecated()`` will no longer be available.rDrEzF``CryptPolicy().handler_is_deprecated()`` will no longer be available.r7) rorrIrJrr7rir9 deprecatedrs r.handler_is_deprecatedz!CryptPolicy.handler_is_deprecatedsq    Z[# 3 YZ# 3 4 99D}}$$T84???r;c |jrttdztdnttdztd|j|r fddd}nj dfd j j|DS) ziterate over key/value pairs representing the policy object. .. deprecated:: 1.6 applications should use :meth:`CryptContext.to_dict` instead. zOInstead of ``context.policy.iter_config()``, use ``context.to_dict().items()``.rDrEzqInstead of ``CryptPolicy().iter_config()``, create a CryptContext instance and use ``context.to_dict().items()``.cFj|jddS)N__.)_render_config_keyrt)keyrxs r. render_keyz+CryptPolicy.iter_config..render_keys!11#6>>tSIIr;cTt|ttfrdj|}|S)N, )rYrtuplejoinr,s r. render_valuez-CryptPolicy.iter_config..render_values#ed5\2 IIe,E r;Fc|SrUr=r,s r.z)CryptPolicy.iter_config..sr;c3DK|]\}}||fywrUr=)rVrr-rrs r.rXz*CryptPolicy.iter_config..s+ U_l51 2 s )rorrIrJrirr iter_config)rrinirfrxrrs @@@r.rzCryptPolicy.iter_configs    66$ 3 66$  3--  J G 33J.L %oo99'B  r;c|jrttdztdnttdztd|jj |S)zexport policy object as dictionary of options. .. deprecated:: 1.6 applications should use :meth:`CryptContext.to_dict` instead. zCInstead of ``context.policy.to_dict()``, use ``context.to_dict()``.rDrEzeInstead of ``CryptPolicy().to_dict()``, create a CryptContext instance and use ``context.to_dict()``.)rorrIrJrirjrs r.rjzCryptPolicy.to_dicts\    ..$ 3 ..$  3 }}$$W--r;c |jrttdztdnttdztd|jj |}t r|jd}|j|y)zexport policy to file. .. deprecated:: 1.6 applications should use :meth:`CryptContext.to_string` instead, and then write the output to a file as desired. zYInstead of ``context.policy.to_file(stream)``, use ``stream.write(context.to_string())``.rDrEz{Instead of ``CryptPolicy().to_file(stream)``, create a CryptContext instance and use ``stream.write(context.to_string())``.rNutf-8N) rorrIrJri to_stringrencodewrite)rrstreamrNouts r.to_filezCryptPolicy.to_files{    >>$ 3 >>$  3 mm%%g%6 **W%C Sr;c|jrttdztdnttdztd|jj |}|r|j |}|S)zexport policy to file. .. deprecated:: 1.6 applications should use :meth:`CryptContext.to_string` instead. zGInstead of ``context.policy.to_string()``, use ``context.to_string()``.rDrEziInstead of ``CryptPolicy().to_string()``, create a CryptContext instance and use ``context.to_string()``.r)rorrIrJrirr)rrrNrOrs r.rzCryptPolicy.to_string.st    00$ 3 00$  3 mm%%g%6 **X&C r;passlibrTFNNFrU)FFr)rN)__name__ __module__ __qualname____doc__ classmethodrKrQrarmrtriroryr~rr|rrrrrrjrrr=r;r.r#r#Xs8xGG.II.%I%IN;;4>@HL 12-(F(O&: V*@2" H.&.r;r#ceZdZdZdZdZdZdZdZdZ dZ dZ dZ dZ dZdZdZdZifdZd Zifd Zd Zed Zd ZdZdZdZdZeddZdZdZddZ ddZ!e"dZ#ddZ$y) _CryptConfigaparses, validates, and stores CryptContext config this is a helper used internally by CryptContext to handle parsing, validation, and serialization of its config options. split out from the main class, but not made public since that just complicates interface too much (c.f. CryptPolicy) :arg source: config as dict mapping ``(cat,scheme,option) -> value`` Nc|j|jd|j||j|j y)NNNr|)_init_scheme_listget _init_options_init_default_schemes _init_records)rrrRs r.ryz_CryptConfig.__init__zs@ vzz*?@A 6" ""$ r;cg}g}t|tr t|}|xsdD]}t|dr|}|j}t |n?t|trt |}|j}ntdt|z||vrtd||j||j|t||_ t||_ y)z,initialize .handlers and .schemes attributesr=r7z+scheme must be name or CryptHandler, not %rz"multiple handlers with same name: N)rYrrrr7r r r\r]rrqrr r|)rrdatar r|elemr9schemes r.rz_CryptConfig._init_scheme_lists d/ 0d#DJB #DtV$ &v.D"56+D1 !)+/:!677  & )** OOG $ NN6 ") #,h W~ r;c|j}|j}ix|_}ix|_}t }t |D]\\}}} } |j ||} |s |s | tvrd}|rT|| | \} } |dk(r| tvrtd| dt| dk(rtdt ||} | |} | | | <|r| dk(r td||| | \} } | dk(r || } | | |<|jdtt||_y#t$r | | i| |<YwxYw#t$r || | ii||<Y wxYw#t$r || i|| <Y wxYw) zYload config dict into internal representation, and init .categories attr allzThe 'zv' option should be configured per-algorithm, and not set globally in the context; This will be an error in Passlib 2.0zThe 'all' scheme is deprecated as of Passlib 1.7, and will be removed in Passlib 2.0; Please configure options on a per-algorithm basis.r|z4'schemes' context option is not allowed per categorymin_verify_timeN)_norm_scheme_option_norm_context_option_scheme_options_context_optionssetradd_global_settingsrrrJrdiscardrsorted categories)rrrRnorm_scheme_optionnorm_context_optionscheme_optionscontext_optionsrcatrrr-explicit_scheme category_map option_maps r.rz_CryptConfig._init_optionss "55"77022~244U *36):7 . % S&# NN3 $Ov#1A*A/U; UU?s2B'B !57 #e+=>PR 0#1 L0%1#%6 +0 33)+"$2330c5A U++.#23#7L).L%o7 .t 4 z 231$9-0%L S)9  A.1C<-@N6*A, 8,/$&GHH#@F%f.AB/u>RSSW,&6<(?@@ @ Ez% % ># %Ez O # /# % EzI FG GEzr;c:|jj||S)zreturn dict mapping category->value for specific context option. .. warning:: treat return value as readonly! )rr)rrr_defaults r.get_context_optionmapz"_CryptConfig.get_context_optionmap&s $$((h77r;c |j|}|jd}|r ||}|||k7r|dfS|dfS|dfS#t$rYywxYw#t$rY|dfSwxYw)zreturn value of specific option, handling category inheritance. also returns flag indicating whether value is category-specific. NFNTF)rrr)rrrrrr-alts r.get_context_option_with_flagz)_CryptConfig.get_context_option_with_flag-s 005L  &  %"8,=C5L9$e|ue|    e|  s =A A A  AAcJ |j||S#t$r|cYSwxYw)zsreturn all options for (scheme,category) combination .. warning:: treat return value as readonly! )rr)rrrrrs r._get_scheme_optionmapz"_CryptConfig._get_scheme_optionmapCs1  ''/9 9 N s  ""cR|j|jj|SrU)r r|index)rrrs r.get_base_handlerz_CryptConfig.get_base_handlerMs }}T\\//788r;ct|j}d|jvr|tjjz }|S)Nrounds) setting_kwdsuh HasRoundsusing_rounds_kwds)r9rs r.expand_settingsz_CryptConfig.expand_settingsPs5++ w++ + BLL:: :Lr;cD|j}|ddj}d}|r(|j}|j|d||j|j |}t |j |D]}|j||r0t j |D]}|j|||d} |j| |r0j| |j|||||k7rd}||fS)zreturn composite dict of all options set for scheme. includes options inherited from 'all' and from default category. result can be modified. returns (kwds, has_cat_specific_options) rNFT)rcopyrhrrr differencerw) rrrr get_optionmaprlhas_cat_optionsdefkwdsallowed_settingsrothers r.get_scheme_options_with_flagz)_CryptConfig.get_scheme_options_with_flagYs22 UD)..0 iikG KK eX6 7 //0E0Ef0MNt9''(89 C HHSM  7|../?@ ! C  !fd+ E  NN5 ! KK fh7 8w"&_$$r;c|j}|djx}|_|d}|j}|sy|j dxsd}|j d}|s|D] }||vs||d<nt d||vr t d|j D]Z}|j ||} |j ||} | s |D] }|| vs|||<:t d|z| | vsNt d|zy) zinitialize maps containing default scheme for each category. have to do this after _init_options(), since the default scheme is affected by the list of deprecated schemes. rrNr=z,must have at least one non-deprecated schemez#default scheme cannot be deprecatedz@C&DEEU" "8:=">?? ?r;c||j} ||S#t$rYnwxYw|js td|dS)z+return default scheme for specific categoryz9no hash schemes configured for this CryptContext instanceN)rrr|)rrrdefaultss r.default_schemez_CryptConfig.default_schemesR(( H% %   ||34 4~s  cjdfd}|dxsd}|r||}| ||k7r|dfS|dfS)z/is scheme deprecated under particular category?rcj|jd}|yd|vrj|k7S|vS)Nr)rr)rrRdepmaprrrs r.testz2_CryptConfig.is_deprecated_with_flag..testsMZZVZZ%56F~6!!4!4S!999''r;NFT)r)rrrrrr-rrs`` @r.is_deprecated_with_flagz$_CryptConfig.is_deprecated_with_flagsS++L9 (T #e x.C5C<Dy e|r;cNi|_ix}|_tx}|_|j}d|j z}|j D]Z}|j}|j|j|D],}|||\}} || s|j||fi||||f<.\y)NrU) _record_lists_recordsr context_kwdsrrr r7rh_create_record) rrrecordsall_context_kwdsrrr9rrrlrs r.rz_CryptConfig._init_recordss  "$$$-/2u44,88 t. }} UG\\F  # #G$8$8 9! U(3FC(@%o;/+>4+>+>w+Tt+TGFCK( U Ur;c F |jdddi|}||usJd||_||_ |S#t$rf}tjdt |}|r?|j d|vr,|j d}t d|jd|d}~wwxYw) NrelaxedTz&.* unexpected keyword argument '(.*)'$rczkeyword not supported by z handler: z"expected unique variant of handlerr=) usingr\rematchrgrouprr7_Context__orig_handlerr)r9rrsettingssubclserrmrs r.rz_CryptConfig._create_records #W]]<4<82M   383FFvx/0   FLMMs C22 C>=C>c |j|S#t$rYnwxYw|jDcgc]}|j||ncc}wc}x}|j|<|S)zxreturn list of records for category (cached) this is an internal helper used only by identify_record() )rrr|r))rrrrr-s r._get_record_listz_CryptConfig._get_record_listDsq %%h/ /    ,,0 OOFH -00 ""8, s Act|ts t|d|j|D]}|j |s|cS|sy|j s t dtjd)z?internal helper to identify appropriate custom handler for hashr>Nzno crypt algorithms supportedzhash could not be identified) rYrrr-identifyr|rrUnknownHashError)rrr>rrr*s r.identify_recordz_CryptConfig.identify_recordVst$ 67%dF3 3++H5 Ft$  :; ;&&'EF Fr;cd|jdD]}|js|cStd)NzLno disabled hasher present (perhaps add 'unix_disabled' to list of schemes?))r- is_disabled RuntimeError)rrr*s r.disabled_recordz_CryptConfig.disabled_recordnsA++D1 F!!  OP Pr;c# K|j}|j}t|}t|}d|vr|jd|r |jn |j }|rdt |fd|jzD]b}|D]/} |||}t|t r t |}|d|f|f1|D]'} || |} t| D]}|| |f| |f)dy#t$rYlwxYw#t$rYGwxYww)aregenerate original config. this is an iterator which yields ``(cat,scheme,option),value`` items, in the order they generally appear inside an INI file. if interpreted as a dictionary, it should match the original keywords passed to the CryptContext (aside from any canonization). it's mainly used as the internal backend for most of the public serialization methods. r|rrUN) rrrremover r|rrrYr) rrrfrr scheme_keys context_keysr-rrrrls r.rz_CryptConfig.iter_configysI--//^, o.   $    *!( dll )4;6 6T__, DDDrrUrr)%rrrrrrr r|rrrrrryrrrrrrrr staticmethodrrrrrrrrr)r-r1r r5rr=r;r.rrKsOHGJLHM  &LG4R &V358,?A9&%V)?V *U,.%6)NV$G0PP.dZ ed>dZ dZ dZ dZ ded fd Zd Zd Zd ZeeedZedZd?dZd?dZedZdZd@dZdAdZdBdZdZedZedZ edZ!dCdZ"dZ#dDdZ$dZ%d Z&d!Z'd"Z(dZ)d#Z*d$Z+dEd%Z,d&Z-dFd'Z.e/d(d)d*+dEd,Z0e/d-d).dEd/Z1e/d-d).dEd0Z2 dGd1Z3dEd2Z4e/d-d)d3+d4Z5dEd5Z6dEd6Z7d7Z8e9d8Z:d9Z;dHd:Zd=Z?y)Jr!a-Helper for hashing & verifying passwords using multiple algorithms. Instances of this class allow applications to choose a specific set of hash algorithms which they wish to support, set limits and defaults for the rounds and salt sizes those algorithms should use, flag which algorithms should be deprecated, and automatically handle migrating users to stronger hashes when they log in. Basic usage:: >>> ctx = CryptContext(schemes=[...]) See the Passlib online documentation for details and full documentation. Nct|tr|di|St||r|S|}|j||S)z2internal helper - accepts string, dict, or contextr=)rYrZload)rLrRrrs r. _norm_sourcezCryptContext._norm_sourcesA fd #==  $M5D IIf Kr;czt|ts t|dd|d}|j||||S)acreate new CryptContext instance from an INI-formatted string. :type source: unicode or bytes :arg source: string containing INI-formatted content. :type section: str :param section: option name of section to read from, defaults to ``"passlib"``. :type encoding: str :arg encoding: optional encoding used when source is bytes, defaults to ``"utf-8"``. :returns: new :class:`CryptContext` instance, configured based on the parameters in the *source* string. Usage example:: >>> from passlib.context import CryptContext >>> context = CryptContext.from_string(''' ... [passlib] ... schemes = sha256_crypt, des_crypt ... sha256_crypt__default_rounds = 30000 ... ''') .. versionadded:: 1.6 .. seealso:: :meth:`to_string`, the inverse of this constructor. zunicode or bytesrRF _autoloadrNrO)rYrrr=)rLrRrNrOrrs r.rQzCryptContext.from_stringsAB&"89#F,>I IU# &'H = r;c@|d}|j||||S)acreate new CryptContext instance from an INI-formatted file. this functions exactly the same as :meth:`from_string`, except that it loads from a local file. :type path: str :arg path: path to local file containing INI-formatted config. :type section: str :param section: option name of section to read from, defaults to ``"passlib"``. :type encoding: str :arg encoding: encoding used to load file, defaults to ``"utf-8"``. :returns: new CryptContext instance, configured based on the parameters stored in the file *path*. .. versionadded:: 1.6 .. seealso:: :meth:`from_string` for an equivalent usage example. Fr@rB) load_path)rLrMrNrOrrs r.rKzCryptContext.from_path s%6U# tWx@ r;c jtd}|j||r|j|d|S)a6Return copy of existing CryptContext instance. This function returns a new CryptContext instance whose configuration is exactly the same as the original, with the exception that any keywords passed in will take precedence over the original settings. As an example:: >>> from passlib.context import CryptContext >>> # given an existing context... >>> ctx1 = CryptContext(["sha256_crypt", "md5_crypt"]) >>> # copy can be used to make a clone, and update >>> # some of the settings at the same time... >>> ctx2 = custom_app_context.copy(default="md5_crypt") >>> # and the original will be unaffected by the change >>> ctx1.default_scheme() "sha256_crypt" >>> ctx2.default_scheme() "md5_crypt" .. versionadded:: 1.6 This method was previously named :meth:`!replace`. That alias has been deprecated, and will be removed in Passlib 1.8. .. seealso:: :meth:`update` Fr@Trh)r!r=)rrrlrs r.rzCryptContext.copy,s3@u- 4  JJtDJ ) r;c &|jdi|S)zG alias for :meth:`copy`, to match PasswordHash.using() r=)rrrrls r.rzCryptContext.usingRstyy 4  r;c Jtdtd|jdi|S)z deprecated alias of :meth:`copy`zCryptContext().replace() has been deprecated in Passlib 1.6, and will be removed in Passlib 1.8, it has been renamed to CryptContext().copy()rDrEr=)rrJrrHs r.rtzCryptContext.replaceXs, < A /tyy 4  r;Tc 4|||d<|turltdt||j|yt |t r-|j|j |j|ytd|r|j|y|rJdy)Nr|zThe CryptContext ``policy`` keyword has been deprecated as of Passlib 1.6, and will be removed in Passlib 1.8; please use ``CryptContext.from_string()` or ``CryptContext.from_path()`` instead.z%policy must be a CryptPolicy instancez/_autoload=False and kwds are mutually exclusive) _UNSETrrJr=rYr#rirhr\)rrr|policyrArls r.ryzCryptContext.__init__cs  %DO   9$  % ~ $FK0 &//* D! GHH  IIdO NN Ntr;cdt|zS)Nz)idr}s r.__repr__zCryptContext.__repr__s(2d833r;c8t|jdS)NT)rHro)r#rr}s r. _get_policyzCryptContext._get_policysTYY[tLLr;ctdtdt|tr|j |j yt d)NzThe CryptPolicy class and the ``context.policy`` attribute have been deprecated as of Passlib 1.6, and will be removed in Passlib 1.8; please use the ``context.load()`` and ``context.update()`` methods instead.rDrEzexpected CryptPolicy instance)rrJrYr#r=rir\)rrrLs r. _set_policyzCryptContext._set_policys> 5 A  / fk * IIfoo &;< .helpers*))&'4@D99T&91 1r;rt)rON)rasciirbr)ropenreaddecoderr) rrrMrhrNrOr^rfhtmps ```` r.rDzCryptContext.load_paths 2 dD84 &f~ & & + +dD! &Vf~ & &dD! ,Rggi&&x077@gcl+ , , & & & & , ,s#B*B6!?C*B36B?C cd}t|trAtrt||d}nt |d|d}|j t ||d}nQt|tr(t|jjd}d}nt|d s t|d d|r)|jtfd t|D}|rG|j;|sy |}t|jjd}|j|t!|}||_ |j#|j$|_|j(|_|j,r|j.j1d d y d |_y )aLoad new configuration into CryptContext, replacing existing config. :arg source: source of new configuration to load. this value can be a number of different types: * a :class:`!dict` object, or compatible Mapping the key/value pairs will be interpreted the same keywords for the :class:`CryptContext` class constructor. * a :class:`!unicode` or :class:`!bytes` string this will be interpreted as an INI-formatted file, and appropriate key/value pairs will be loaded from the specified *section*. * another :class:`!CryptContext` object. this will export a snapshot of its configuration using :meth:`to_dict`. :type update: bool :param update: By default, :meth:`load` will replace the existing configuration entirely. If ``update=True``, it will preserve any existing configuration options that are not overridden by the new source, much like the :meth:`update` method. :type section: str :param section: When parsing an INI-formatted string, :meth:`load` will look for a section named ``"passlib"``. This option allows an alternate section name to be used. Ignored when loading from a dictionary. :type encoding: str :param encoding: Encoding to use when **source** is bytes. Defaults to ``"utf-8"``. Ignored when loading from a dictionary. .. deprecated:: 1.8 This keyword, and support for bytes input, will be dropped in Passlib 2.0 :raises TypeError: * If the source cannot be identified. * If an unknown / malformed keyword is encountered. :raises ValueError: If an invalid keyword value is encountered. .. note:: If an error occurs during a :meth:`!load` call, the :class:`!CryptContext` instance will be restored to the configuration it was in before the :meth:`!load` call was made; this is to ensure it is *never* left in an inconsistent state due to a load error. .. versionadded:: 1.6 TrR)paramr)source_encodingrhz&reFrXzstring or dictc38K|]\}}||fywrUr=)rVrr-parses r.rXz$CryptContext.load../s&?(c5!:u-?N_strip_unused_context_kwds)rYrrr r r[rr!rZrrrr_parse_config_keyrrhr_reset_dummy_verifyr) _get_recordr1_identify_recordr__dict__rwrm) rrrRrhrNrO parse_keysrfconfigrks @r.r=zCryptContext.loadsj@ f4 5#FHHE!&'8(02++N6,BG,TVF  -&..44T4BCFJ)#F,helper used to parse ``cat__scheme__option`` keys into a tuplerrrcNrrDz'keys must have less than 3 separators: rzempty category: %rrxzempty scheme: %rzempty option: %r)rYrrtsplitrgr\)ckeypartscountrrrs r.rnzCryptContext._parse_config_keyIs$ 344 S$'--d3E  A:#T58C aZCKFC aZ$ C!$% % ) C0478 8 Y FF..56 6.56 6FCr;c|r=t|dkDr td|r td|j|ddy|r|j|dyy)aHelper for quickly changing configuration. This acts much like the :meth:`!dict.update` method: it updates the context's configuration, replacing the original value(s) for the specified keys, and preserving the rest. It accepts any :ref:`keyword ` accepted by the :class:`!CryptContext` constructor. .. versionadded:: 1.6 .. seealso:: :meth:`copy` rcz(expected at most one positional argumentz.positional arg and keywords mutually exclusiverTrFN)rgr\r=rrrsrls r.rhzCryptContext.updategsY 4y1} JKK PQQ IId1gdI +  IId4I (r;chjj}|rtfd|DS|S)a;return schemes loaded into this CryptContext instance. :type resolve: bool :arg resolve: if ``True``, will return a tuple of :class:`~passlib.ifc.PasswordHash` objects instead of their names. :returns: returns tuple of the schemes configured for this context via the *schemes* option. .. versionadded:: 1.6 This was previously available as ``CryptContext().policy.schemes()`` .. seealso:: the :ref:`schemes ` option for usage example. c3FK|]}j|yw)rNr8)rVrrrrrs r.rXz'CryptContext.schemes..s(0#fh\R0s!)rr|r)rrrfrrr|s` `` r.r|zCryptContext.schemess8.,,&& 0'.00 0Nr;cJ|jd||}|r|S|jS)ahreturn name of scheme that :meth:`hash` will use by default. :type resolve: bool :arg resolve: if ``True``, will return a :class:`~passlib.ifc.PasswordHash` object instead of the name. :type category: str or None :param category: Optional :ref:`user category `. If specified, this will return the catgory-specific default scheme instead. :returns: name of the default scheme. .. seealso:: the :ref:`default ` option for usage example. .. versionadded:: 1.6 .. versionchanged:: 1.7 This now returns a hasher configured with any CryptContext-specific options (custom rounds settings, etc). Previously this returned the base hasher from :mod:`passlib.hash`. Nr)r9r7)rrrrfrhashers r.rzCryptContext.default_schemes)<dH<H v1fkk1r;c |j||}|r |jS|S#t$rYnwxYw|jjrtd|td)ahelper to resolve name of scheme -> :class:`~passlib.ifc.PasswordHash` object used by scheme. :arg scheme: This should identify the scheme to lookup. If omitted or set to ``None``, this will return the handler for the default scheme. :arg category: If a user category is specified, and no scheme is provided, it will use the default for that category. Otherwise this parameter is ignored. :param unconfigured: By default, this returns a handler object whose .hash() and .needs_update() methods will honor the configured provided by CryptContext. See ``unconfigured=True`` to get the underlying handler from before any context-specific configuration was applied. :raises KeyError: If the scheme does not exist OR is not being used within this context. :returns: :class:`~passlib.ifc.PasswordHash` object used to implement the named scheme within this context (this will usually be one of the objects from :mod:`passlib.hash`) .. versionadded:: 1.6 This was previously available as ``CryptContext().policy.get_handler()`` .. versionchanged:: 1.7 This now returns a hasher configured with any CryptContext-specific options (custom rounds settings, etc). Previously this returned the base hasher from :mod:`passlib.hash`. z9crypt algorithm not found in this CryptContext instance: z8no crypt algorithms loaded in this CryptContext instance)rpr!rrr )rrrrrrs r.r9zCryptContext.handlersyL %%fh7F444     << :@CD D34 4s$$ 00cNtd|jjDS)zCcheck if any handlers in this context aren't in the global registryc36K|]}t|s|ywrU)r:rVr9s r.rXz:CryptContext._get_unregistered_handlers..2s=27;=s)rrr r}s r._get_unregistered_handlersz'CryptContext._get_unregistered_handlers0s%=DLL,A,A== =r;c.|jjS)z return :class:`!set` containing union of all :ref:`contextual keywords ` supported by the handlers in this context. .. versionadded:: 1.6.6 )rrr}s r.rzCryptContext.context_kwds5s||(((r;cD|\}}}|r|d|xsdd|S|r|d|S|S)z*convert 3-part config key to single stringrrxr=)rrroptions r.rzCryptContext._render_config_keyBs;"VV #&(;)(;VD D %v. .Mr;cHt|ttfrdj|}nLt|tr ?}}S$''r;cv|jtfd|jj|DS)agReturn current configuration as a dictionary. :type resolve: bool :arg resolve: if ``True``, the ``schemes`` key will contain a list of a :class:`~passlib.ifc.PasswordHash` objects instead of just their names. This method dumps the current configuration of the CryptContext instance. The key/value pairs should be in the format accepted by the :class:`!CryptContext` class constructor, in fact ``CryptContext(**myctx.to_dict())`` will create an exact copy of ``myctx``. As an example:: >>> # you can dump the configuration of any crypt context... >>> from passlib.apps import ldap_nocrypt_context >>> ldap_nocrypt_context.to_dict() {'schemes': ['ldap_salted_sha1', 'ldap_salted_md5', 'ldap_sha1', 'ldap_md5', 'ldap_plaintext']} .. versionadded:: 1.6 This was previously available as ``CryptContext().policy.to_dict()`` .. seealso:: the :ref:`context-serialization-example` example in the tutorial. c38K|]\}}||fywrUr=)rVrr-rs r.rXz'CryptContext.to_dict..s(I"U _e,Irl)rrZrr)rrrfrs @r.rjzCryptContext.to_dictbs=>,, I&*ll&>&>w&GII Ir;c|j}|j}|j||jj D])\}}|||}||}|j |||+y)z(helper to write to ConfigParser instanceN)rr add_sectionrrr)rrparserrNrrkvs r._write_to_parserzCryptContext._write_to_parsersk,, -- 7#<<++- &CAaQ"A1 A JJw1 % &r;c:t}|j||t}|j||j }|r*|jddj d|Dz|j }ts|jd}|S)aHserialize to INI format and return as unicode string. :param section: name of INI section to output, defaults to ``"passlib"``. :returns: CryptContext configuration, serialized to a INI unicode string. This function acts exactly like :meth:`to_dict`, except that it serializes all the contents into a single human-readable string, which can be hand edited, and/or stored in a file. The output of this method is accepted by :meth:`from_string`, :meth:`from_path`, and :meth:`load`. As an example:: >>> # you can dump the configuration of any crypt context... >>> from passlib.apps import ldap_nocrypt_context >>> print ldap_nocrypt_context.to_string() [passlib] schemes = ldap_salted_sha1, ldap_salted_md5, ldap_sha1, ldap_md5, ldap_plaintext .. versionadded:: 1.6 This was previously available as ``CryptContext().policy.to_string()`` .. seealso:: the :ref:`context-serialization-example` example in the tutorial. z# NOTE: the %s handler(s) are not registered with Passlib, # this string may not correctly reproduce the current configuration. rc3FK|]}t|jywrU)reprr7rs r.rXz)CryptContext.to_string..sMWd7<<0Ms!r) rrrrrrgetvaluerrd)rrrNrbuf unregisteredrs r.rzCryptContext.to_strings4"# fg. S668  II[IIM MMN Olln**W%C r; rDr&rc$|jyrU)ror}s r.reset_min_verify_timez"CryptContext.reset_min_verify_times   "r;c|r.t|ts t|d|j||S|j ||S)zCreturn record based on scheme, or failing that, by identifying hashr>)rYrrrprqrrr>rrs r._get_or_identify_recordz$CryptContext._get_or_identify_recordsE d$:;)$77##FH5 5((x8 8r;c|sy|jjj|j}|D]}|j|dy)af helper which removes any context keywords from **kwds** that are known to be used by another scheme in this context, but are NOT supported by handler specified by **record**. .. note:: as optimization, load() will set this method to None on a per-instance basis if there are no context kwds. N)rrrrw)rrrlr* unused_kwdsrs r.rmz'CryptContext._strip_unused_context_kwdssG ll//::6;N;NO  C HHS$  r;c|tdt|j|||}|jxs|j ||S)a Check if hash needs to be replaced for some reason, in which case the secret should be re-hashed. This function is the core of CryptContext's support for hash migration: This function takes in a hash string, and checks the scheme, number of rounds, and other properties against the current policy. It returns ``True`` if the hash is using a deprecated scheme, or is otherwise outside of the bounds specified by the policy (e.g. the number of rounds is lower than :ref:`min_rounds ` configuration for that algorithm). If so, the password should be re-hashed using :meth:`hash` Otherwise, it will return ``False``. :type hash: unicode or bytes :arg hash: The hash string to examine. :type scheme: str or None :param scheme: Optional scheme to use. Scheme must be one of the ones configured for this context (see the :ref:`schemes ` option). If no scheme is specified, it will be identified based on the value of *hash*. .. deprecated:: 1.7 Support for this keyword is deprecated, and will be removed in Passlib 2.0. :type category: str or None :param category: Optional :ref:`user category `. If specified, this will cause any category-specific defaults to be used when determining if the hash needs to be updated (e.g. is below the minimum rounds). :type secret: unicode, bytes, or None :param secret: Optional secret associated with the provided ``hash``. This is not required, or even currently used for anything... it's for forward-compatibility with any future update checks that might need this information. If provided, Passlib assumes the secret has already been verified successfully against the hash. .. versionadded:: 1.6 :returns: ``True`` if hash should be replaced, otherwise ``False``. :raises ValueError: If the hash did not match any of the configured :meth:`schemes`. .. versionadded:: 1.6 This method was previously named :meth:`hash_needs_update`. .. seealso:: the :ref:`context-migration-example` example in the tutorial. zqCryptContext.needs_update(): 'scheme' keyword is deprecated as of Passlib 1.7, and will be removed in Passlib 2.0r?)rrJrr needs_update)rrr>rrr?r*s r.rzCryptContext.needs_updatesUv   C# %--dFHE  LF$7$7V$7$LLr;z1.6z2.0zCryptContext.needs_update())rremoved replacementc(|j|||S)aLegacy alias for :meth:`needs_update`. .. deprecated:: 1.6 This method was renamed to :meth:`!needs_update` in version 1.6. This alias will be removed in version 2.0, and should only be used for compatibility with Passlib 1.3 - 1.5. )rrs r.hash_needs_updatezCryptContext.hash_needs_updateFs  vx88r;z1.7)rrc x|j||}|j}|r ||||jdi|S)zGenerate a config string for specified scheme. .. deprecated:: 1.7 This method will be removed in version 2.0, and should only be used for compatibility with Passlib 1.3 - 1.6. r=)rprm genconfig)rrrrr"r* strip_unuseds r.rzCryptContext.genconfigQsD!!&(366  6 *v+(++r;c ~|j|||}|j}|r ||||j||fi|S)zGenerate hash for the specified secret using another hash. .. deprecated:: 1.7 This method will be removed in version 2.0, and should only be used for compatibility with Passlib 1.3 - 1.6. )rrmgenhash)rrr?rtrrrlr*rs r.rzCryptContext.genhash`sH--ffhG66  v &v~~ff555r;cj|j|||}|y|r|r |jS|S|jS)aAttempt to identify which algorithm the hash belongs to. Note that this will only consider the algorithms currently configured for this context (see the :ref:`schemes ` option). All registered algorithms will be checked, from first to last, and whichever one positively identifies the hash first will be returned. :type hash: unicode or bytes :arg hash: The hash string to test. :type category: str or None :param category: Optional :ref:`user category `. Ignored by this function, this parameter is provided for symmetry with the other methods. :type resolve: bool :param resolve: If ``True``, returns the hash handler itself, instead of the name of the hash. :type required: bool :param required: If ``True``, this will raise a ValueError if the hash cannot be identified, instead of returning ``None``. :returns: The handler which first identifies the hash, or ``None`` if none of the algorithms identify the hash. N)rqr!r7)rrr>rrfrrr*s r.r/zCryptContext.identifyosBD&&tXx@ > 444 ;; r;c |tdt|j||}|j}|r ||||j|fi|S)aZrun secret through selected algorithm, returning resulting hash. :type secret: unicode or bytes :arg secret: the password to hash. :type scheme: str or None :param scheme: Optional scheme to use. Scheme must be one of the ones configured for this context (see the :ref:`schemes ` option). If no scheme is specified, the configured default will be used. .. deprecated:: 1.7 Support for this keyword is deprecated, and will be removed in Passlib 2.0. :type category: str or None :param category: Optional :ref:`user category `. If specified, this will cause any category-specific defaults to be used when hashing the password (e.g. different default scheme, different default rounds values, etc). :param \*\*kwds: All other keyword options are passed to the selected algorithm's :meth:`PasswordHash.hash() ` method. :returns: The secret as encoded by the specified algorithm and options. The return value will always be a :class:`!str`. :raises TypeError, ValueError: * If any of the arguments have an invalid type or value. This includes any keywords passed to the underlying hash's :meth:`PasswordHash.hash() ` method. .. seealso:: the :ref:`context-basic-example` example in the tutorial ziCryptContext.hash(): 'scheme' keyword is deprecated as of Passlib 1.7, and will be removed in Passlib 2.0)rrJrprmr>)rrr?rrrlr*rs r.r>zCryptContext.hashs`V   C# %!!&(366  v &v{{6*T**r;zCryptContext.hash()c&|j|i|S)a Legacy alias for :meth:`hash`. .. deprecated:: 1.7 This method was renamed to :meth:`!hash` in version 1.7. This alias will be removed in version 2.0, and should only be used for compatibility with Passlib 1.3 - 1.6. )r>r|s r.encryptzCryptContext.encryptstyy$'$''r;c |tdt||jy|j|||}|j}|r ||||j ||fi|S)averify secret against an existing hash. If no scheme is specified, this will attempt to identify the scheme based on the contents of the provided hash (limited to the schemes configured for this context). It will then check whether the password verifies against the hash. :type secret: unicode or bytes :arg secret: the secret to verify :type hash: unicode or bytes :arg hash: hash string to compare to if ``None`` is passed in, this will be treated as "never verifying" :type scheme: str :param scheme: Optionally force context to use specific scheme. This is usually not needed, as most hashes can be unambiguously identified. Scheme must be one of the ones configured for this context (see the :ref:`schemes ` option). .. deprecated:: 1.7 Support for this keyword is deprecated, and will be removed in Passlib 2.0. :type category: str or None :param category: Optional :ref:`user category ` string. This is mainly used when generating new hashes, it has little effect when verifying; this keyword is mainly provided for symmetry. :param \*\*kwds: All additional keywords are passed to the appropriate handler, and should match its :attr:`~passlib.ifc.PasswordHash.context_kwds`. :returns: ``True`` if the password matched the hash, else ``False``. :raises ValueError: * if the hash did not match any of the configured :meth:`schemes`. * if any of the arguments have an invalid value (this includes any keywords passed to the underlying hash's :meth:`PasswordHash.verify() ` method). :raises TypeError: * if any of the arguments have an invalid type (this includes any keywords passed to the underlying hash's :meth:`PasswordHash.verify() ` method). .. seealso:: the :ref:`context-basic-example` example in the tutorial kCryptContext.verify(): 'scheme' keyword is deprecated as of Passlib 1.7, and will be removed in Passlib 2.0F)rrJ dummy_verifyrrmverify)rrr?r>rrrlr*rs r.rzCryptContext.verifyszv   C# % <    --dFHE66  v &v}}VT2T22r;c b|tdt||jy|j|||}|j}|r|r|j }|||n|}|j ||fi|sy|js|j||rd|j|fd|i|fSy)a verify password and re-hash the password if needed, all in a single call. This is a convenience method which takes care of all the following: first it verifies the password (:meth:`~CryptContext.verify`), if this is successfull it checks if the hash needs updating (:meth:`~CryptContext.needs_update`), and if so, re-hashes the password (:meth:`~CryptContext.hash`), returning the replacement hash. This series of steps is a very common task for applications which wish to update deprecated hashes, and this call takes care of all 3 steps efficiently. :type secret: unicode or bytes :arg secret: the secret to verify :type secret: unicode or bytes :arg hash: hash string to compare to. if ``None`` is passed in, this will be treated as "never verifying" :type scheme: str :param scheme: Optionally force context to use specific scheme. This is usually not needed, as most hashes can be unambiguously identified. Scheme must be one of the ones configured for this context (see the :ref:`schemes ` option). .. deprecated:: 1.7 Support for this keyword is deprecated, and will be removed in Passlib 2.0. :type category: str or None :param category: Optional :ref:`user category `. If specified, this will cause any category-specific defaults to be used if the password has to be re-hashed. :param \*\*kwds: all additional keywords are passed to the appropriate handler, and should match that hash's :attr:`PasswordHash.context_kwds `. :returns: This function returns a tuple containing two elements: ``(verified, replacement_hash)``. The first is a boolean flag indicating whether the password verified, and the second an optional replacement hash. The tuple will always match one of the following 3 cases: * ``(False, None)`` indicates the secret failed to verify. * ``(True, None)`` indicates the secret verified correctly, and the hash does not need updating. * ``(True, str)`` indicates the secret verified correctly, but the current hash needs to be updated. The :class:`!str` will be the freshly generated hash, to replace the old one. :raises TypeError, ValueError: For the same reasons as :meth:`verify`. .. seealso:: the :ref:`context-migration-example` example in the tutorial. r)FNrTr)TN) rrJrrrmrrrrr>) rrr?r>rrrlr*r clean_kwdss r.verify_and_updatezCryptContext.verify_and_update- s@   C# % <    --dFHE66 DJ V ,J v}}VT8Z8   &"5"5d6"5"J6EHEEE Er;ztoo many secretsc8|j|jS)z> precalculated hash for dummy_verify() to use )r> _dummy_secretr}s r. _dummy_hashzCryptContext._dummy_hash s yy++,,r;cLt|jj|y)z> flush memoized values used by dummy_verify() N)r]r clear_cacher}s r.roz CryptContext._reset_dummy_verify s T **40r;cP|j|j|jy)a Helper that applications can call when user wasn't found, in order to simulate time it would take to hash a password. Runs verify() against a dummy hash, to simulate verification of a real account password. :param elapsed: .. deprecated:: 1.7.1 this option is ignored, and will be removed in passlib 1.8. .. versionadded:: 1.7 F)rrr)rrelapseds r.rzCryptContext.dummy_verify s! D&&(8(89r;c<|j|dj S)an test if hash represents a usuable password -- i.e. does not represent an unusuable password such as ``"!"``, which is recognized by the :class:`~passlib.hash.unix_disabled` hash. :raises ValueError: if the hash is not recognized (typically solved by adding ``unix_disabled`` to the list of schemes). N)rqr3)rrr>s r. is_enabledzCryptContext.is_enabled s ((t4@@@@r;cl|jj}|jsJ|j|S)a return a string to disable logins for user, usually by returning a non-verifying string such as ``"!"``. :param hash: Callers can optionally provide the account's existing hash. Some disabled handlers (such as :class:`!unix_disabled`) will encode this into the returned value, so that it can be recovered via :meth:`enable`. :raises RuntimeError: if this function is called w/o a disabled hasher (such as :class:`~passlib.hash.unix_disabled`) included in the list of schemes. :returns: hash string which will be recognized as valid by the context, but is guaranteed to not validate against *any* password. )rr5r3disablerrr>r*s r.rzCryptContext.disable s.(--!!!~~d##r;cd|j|d}|jr|j|S|S)a inverse of :meth:`disable` -- attempts to recover original hash which was converted by a :meth:`!disable` call into a disabled hash -- thus restoring the user's original password. :raises ValueError: if original hash not present, or if the disabled handler doesn't support encoding the original hash (e.g. ``django_disabled``) :returns: the original hash. N)rqr3enablers r.rzCryptContext.enable s5&&tT2   ==& &Kr;r)Frr)FNF)NFFrrr)NN)NNN)NFFF)rrU)@rrrrrrprqrr>rQrKrrrtrKryrOrQrSpropertyrLr:r[rDr=rnrhr|rr9rrrrrjrrmvt_estimate_max_samplesmvt_estimate_min_samplesmvt_estimate_max_timemvt_estimate_resolutionrrrrrmrrrrrr/r>rrrrr rrorrrrr=r;r.r!r!sD @GK   $$L<$L! ! $OD4 M =k;45F & &,8q3f  :)J<2b34j= ))(((!IF&'z "!"MO#(9 CMJ%Dab9c9%7 ,8 ,%7 68 6EJ#+Z6+p%DYZ ([ (K3ZZB'M-- 1 . A$0r;r!c4eZdZdZdZddZfdZdZxZS)r"aCryptContext subclass which doesn't load handlers until needed. This is a subclass of CryptContext which takes in a set of arguments exactly like CryptContext, but won't import any handlers (or even parse its arguments) until the first time one of its methods is accessed. :arg schemes: The first positional argument can be a list of schemes, or omitted, just like CryptContext. :param onload: If a callable is passed in via this keyword, it will be invoked at lazy-load time with the following signature: ``onload(**kwds) -> kwds``; where ``kwds`` is all the additional kwds passed to LazyCryptContext. It should perform any additional deferred initialization, and return the final dict of options to be passed to CryptContext. .. versionadded:: 1.6 :param create_policy: .. deprecated:: 1.6 This option will be removed in Passlib 1.8, applications should use ``onload`` instead. :param kwds: All additional keywords are passed to CryptContext; or to the *onload* function (if provided). This is mainly used internally by modules such as :mod:`passlib.apps`, which define a large number of contexts, but only a few of them will be needed at any one time. Use of this class saves the memory needed to import the specified handlers until the context instance is actually accessed. As well, it allows constructing a context at *module-init* time, but using :func:`!onload()` to provide dynamic configuration at *application-run* time. .. note:: This class is only useful if you're referencing handler objects by name, and don't want them imported until runtime. If you want to have the config validated before your application runs, or are passing in already-imported handler instances, you should use :class:`CryptContext` instead. .. versionadded:: 1.4 Nc |||d<||_y)Nr|) _lazy_kwds)rrr|rls r.ryzLazyCryptContext.__init__- s  %DOr;cV|j}d|vr[tdt|jd}|di|}tj |d}|j j}nd|vr|jd}|di|}|`tt|*di|t|_ y)N create_policyzThe CryptPolicy class, and LazyCryptContext's ``create_policy`` keyword have been deprecated as of Passlib 1.6, and will be removed in Passlib 1.8; please use the ``onload`` keyword instead.Frdonloadr=) rrrJrwr#rarirjsuperr"ryr! __class__)rrrlrresultrLrrs r. _lazy_initzLazyCryptContext._lazy_init2 s d " >$  % !HH_5M"*T*F ,,V5,AF??**,D  XXh'F>D>D O .66%r;c|jdr|jdr|j|jtj ||S)N_r) startswithrrobject__getattribute__)rrattrs r.rz!LazyCryptContext.__getattribute__E s@$(= OO '!&&tT22r;rU) rrrrrryrr __classcell__)rs@r.r"r" s1dJ &&3r;r"rU)Br __future__rrlogging getLoggerrlog threadingtimewarningsrrr passlib.excrrrpasslib.registryr r passlib.utilsr rr r rrrrrpasslib.utils.binaryrpasslib.utils.compatrrrrrrrrrrrpasslib.utils.decorrr __all__rrKr/rrrZr*rr:r:r@rrIr#rr!r"r=r;r.rs3& 'g''1 TTF.$$$$ E   M # <(-89 A j&jf\ <6\