Skip to main content

Posts

Showing posts from December, 2016

`help_crack.py` Debian init script

Startup init script for the Distributed WPA PSK strength auditor python script Turning the `help_crack.py` utility into a system daemon can be achieved by utilizing the `screen` utility, below is my first attempt at it - feel free to comment with improvements or questions. #!/bin/sh ### BEGIN INIT INFO # Provides: # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO # Symbolic link this file into your `/etc/init.d`, then run `rcconf` and select the script to start, note the file name must be alphanumeric only # example: `root@sh1:/etc/init.d# ln -s /usr/local/wpa-sec.stanev.org-help_crack.py/help_crack.py.init.sh help_crack` dir="/usr/local/wpa-sec.stanev.org-help_crack.py" cmd="screen -d -m -S help_crack.py ./help_crack.py" user="" #!/bin/sh ### B

Lightning Out off Platform Example

Due to the limited documentation out there for the BETA Lightning Out functionality I am posting my code for others to benefit. Please note that after extensive research I have come to the conclusion that off platform functionality is broken, but executing the code from within a naked VF page should work. The issue is that the bootstrapping process does not adjust the URLs for the dynamically loaded scripts and styles sheets - the JS assumes it is still run from within a SF org domain. A case with SF has been filled but if I am incorrect on my conclusion please comment. Even if one patches the script/style URLs loading at runtime further errors manifest from withing aura_prod.js Salesforce's 'Lighting Out' Example Prior to using the below code ensure you have wrapped your lighting component into an App , setup a connected App , and CORS whitelisted your domain - afterwards copy and paste the below into your HTML file to be served from a server. ... <div

Windows Error: "Source Path Too Long"

Unable to delete folder due to 'path too long' error Windows dinosaur 256(?) path limitation weirdness prevented me from deleting a backup recovery folder, the solution to that is to use a utility called Unlocker - it also allows deletion/moving of locked files. If you found this useful feel free to follow me on twitter @danielsokolows or comment, also do donate the author of the program.