| #!/bin/bash | |
| # Forticlient SSL VPN Client launching script utilizing expect. | |
| # -------------------------------------------- | |
| # CONFIGURATION | |
| # If empty - script will take some simple logic to locate appropriate binary. | |
| FORTICLIENT_PATH="" |
There's a workaround that might be useful for some people - use the Shadowsocks app for Android TV. Because that app only accepts a JSON configuration file, you need to convert the Outline key to JSON.
{
"server":"YOUR-SERVER",
"server_port":12345,
"local_port":1080,
"password":"YOUR-PASSWORD",
"method":"chacha20-ietf-poly1305",
| # Useful for improving Time Machine backup prep. times, Mac App Store install speeds, etc. | |
| sudo sysctl debug.lowpri_throttle_enabled=0 | |
| # To restore defaults | |
| sudo sysctl debug.lowpri_throttle_enabled=1 |
I have two user accounts set up on my mac. User drew I use for most things, but if I'm making a screencast I'll switch to the demo user. I know that the demo user has a clean desktop, and the font size is larger than usual in my terminal and text editors, making everything a bit more legible when capturing the screen. When I record a screencast as the demo user, I save the file to /Users/Shared/screencasts. As I understand it, the /Users/Shared directory is supposed to be accessible to all user accounts on the mac. If I created and saved a screenflow document as the demo user, I should be able to read and write that file when logged in as user drew.
That was the theory, but it didn't always work out that well in practice. I would occasionally find that a directory was only writable by one user or the other. Perhaps I'd open a screenflow document as user drew and attempt to export the video to the same directory, only to find that the directory was owned by demo, meaning that I couldn't cr
| Note: I've left some of the full package names in tact to show exactly where the class comes from. | |
| #### Pull dependencies in using composer #### | |
| //Example composer.json | |
| { | |
| "require": { | |
| "symfony/config" : "2.1.0", | |
| "symfony/yaml" : "2.1.0", | |
| "twig/twig": "1.9.0", |
You should never let passwords or private data be transmitted over an untrusted network (your neighbor’s, the one at Starbucks or the company) anyway, but on a hacker congress like the #30C3, this rule is almost vital.
Hackers get bored easily, and when they’re bored, they’re starting to look for things to play with. And a network with several thousand connected users is certainly an interesting thing to play with. Some of them might start intercepting the data on the network or do other nasty things with the packets that they can get.
If these packets are encrypted, messing with them is much harder (but not impossible! – see the end of this article). So you want your packets to be always encrypted. And the best way to do that is by using a VPN.
My typical setup for a development box in VirtualBox uses two NICs. The first uses NAT to allow the box to communicate with the outside world through my host computer’s network connection. (NAT is the default, so shouldn't require any setup.) The second is a "host-only" connection that allows my host and guest to interact.
To create a host-only connection in VirtualBox, start by opening the preferences in VirtualBox. Go to the "Network" tab, and addd a Host-only Network. Modify the host-only network, and disable DHCP. Make a note of the IP address. (Feel free to set the IP address as well, if you like.)
Next, assign this host-only adapter to the virtual machine. Select the VM and press "Settings". Go to the "Network" tab, and select "Adpater 2". Enable the adapter, set it to a "Host-only Adapter", and select the adpater you created above.
| /* This Source Code Form is subject to the terms of the Mozilla Public | |
| * License, v. 2.0. If a copy of the MPL was not distributed with this file, | |
| * You can obtain one at http://mozilla.org/MPL/2.0/. */ | |
| "use strict"; | |
| /* | |
| * thirty-two | |
| * https://github.com/chrisumbel/thirty-two | |
| * |
