ヤミRoot VoidGate
User / IP
:
216.73.217.162
Host / Server
:
15.235.182.215 / pollibazaar.com
System
:
Linux asia.cbnex.com 5.14.0-611.49.2.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 30 09:05:08 EDT 2026 x86_64
Command
|
Upload
|
Create
Mass Deface
|
Jumping
|
Symlink
|
Reverse Shell
Ping
|
Port Scan
|
DNS Lookup
|
Whois
|
Header
|
cURL
:
/
home
/
pollibazaar
/
public_html
/
config
/
Viewing: passport.php
<?php return [ /* |-------------------------------------------------------------------------- | Passport Guard |-------------------------------------------------------------------------- | | Here you may specify which authentication guard Passport will use when | authenticating users. This value should correspond with one of your | guards that is already present in your "auth" configuration file. | */ 'guard' => 'web', /* |-------------------------------------------------------------------------- | Encryption Keys |-------------------------------------------------------------------------- | | Passport uses encryption keys while generating secure access tokens for | your application. By default, the keys are stored as local files but | can be set via environment variables when that is more convenient. | */ 'private_key' => env('PASSPORT_PRIVATE_KEY'), 'public_key' => env('PASSPORT_PUBLIC_KEY'), /* |-------------------------------------------------------------------------- | Passport Database Connection |-------------------------------------------------------------------------- | | By default, Passport's models will utilize your application's default | database connection. If you wish to use a different connection you | may specify the configured name of the database connection here. | */ 'connection' => env('PASSPORT_CONNECTION'), /* |-------------------------------------------------------------------------- | Client UUIDs |-------------------------------------------------------------------------- | | By default, Passport uses auto-incrementing primary keys when assigning | IDs to clients. However, if Passport is installed using the provided | --uuids switch, this will be set to "true" and UUIDs will be used. | */ 'client_uuids' => false, /* |-------------------------------------------------------------------------- | Personal Access Client |-------------------------------------------------------------------------- | | If you enable client hashing, you should set the personal access client | ID and unhashed secret within your environment file. The values will | get used while issuing fresh personal access tokens to your users. | */ 'personal_access_client' => [ 'id' => env('PASSPORT_PERSONAL_ACCESS_CLIENT_ID'), 'secret' => env('PASSPORT_PERSONAL_ACCESS_CLIENT_SECRET'), ], ];
Coded With 💗 by
0x6ick