elpatron
262cffe4a6
- Scripts: start-webdav.cmd, stop-webdav.cmd (echo messages, REM comments) - Server: server.js (console.log, HTTP error messages) - Token tools: token-test.js, token-refresh.js - Other: auth-poc.js, debug-name-decrypt.js, internxt-client.js, upload.js - Docs: README, .env.example, docs/*.md Made-with: Cursor
36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
# Extract CRYPTO_SECRET from drive.internxt.com
|
||
|
||
If login fails with "Wrong login credentials", `CRYPTO_SECRET` is likely incorrect. drive-web uses `REACT_APP_CRYPTO_SECRET`, which may differ from the CLI value (`6KYQBP847D4ATSFA`).
|
||
|
||
## Method 1: DEBUG mode (verify salt decryption)
|
||
|
||
```bash
|
||
DEBUG=1 npm run auth-test
|
||
```
|
||
|
||
- **"Salt decryption OK"** → CRYPTO_SECRET is correct, problem is elsewhere (password, API)
|
||
- **"Salt decryption failed"** → CRYPTO_SECRET is wrong
|
||
|
||
## Method 2: Search for secret in browser
|
||
|
||
1. Open https://drive.internxt.com
|
||
2. DevTools (F12) → **Sources**
|
||
3. **Ctrl+Shift+F** (search in all files)
|
||
4. Search for:
|
||
- `6KYQBP847D4ATSFA` – if found, same value as CLI is used
|
||
- `REACT_APP_CRYPTO_SECRET` or `CRYPTO_SECRET`
|
||
- Hex strings (e.g. 16 chars like `a1b2c3d4e5f6...`)
|
||
|
||
5. Add found value to `.env`:
|
||
```
|
||
CRYPTO_SECRET=found_value
|
||
```
|
||
|
||
## Method 3: Build drive-web locally (with known secret)
|
||
|
||
If you have access to drive-web and know the correct secret:
|
||
|
||
1. Create `.env` in `drive-web` with `REACT_APP_CRYPTO_SECRET=...`
|
||
2. Run `yarn build`
|
||
3. Search build artifacts for the embedded value
|