Linux server1.signalhg.team 4.18.0-553.134.1.el8_10.x86_64 #1 SMP Tue Jun 16 16:05:57 EDT 2026 x86_64
Apache
: 209.74.80.147 | : 216.73.216.85
150 Domain
8.1.34
signgwph
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
home /
signgwph /
signaltechdemo22.com /
config /
[ HOME SHELL ]
Name
Size
Permission
Action
app.php
4.18
KB
-rw-rw-rw-
auth.php
4.27
KB
-rw-rw-rw-
cache.php
3.36
KB
-rw-rw-rw-
database.php
5.95
KB
-rw-rw-rw-
filesystems.php
2.31
KB
-rw-rw-rw-
goat1.php
143.87
KB
-rw-r--r--
logging.php
4.21
KB
-rw-rw-rw-
mail.php
3.15
KB
-rw-rw-rw-
paypal.php
1.16
KB
-rw-rw-rw-
permission.php
6.93
KB
-rw-rw-rw-
queue.php
3.72
KB
-rw-rw-rw-
sanctum.php
3.03
KB
-rw-rw-rw-
services.php
973
B
-rw-rw-rw-
session.php
7.67
KB
-rw-rw-rw-
Delete
Unzip
Zip
${this.title}
Close
Code Editor : sanctum.php
<?php use Illuminate\Cookie\Middleware\EncryptCookies; use Illuminate\Foundation\Http\Middleware\ValidateCsrfToken; use Laravel\Sanctum\Http\Middleware\AuthenticateSession; use Laravel\Sanctum\Sanctum; return [ /* |-------------------------------------------------------------------------- | Stateful Domains |-------------------------------------------------------------------------- | | Requests from the following domains / hosts will receive stateful API | authentication cookies. Typically, these should include your local | and production domains which access your API via a frontend SPA. | */ 'stateful' => explode(',', env('SANCTUM_STATEFUL_DOMAINS', sprintf( '%s%s', 'localhost,localhost:3000,127.0.0.1,127.0.0.1:8000,::1', Sanctum::currentApplicationUrlWithPort(), // Sanctum::currentRequestHost(), ))), /* |-------------------------------------------------------------------------- | Sanctum Guards |-------------------------------------------------------------------------- | | This array contains the authentication guards that will be checked when | Sanctum is trying to authenticate a request. If none of these guards | are able to authenticate the request, Sanctum will use the bearer | token that's present on an incoming request for authentication. | */ 'guard' => ['web'], /* |-------------------------------------------------------------------------- | Expiration Minutes |-------------------------------------------------------------------------- | | This value controls the number of minutes until an issued token will be | considered expired. This will override any values set in the token's | "expires_at" attribute, but first-party sessions are not affected. | */ 'expiration' => null, /* |-------------------------------------------------------------------------- | Token Prefix |-------------------------------------------------------------------------- | | Sanctum can prefix new tokens in order to take advantage of numerous | security scanning initiatives maintained by open source platforms | that notify developers if they commit tokens into repositories. | | See: https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning | */ 'token_prefix' => env('SANCTUM_TOKEN_PREFIX', ''), /* |-------------------------------------------------------------------------- | Sanctum Middleware |-------------------------------------------------------------------------- | | When authenticating your first-party SPA with Sanctum you may need to | customize some of the middleware Sanctum uses while processing the | request. You may change the middleware listed below as required. | */ 'middleware' => [ 'authenticate_session' => AuthenticateSession::class, 'encrypt_cookies' => EncryptCookies::class, 'validate_csrf_token' => ValidateCsrfToken::class, ], ];
Close
