Kernel Panic support?

[spotlightishere]

Is there any way to keep testing after a kernel panic?

[spotlightishere]

I noticed that you added that it would be easy, but you would need a math wizard to start implimenting it. I'm not, but I probally could try.

[compilingEntropy]

Support for this is planned, but optimizing the algorithm for speed has proven difficult--the amount of tests you can complete in one boot cycle needs to be calculated in the testing phase, and that value taken into consideration when dividing the file.
For now, it'll just take a long time to do kernel panics. Create a launch daemon in /System/Library/LaunchDaemons/com.compilingentropy.bytefinder.plist that loads bytefinder. Bytefinder will need to be modified to save and resume (when applicable) its progress, like fuzzycactus.

Here's a sample launch daemon:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>AbandonProcessGroup</key>
        <true/>
        <key>Label</key>
        <string>com.compilingentropy.bytefinder</string>
        <key>ProcessType</key>
        <string>Interactive</string>
        <key>ProgramArguments</key>
        <array>
                <string>/usr/var/finder.sh</string>
                <string>start</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
</dict>
</plist>

[spotlightishere]

Ok. I'll mess around with it. If it works, I'll also add my runtime patches.

[compilingEntropy]

It would take a math wizard (or a lot of my time) to do it right, but it could be done really inefficiently without adding much. =P

[spotlightishere]

Wait.. the problem is that it starts at boot, right? If the iThing is locked, it couldn't run. How would we bypass that?

[compilingEntropy]

Yeah, unlocking broke back in iOS 7 (see the bug filed in innoying's sbutils). I'd suggest finding a tweak that disables the lock screen entirely.

[spotlightishere]

How would you get the real path to something? In case the user enters ../files/file.file?

[compilingEntropy]

This is how I did it in fuzzycactus:

    #relative paths
    path="$( pwd )"
    if [[ "${file:0:2}" == "./" ]]; then
        file="$path/${file:2}"
    elif [[ "${file:0:3}" == "../" ]]; then
        file="$path/$file"
    fi

    if [[ ! -e "$file" ]]; then
        echo "The provided file does not exist."
        echo "Please check your path and try again."
        cleanexit
    fi

Most if not all of the code needed is in fuzzycactus actually.

[spotlightishere]

YES! This is tough (I'm more web development) but its fun learning along the way.

[spotlightishere]

Actually, I see you implimented that already. Ignore me.

[spotlightishere]

Ok. I got it to make the LaunchAgent file. My hands are falling off. I'm going to create a pull request, and then I have to move on to soemthing else. Oh, I added something you forgot.

[spotlightishere]

On CoolStar's public repo, there is a tweak to remove the passcode over SSH. Would this be helpful?

[compilingEntropy]

Yeah, if I were to add that to the dependencies and run it at the beginning it'd probably solve a lot of problems (assuming it works as I imagine it does, I haven't actually tested it). Then we'd just need another tweak to disable the lockscreen entirely.