m0j0hn

Preface:
I have no idea if any of this is the "right" way of doing it. This is just how I got my unit working.
Good luck.

WARNING: Do not use a V1 Waveshare display module with a stock pwnagotchi! The pwnagotchi expects a V2 module, and may irreparably damage a V1 module!
A V1 display module *can* work, but you must modify `waveshare.py` and `display.py` beforehand. For the time being, this is left as an exercise for the reader.
If you have already burnt a V1 display, try disconnecting it from the Pi and leaving it overnight. This may rejuvenate the display somewhat, but it will likely still display signs of damage.

Installation:
1. `dd` Raspbian Lite to an SD card.

m0j0hn

Enable specifying which asciidoctor-gradle-plugin backend(s) to run using gradle asciidoc -Pbackends=pdf,xhtml5.

asciidoctor {
  // Other configuration goes here

  backends = {
    // Enable -Pbackends='pdf,xhtml5' to specify backend(s) to use
    def BACKENDS = ['pdf','xhtml5'] // Default backends we use
 if(project.hasProperty('backends')){

m0j0hn

'''
Input MD5   : BB4E83D7A77AADD7F62728314EF09461
File Name   : C:\Program Files (x86)\Powersaves For AMIIBO\Powersaves For AMIIBO.exe

0x108fd0 : schannel_recv                    -> log buffer on end
0x1090d0 : schannel_recv end
0x108d10 : schannel_send                    -> log buffer on start

0xce61 : deals with https "Token"
0xceab : deals with https "Vuid"

m0j0hn

http://stackoverflow.com/questions/6612344/prevent-unit-tests-in-maven-but-allow-integration-tests

The maven-failsafe-plugin is for running Integration Tests.
Integration Tests, according to Maven lifecycle definition, come after Unit Tests - and after packaging.
And the maven-failsafe-plugin provides hooks to call code to install those packages, and reliably spin-up and tear-down services used by the Integration Tests regardless of success/failure of the test.
This is something the maven-surefire-plugin Unit Test plugin does not do, as it expects all its operations to be wholly confined to the JVM
My intent in adding the maven-failsafe-plugin is to give us better control over our tests, and to provide an easy way to migrate slow, non-Unit Tests to a different test harness, to be run after Unit Tests have passed. Once the maven-failsafe-plugin is available, this is as simple as renaming tests from Test.java or *Test.java to IT.java or *IT.java. And I will note that there are already some tests which match th

m0j0hn

Maven Speedups

There are several things one can do to speed up routine Maven builds - here is a non-exhaustive list of things to try - please let me know which ones work / don't work for you!

• TODO: (multicore/multithread options!!!)

• Prepare for offline mode: Tell Maven to download everything you depend on, so you can work offline.