Daniel Sokolowski's Blog

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...

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...

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.

Protocol error occurred. Error was returned from the destination server. The Softether server by default to run on port 443 , if you server also hosts normal https then 443 is already taken and so Softether can't bind to it. When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server. By default Softether also listens on 992 , 1194 , and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows .

Save error: A problem was encountered while invoking the subscription method If in the Salesforce 'Developer Console' you get the error mentioned in the subject or if you in Eclipse Force.com IDE you get: Save error: A problem was encountered while invoking the subscription method: No TOKENS named markup://c:defaultTokens foundproblem Save error: COMPONENT's markup cannot be empty. If you are trying to delete the Lightning definition bundle, directly delete the bundle instead. Save error: QualifiedName is required for descriptors Then ensure that you don't have an empty `controller=""` attribute, this took a me a little while to notice so for the prosperity of others and my own memory forming benefit I am posting this. If this has helped you feel free to follow @danielsokolows or thanks comment.

Fix for: `Command '/usr/bin/python src/build/linux/sysroot_scripts/install-sysroot.py --running-as-hook' returned non-zero exit status 1 in /root/chromium-src`. As part of some R&D for a JS framework I have been thinking of for a while I needed to do some Chromium hacking, problem is I hit a wall just simply attempting to check out the source code. This was on a fresh Debian VM machine following the official checkout docs . root@lh1:~/chromium-src# fetch --no-history chromium Running: gclient root Running: gclient config --spec 'solutions = [ { "url": "https://chromium.googlesource.com/chromium/src.git", "managed": False, "name": "src", "deps_file": ".DEPS.git", "custom_deps": {}, }, ] ' Running: gclient sync --no-history Error: Command '/usr/bin/python src/build/linux/sysroot_scripts/install-sysroot.py --running-as-hook' returned non-zero exit status...

"Save error: Package Visibility: Type is not visible: " If all other checks fail and you are actually able to reference ` ` than in my experience this error is caused due to the fact that the class you are working on has been updated on the server. Solution is to disable tooling api support in project properties. If this has helped you please comment or follow me @danielsokolows .