theotherside

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

theotherside

//
//  AppDelegate.m
//  NanoCompanion
//
//  Created by Steven Troughton-Smith on 13/01/2015.
//  Copyright (c) 2015 High Caffeine Content. All rights reserved.
//

#import "AppDelegate.h"

theotherside

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.

Table of Contents

• Motivation
• Audience
• TL;DR?
• Updates
• Technologies that Affect Security and Privacy

theotherside

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intented purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

Why not?

Because a VPN in this sense is just a glorified proxy. The VPN provider can see all your traffic, and do with it what they want - including logging.

theotherside

# coding: utf-8
from Foundation import *
from QuartzCore import *
from UIKit import *

import console

WKWebView = ObjCClass('WKWebView')
	
@on_main_thread

theotherside

# coding: utf-8
from Foundation import *
from QuartzCore import *
from UIKit import *

import console

WKWebView = ObjCClass('WKWebView')
	
@on_main_thread

theotherside

# coding: utf-8
from objc_util import *
import console
import urllib
import dialogs

WKWebView = ObjCClass('WKWebView')
UIViewController = ObjCClass('UIViewController')
UIBarButtonItem = ObjCClass('UIBarButtonItem')
NSURLRequest = ObjCClass('NSURLRequest')

theotherside

# coding: utf-8

from UIKit import *
from Foundation import *
from ctypes import *

libobjc = CDLL('/usr/lib/libobjc.dylib')

QLPreviewController = ObjCClass('QLPreviewController')

theotherside

# coding: utf-8

from UIKit import *

def main():
	rootVC = UIApplication.sharedApplication().keyWindow().rootViewController()
	tabVC = rootVC.detailViewController()
	
	methods = [pydiaButtonPressed]
	PydiaItemController = create_objc_class('PydiaItemController', NSObject, methods = methods)

theotherside

Git cheat list

• all commits that your branch have that are not yet in master

  git log master..<HERE_COMES_YOUR_BRANCH_NAME>
  

• setting up a character used for comments

git config core.commentchar