Mini File Manager

ZSec File Manager

Current Directory: /home/aiessinternational.com/public_html

[Up]

.. [Open]

.htaccess [Edit]

21cbfe [Open]

ALFA_DATA [Open]

advance [Open]

advance.zip [Edit]

ammika.php [Edit]

c8aa5 [Open]

click.php [Edit]

defaults.php [Edit]

google41b982abb0d9ca3b.html [Edit]

index.php [Edit]

index.php0 [Edit]

item.php [Edit]

license.txt [Edit]

mah.php [Edit]

networks.php [Edit]

options.php [Edit]

plugins.php [Edit]

product.php [Edit]

readme.html [Edit]

robots.txt [Edit]

saiga.php [Edit]

search.php [Edit]

web.config [Edit]

wp-activate.php [Edit]

wp-admin [Open]

wp-blog-header.php [Edit]

wp-comments-post.php [Edit]

wp-config-sample.php [Edit]

wp-config.php [Edit]

wp-content [Open]

wp-cron.php [Edit]

wp-includes [Open]

wp-links-opml.php [Edit]

wp-load.php [Edit]

wp-log1n.php [Edit]

wp-mail.php [Edit]

wp-settings.php [Edit]

wp-signup.php [Edit]

wp-trackback.php [Edit]

wp.php [Edit]

xmlrpc.php [Edit]

Edit File

# These settings are specific to hardening the kernel itself from attack
# from userspace, rather than protecting userspace from other malicious
# userspace things.
#
#
# When an attacker is trying to exploit the local kernel, it is often
# helpful to be able to examine where in memory the kernel, modules,
# and data structures live. As such, kernel addresses should be treated
# as sensitive information.
#
# Many files and interfaces contain these addresses (e.g. /proc/kallsyms,
# /proc/modules, etc), and this setting can censor the addresses. A value
# of "0" allows all users to see the kernel addresses. A value of "1"
# limits visibility to the root user, and "2" blocks even the root user.
kernel.kptr_restrict = 1

# Access to the kernel log buffer can be especially useful for an attacker
# attempting to exploit the local kernel, as kernel addresses and detailed
# call traces are frequently found in kernel oops messages. Setting
# dmesg_restrict to "0" allows all users to view the kernel log buffer,
# and setting it to "1" restricts access to those with CAP_SYSLOG.
#
# dmesg_restrict defaults to 1 via CONFIG_SECURITY_DMESG_RESTRICT, only
# uncomment the following line to disable.
# kernel.dmesg_restrict = 0