X7ROOT File Manager
Current Path:
/home/cbholdings/pasukulu/lib/adodb
home
/
cbholdings
/
pasukulu
/
lib
/
adodb
/
📁
..
📄
LICENSE.md
(25.79 KB)
📄
README.md
(4.32 KB)
📄
SECURITY.md
(1.37 KB)
📄
adodb-active-record.inc.php
(27.92 KB)
📄
adodb-active-recordx.inc.php
(37.82 KB)
📄
adodb-csvlib.inc.php
(8.63 KB)
📄
adodb-datadict.inc.php
(28.53 KB)
📄
adodb-error.inc.php
(9.21 KB)
📄
adodb-errorhandler.inc.php
(3.03 KB)
📄
adodb-errorpear.inc.php
(2.56 KB)
📄
adodb-exceptions.inc.php
(2.66 KB)
📄
adodb-lib.inc.php
(37.69 KB)
📄
adodb-loadbalancer.inc.php
(26.2 KB)
📄
adodb-memcache.lib.inc.php
(9.55 KB)
📄
adodb-pager.inc.php
(7.87 KB)
📄
adodb-pear.inc.php
(9.63 KB)
📄
adodb-perf.inc.php
(30.63 KB)
📄
adodb-time.inc.php
(42.73 KB)
📄
adodb-xmlschema.inc.php
(54.05 KB)
📄
adodb-xmlschema03.inc.php
(61.52 KB)
📄
adodb.inc.php
(153.34 KB)
📁
datadict
📁
drivers
📄
index.html
(0 B)
📁
lang
📁
perf
📄
phpdoc
(732 B)
📄
phpdoc.dist.xml
(542 B)
📄
pivottable.inc.php
(6.46 KB)
📄
readme_moodle.txt
(1.59 KB)
📄
rsfilter.inc.php
(1.74 KB)
📄
toexport.inc.php
(3.69 KB)
📄
tohtml.inc.php
(5.77 KB)
📄
xmlschema.dtd
(1.42 KB)
📄
xmlschema03.dtd
(1.64 KB)
📁
xsl
Editing: SECURITY.md
# ADOdb Security Policy ## Supported Versions The following releases of the library are currently being supported with security updates. Please refer to the [project's home page](https://adodb.org) for actual version numbers. - Stable - Legacy - Development (Git *master* branch) Older releases are no longer supported. ## Reporting a Vulnerability If you discover a vulnerability in ADOdb, please contact the [project's maintainer](https://github.com/dregad) - by e-mail (look for it in the Git history) - via private chat on [Gitter](https://gitter.im/dregad) Kindly provide the following information in your report: - Affected ADOdb version(s) or Git revision - A clear and detailed description of the issue, including if possible a code snippet to demonstrate or reproduce the vulnerability - A patch for the issue if you have one, preferably in *Git diff* format ### CVE handling To ensure a comprehensive and detailed declaration of the issue, we generally prefer requesting CVE IDs ourselves, which usually happens after our analysis confirms the vulnerability. In case you have already obtained a CVE ID, do not forget to reference it in your report. ### Credits Let us know if and how you wish to be credited for the finding. Your name, e-mail, company, etc. will be included as specified in the CVE report, as well as in the Git commit message patching the issue.
Upload File
Create Folder