- Zoom abuses the installer flow on MacOS to bypass permissions dialogs (source)
- Zoom sends identifying device info to Facebook, even when users don't have a Facebook account (source) (fixed)
- A bug in Zoom sent identifying information (including email addresses and profile pictures) of thousands of users to strangers (source)
- Zoom claims that meetings are end-to-end encrypted in their white paper and marketing materials, but meetings are only encrypted in transit, and are available in plaintext to Zoom servers and employees. (source)
zoomAutenticationTool
can be used to escalat
/* | |
* From https://www.open-mpi.org/faq/?category=runcuda | |
* Command: | |
* $ mpic++ cuda_aware_check.cpp | |
* $ mpirun a.out | |
* Program that shows the use of CUDA-aware macro and runtime check. | |
* Requires Open MPI v2.0.0 or later. | |
*/ | |
#include <stdio.h> | |
#include "mpi.h" |
I'm still not sure what but on both my systems my keys just don't get loaded back into the ssh-agent on restarts and new login sessions. I got annoyed enough at it that I jumped through the hoops of putting ssh-add into a script and writting a property list file to load as a launchagent to fix it.
If you haven't done so already you can use the well written gub hub instructions for generating ssh keys. Once you get them generated you'll add them with ssh-add -K <sshkey>
where sshkey is the file path/name. Keys are stored by default in your ~/.ssh folder
Note that you may need to use ssh-add --apple-use-keychain
in Big Sur onward instead of ssh-add -K
. I discovered the issue in Montery after skipping Big Sur.
The manual method (assuming your keys were stored into the Mac OS Keychain) is to open up Terminal
- macOS 10.15.5
- tmux 3.1b
macOS has ncurses version 5.7 which does not ship the terminfo description for tmux. There're two ways that can help you to solve this problem.
Instead of tmux-256color
, use screen-256color
which comes with system. Place this command into ~/.tmux.conf
or ~/.config/tmux/tmux.conf
(for version 3.1 and later):
If you're using a high-end bluetooth headset on your Macbook Pro it's likely your mac is using an audio codec which favors battery efficiency over high quality. This results in a drastic degradation of sound, the SBC codec is the likely culprit, read more about it here.
import numpy as np | |
from matplotlib.colors import LinearSegmentedColormap as LSC | |
from matplotlib.cm import register_cmap | |
def modulo_cmap(cmap, name=None): | |
colors = np.roll(cmap(np.arange(cmap.N)), cmap.N // 2, axis=0) | |
if name is None: | |
name = map.name + "_mod" | |
return LSC.from_list(name, colors, cmap.N) |
"""Dead simple ANSI coloring.""" | |
import os | |
import sys | |
RED = 31 | |
GREEN = 32 | |
YELLOW = 33 | |
BOLD = 1 | |
RESET_ALL = 0 |
''' Script for downloading all GLUE data. | |
Note: for legal reasons, we are unable to host MRPC. | |
You can either use the version hosted by the SentEval team, which is already tokenized, | |
or you can download the original data from (https://download.microsoft.com/download/D/4/6/D46FF87A-F6B9-4252-AA8B-3604ED519838/MSRParaphraseCorpus.msi) and extract the data from it manually. | |
For Windows users, you can run the .msi file. For Mac and Linux users, consider an external library such as 'cabextract' (see below for an example). | |
You should then rename and place specific files in a folder (see below for an example). | |
mkdir MRPC | |
cabextract MSRParaphraseCorpus.msi -d MRPC |
Here are the steps to installing and setting up GDB on Mac OS Sierra/High Sierra.
Run brew install gdb
.
On starting gdb, you will get the following error:
Unable to find Mach task port for process-id 2133: (os/kern) failure (0x5).
(please check gdb is codesigned - see taskgated(8))
To fix this error, follow the following steps: