141–150 of 200 posts
Earlier quoted context omitted.
A computer is only secure if it remains powered off and airgapped.
Turn off your computer and make sure it powers down Drop it in a 43-foot hole in the ground Bury it completely, rocks and boulders should be fine
Earlier quoted context omitted.
Turn off your computer and make sure it powers down Drop it in a 43-foot hole in the ground Bury it completely, rocks and boulders should be fine
> rocks and boulders should be fine You’re setting yourself up for a supply chain attach here if you trust whatever rocks and boulders are sitting around. A well resourced adversary may have placed power supply boulders and wifi rocks in your back yard.
Tomorrow is a new day.
Fun game, but it showed the lack of security hygiene employed by the game writer. It said `cat ~/.zshrc` was bad because it would share tokens and secrets, but I would never put secrets into my shell rc.
Fun game, but it showed the lack of security hygiene employed by the game writer. It said `cat ~/.zshrc` was bad because it would share tokens and secrets, but I would never put secrets into my shell rc.
Earlier quoted context omitted.
Where would you put them?
Literally anywhere else! Your dotfiles should be publishable to github. If they aren't you're doing them wrong. A good thing to do is organize. You can actually load different files. Here's a pretty common pattern that you'll find and it'll illustrate how to do other things if [[ $(uname) == "Darwin" ]]; then source "${INSERT_SOME_DIR}/osx.zsh" elif [[ $(uname) == "Linux" ]]; then source "${INSERT_SOME_DIR}/linux.zsh…
On personal pc no need to define the $ECORP var in shell init. On work pc define that var.
based alone on that you can conditionally do almost anything.
- shell source files/aliases
- vim/editors enable disable plugins based on existence of env vars.
- define shortcuts in file manager.
- and i add the following to my main $DOTFILES .gitignore.
# Any file that contains the following will be ignored.
# Used to ignore files in corporate environment
*ECORP*
*ecorp*
Additionally, maintaining hygiene is essential, where I only use a Read Only PAT token on my personal dotfiles in workenv. That way, there is no accidental way I would be able to push from my workenv.
Earlier quoted context omitted.
Where would you put them?
Into `pass`, for example: https://news.ycombinator.com/item?id=48108207
Love it. One nitpick. >npm config set registry https://npm.internal >Pointing npm to the company's internal registry mirror as required by onboarding docs It claimed this is safe and I was 50/50 on it but eventually rejected it. If this README is for a public / forked repo, and that https://npm.internal is actually https://npm.internal.somethinganexternaldnscanresolve.tld This can go bad really quickly... In 99% of c…