With the recent removal of the 140-character limit in Direct Messages by Twitter, DM's have now become a much more useful platform for communicating between individuals and groups. Sadly, DM's are still sent in plaintext between users and Twitter has no plans currently on encrypting these messages, at least as of August 2015. Since these are stored in plaintext at rest, an adversary can see the content of the message you are sending, which the two parties might not wish to happen. Fortunately as a few applications with basic Twitter support which also have excellent support for OTR, all hope isn't lo
# Author: Aram Grigorian <aram@opendns.com> | |
# https://github.com/aramg | |
# https://github.com/opendns | |
# | |
# By default, nginx will close upstream connections after every request. | |
# The upstream-keepalive module tries to remedy this by keeping a certain minimum number of | |
# persistent connections open at all times to upstreams. These connections are re-used for | |
# all requests, regardless of downstream connection source. There are options available | |
# for load balacing clients to the same upstreams more consistently. | |
# This is all designed around the reverse proxy case, which is nginxs main purpose. |
/* | |
$ cryptol blake256.cry | |
_ _ | |
___ _ __ _ _ _ __ | |_ ___ | | | |
/ __| '__| | | | '_ \| __/ _ \| | | |
| (__| | | |_| | |_) | || (_) | | | |
\___|_| \__, | .__/ \__\___/|_| | |
|___/|_| version 2.2.4 | |
Loading module Cryptol |
Edward Snowden answered questions after a showing of CITIZENFOUR at the IETF93 meeting; this is a transcript of the video recording.
For more information, see the Internet Society article.
git-prebase improves on 'git rebase -i' by adding information per commit regarding which files it touched.
- Each file gets an alpha-numeric identifier at a particular column, a list of which appears below the commit list. (The identifiers wrap around after the 62nd file)
- Commits can be moved up and down safely (without conflicts) as long as their columns don't clash (they did not touch the same file).
Add the executable to your path and git will automatically expose it as
The purpose of this document is to make recommendations on how to browse in a privacy and security conscious manner. This information is compiled from a number of sources, which are referenced throughout the document, as well as my own experiences with the described technologies.
I welcome contributions and comments on the information contained. Please see the How to Contribute section for information on contributing your own knowledge.
This list has moved to the following page:
http://anonymoushash.vmbrasseur.com/resources/negotiation/
It's joining a number of other lists of resources (management, telecommuting, etc.):
http://anonymoushash.vmbrasseur.com/resources/
Keeping them all together like this makes it much more likely I'll maintain them (as a group they'll have a larger mindshare in my cluttered & busy brain) rather than fire & forget a list which is never updated again.
// Written Alan Ward -- copied from larger program, not fully tested | |
// Placed into the public domain | |
char worker_endpoint [128], worker_endpoints [1024]; | |
int process_instance; | |
worker_endpoints [0] = 0; | |
// start async worker processes | |
for ( process_instance = 0; process_instance < CFG_Backend_Threads; process_instance++ ) { |
In response to some people claiming that using a CSPRNG is "going way overboard" and/or is "overkill", I've written this test to verify the performance impact of using a CSPRNG versus their insecure mt_rand()
based hacks.
I think the results are conclusive (at least on my device): A 50% speed increase. In addition to less-predictable randomness.
If anyone would like to suggest a benchmark script (or conditions that lead to different results with mine), let me know and I will link to them here.