mirror of
https://github.com/fluffos/fluffos
synced 2026-08-12 18:26:06 -04:00
c914f03d66
* docs: add local full-text search and a contributor README Add @easyops-cn/docusaurus-search-local to the Docusaurus site so the docs get an offline search bar (index built at build time, no external service). English and zh-CN pages are both indexed, and matched terms are highlighted on the target page. Add docs/README.md describing the Docusaurus setup, local dev/build commands, search behavior, directory layout, and gotchas; exclude it from the published site alongside CLAUDE.md. Point the root README's docs/ entry at it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE * docs: remove dead framework leftovers, fix index generation, complete the nav Delete the VitePress (.vitepress/) and Jekyll (_layouts/, css/) leftovers, the one-shot migration scripts (fix_md_header.py, fix_seealso.py), and the stale keywords.json snapshot; prune the matching .gitignore entries and docusaurus exclude patterns. Rewrite gen_index.py for Docusaurus: it emitted dead .html links and legacy 'layout: doc' frontmatter, choked on non-markdown entries, and dropped nested categories — regenerating an index would have broken it. It now emits the extension-less links the site actually uses, links nested category indexes (restoring apply/* on the zh-CN index), and refuses to run on the docs root. Fix update_index.sh's copy-paste titles (zh-CN efun/build were titled 'APPLY'), stop it clobbering the hand-written lpc/index.md, and cover cli/. Regenerated indexes pick up the missing driver/ffi-plan entry. add_missing_efuns.py now takes the keywords.json path as an argument instead of requiring a stale copy. Move CNAME and the Google site-verification file into static/ so they actually reach the published build output. Complete the sidebar: link the CLI category to cli/index and add the missing portbind/symbol/generate_keywords pages, and expose the previously orphaned stdlib section under Reference. Promote onBrokenLinks to 'throw' now the build is warning-free, and drop the empty Demo section from the landing page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE * docs: strip legacy 'layout: doc' frontmatter from all pages Mechanical sweep removing the Jekyll-era 'layout: doc' line from every doc page's frontmatter (Docusaurus ignores it), and the matching line from the templates in docs/CLAUDE.md so new pages don't reintroduce it. No content changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE --------- Co-authored-by: Claude <noreply@anthropic.com>
2.3 KiB
2.3 KiB
| title |
|---|
| strings / hash |
hash
NAME
hash() - hash a string with the specified algorithm
SYNOPSIS
string hash( string algo, string str );
DESCRIPTION
Returns the hash of string `str` by the `algo` algorithm.
Algorithm `algo` can be one of:
**Legacy algorithms:**
md4 md5 ripemd160
**Legacy algorithms (OpenSSL 1.x - 2.x only):**
md2 mdc2
**SHA-1 and SHA-2 family:**
sha1 sha224 sha256 sha384 sha512
**SHA-3 family (recommended):**
sha3-224 sha3-256 sha3-384 sha3-512
**BLAKE2 family (high performance):**
blake2s256 blake2b512
**Other algorithms:**
sm3
This requires PACKAGE_CRYPTO to be enabled when compiling the driver.
**Compatibility Notes:**
- MD2 and MDC2 are only available with OpenSSL 1.x - 2.x (removed in OpenSSL 3.x)
- BLAKE2 family requires OpenSSL 1.1.0+
- SHA-3 family and SM3 require OpenSSL 1.1.1+
Note: For new applications, SHA-3 and BLAKE2 algorithms are recommended over
legacy MD and older SHA algorithms for better security and performance.
EXAMPLE
// Legacy algorithms
hash("md4", "Something") = "abc554cae9acd8f168101954383335df"
hash("md5", "Something") = "73f9977556584a369800e775b48f3dbe"
hash("sha1", "Something") = ...40 characters...
// Legacy algorithms (OpenSSL 1.x - 2.x only)
hash("md2", "Something") = ...32 characters... (if available)
hash("mdc2", "Something") = ...32 characters... (if available)
// SHA-2 family
hash("sha224", "Something") = ...56 characters...
hash("sha256", "Something") = ...64 characters...
hash("sha384", "Something") = ...96 characters...
hash("sha512", "Something") = ...128 characters...
// SHA-3 family (recommended for new applications)
hash("sha3-256", "Something") = ...64 characters...
hash("sha3-512", "Something") = ...128 characters...
// BLAKE2 family (high performance)
hash("blake2s256", "Something") = ...64 characters...
hash("blake2b512", "Something") = ...128 characters...
// Other algorithms
hash("ripemd160", "Something") = ...40 characters...
hash("sm3", "Something") = ...64 characters...
SEE ALSO
crypt(3), oldcrypt(3), sha1(3)