Search Results for "docs"

With Django Hijack, admins can log in and work on behalf of other users without having to know their credentials. 3.x docs are available in the docs folder. This version provides a security-first design, easy integration, customization, out-of-the-box Django admin support and dark mode. It is a complete rewrite and all former APIs are broken. A form is used to perform a POST including a CSRF-token for security reasons. The field user_pk is mandatory and the value must be set to the target users' primary key. ...

Protect My Docs is a free watermarking tool for PDF and image files. Add a fully customizable text watermark with AES-128 encryption, ZIP AES-256 export, and mail optimization. No Python installation required. Available for Windows, macOS, and Linux.

This repo is a public collection of malware samples and related dissection/analysis information, maintained by InQuest. It gathers various kinds of malicious artifacts, executables, scripts, macros, obfuscated documents, etc., with metadata (e.g., VirusTotal reports), file carriers, and sample hashes. It’s intended for malware analysts/researchers to help study how malware works, how they are delivered, and how it evolves.

...All images and random phrases can be changed by creating files under the .BloodyProfanity directory. Files that can be overloaded include: .BloodyProfanity/conf/sarcasm.yaml # random fail messages, begin every line with '-' (see yaml docs for more) .BloodyProfanity/img/bg.png .BloodyProfanity/img/error.png Other settings can be changed by editing the globals near the top of locker.py. REQUIREMENTS: KDE, PyYAML, Subprocess32, wxPython, fprintd and of course Python. INSTALLATION # As root b=/usr/share/BloodyProfanity cp -rvp /path/to/bp $b g=/usr/lib/kde4/libexec/kscreenlocker_greet cp -v $g $g.bak cp -vpf $b/locker.py $g # As user fprintd-enroll fprintd-verify # important mkdir -p ~/.BloodyProfanity/conf ~/.BloodyProfanity/img

...Once urls are harvested from google dorks they are saved to a log file for future reference. One a sql check is run, the vulnerable URLs are saved to a seperate log file. View the readme in /docs for more information.