I hereby claim:
- I am saoud on github.
- I am saoud (https://keybase.io/saoud) on keybase.
- I have a public key ASAkzMkZ__kwg30IWMEY-V4wa3xpwwr-jJlpDW8FZ4bNBAo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
#! /usr/bin/env bash | |
set -e | |
# Config | |
ZNC_VERSION="1.8.2" | |
# Ensure package list is up to date. | |
apt update | |
# Install runtime dependencies. |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
# Instructions for installing Pi-hole 4.2 on UniFi CloudKey Gen 1 (UC-CK) running firmware 0.13.6 | |
# Pi-hole will need to be completely re-installed after every FW update or if CloudKey is reset to defaults. | |
# Verify UC-CK is running firmware v0.13.6 (or later) before installing Pi-hole. If not, do: | |
ubnt-systool fwupdate https://dl.ubnt.com/unifi/stage/cloudkey/firmware/UCK/UCK.mtk7623.v0.13.6.7ad551e.190225.0939.bin | |
# UC-CK firmware v0.13.6 downgrades UniFi Controller to 5.10.17. Upgrade to 5.10.19 with: | |
cd /tmp | |
wget https://dl.ubnt.com/unifi/5.10.19/unifi_sysvinit_all.deb | |
dpkg -i unifi_sysvinit_all.deb |
firewall { | |
all-ping enable | |
broadcast-ping disable | |
ipv6-receive-redirects disable | |
ipv6-src-route disable | |
ip-src-route disable | |
log-martians enable | |
name WAN_IN { | |
default-action drop | |
description "WAN to internal" |