FoxiGram/TMessagesProj/jni/voip/webrtc/base/hash
instant992 8e79f2ee9c FoxiGram: Telegram client with built-in Xray VLESS proxy
Based on Nekogram. Key additions:
- Rebrand to FoxiGram (app name, APK name, applicationId com.foxigram.app)
- Embedded Xray (VLESS+Reality) proxy client via JNI libxray.so
- Bundled hidden one-tap proxies (LTE + WiFi), read-only in UI
- Auto-restore proxy on restart, rebind to active network (LTE/WiFi)
- Server credentials externalized to git-ignored XrayServers.java (+ template)
- libxray Go source included; compiled .so, keystore, google-services.json ignored
2026-06-08 16:41:07 +04:00
..
hash.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
hash.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
legacy_hash.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
legacy_hash.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_boringssl.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_boringssl.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_constexpr.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_constexpr_internal.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_nacl.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
md5_nacl.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
README.md FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
sha1.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
sha1.h FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00
sha1_boringssl.cc FoxiGram: Telegram client with built-in Xray VLESS proxy 2026-06-08 16:41:07 +04:00

Choosing A Hash Function

Note: this document is still very much a work-in-progress. Currently missing:

  • recommendations for hashed containers
  • recommendations for a better persistent hash
  • recommendations for a secure hash

If a hash function with unchanging output is needed, please select from one of the unchanging forever options below.

Non-cryptographic

name input output unchanging forever notes
Hash() overloaded uint32_t no This function is currently being updated to return size_t.
PersistentHash() overloaded uint32_t yes Fairly weak but widely used for persisted hashes.
CityHash64() base::span<const uint8_t> uint64_t yes (note 1) Version 1.0.3. Has some known weaknesses.
CityHash64WithSeed() base::span<const uint8_t> uint64_t yes (note 1) Version 1.0.3. Has some known weaknesses.

Cryptographic

There are no hashes in //base that provide cryptographic security.

name input output unchanging forever notes
MD5String() std::string std::string yes INSECURE
SHA1HashString std::string std::string yes INSECURE

Deprecated

Note: CRC32, Murmur2, and Murmur3 will be listed here.

Note 1: While CityHash is not guaranteed unchanging forever, the version used in Chrome is pinned to version 1.0.3.