Dirk

joined 2 years ago
[–] Dirk@lemmy.ml 2 points 2 years ago (1 children)

It’s a lork!

[–] Dirk@lemmy.ml 17 points 2 years ago (1 children)

Especially not one I have to "subscribe" to.

The whole idea is just ridiculously stupid.

[–] Dirk@lemmy.ml 4 points 2 years ago

So, you found out how propaganda works.

[–] Dirk@lemmy.ml 2 points 2 years ago
  • Do you use bash? If not, which one do you use? zsh, fish? Why do you do it?
  • Do you write #!/bin/bash or #!/bin/sh? Do you write fish exclusive scripts?

I use bash, and I use #!/bin/bash for my scripts. Some are POSIX compliant, some have bashisms. But I really don't care about bashisms, since I explicitly set the bash as interpreter. So no, no fish exclusive scripts, but some "bash exclusive" scripts. Since fish is aimed towards being used as interactive shell I don't see a real reason to use it as interpreter for scripts anyways.

  • Do you have two folders, one for proven commands and one for experimental?
  • Do you publish/ share those commands?
  • Do you sync the folder between your server and your workstation?

I have my scripts in $HOME/.scripts and softlink them from a directory in $PATH. Some of the scripts are versioned using Git, but the repository is private and I do not plan sharing them because the repoand the scripts scripts contain some not-tho-share information and mostly are simply not useful outside my carefully crafted and specific environment. If I want to share a script, I do it individually or make a proper public Git repository for it.

Since my server(s) and my workstations have different use cases I do not share any configuration between them. I share some configuration between different workstations, though. My dotfiles repository is mainly there for me to keep track of changes in my dotfiles.

is it bad practice to create a handful of commands

It becomes bad practice if it is against your personal or corporate guidelines regarding best practices. While it is not particularly bad or insecure, etc. to create bash scripts containing a single command, maybe use an alias instead. The $1 is automatically the first parameter after typing the alias in the shell.

alias podup="podman compose up -d"
alias poddown="podman compose down"
alias podlog="podman logs -f --tail 20"

Not quite sure about the podman syntax, if podman exec /bin/sh -it "$1" also works, you can use alias podenter="podman exec /bin/sh -it, Otherwise a simple function would do the trick.

[–] Dirk@lemmy.ml 35 points 2 years ago (1 children)

Absolutely!

I don't know for other countries but here in Germany the employer - by law - has to provide the employee with everything the employee needs to do the job he's hired for.

I boldly assume this is the case in most countries.

[–] Dirk@lemmy.ml 9 points 2 years ago (1 children)

#729fcf

It's part of the Tango color palette.

[–] Dirk@lemmy.ml 178 points 2 years ago (4 children)

My friend works for a company which requires her to use Microsoft specific application

So the company needs to provide said friend with all the needed software.

[–] Dirk@lemmy.ml 3 points 2 years ago

Ladies and gentlemen, we have a winner!

[–] Dirk@lemmy.ml 6 points 2 years ago

Temporary workaround applications/scripts become de-facto standards sounds familiar. They disabled loading script files in Powershell but you can still copy&paste the file's content ...

People have no idea how absurd IT in corporations is.

[–] Dirk@lemmy.ml 9 points 2 years ago (1 children)

That make the badges NFC tags but without actual NFC ...

At least they had the code not in direct sight on their desk.

[–] Dirk@lemmy.ml 7 points 2 years ago* (last edited 2 years ago) (1 children)

Big international corporate, IT security hired by personal connections instead of skill, IT security never worked in daily business.

The fun thing is, that they refer to NIST guidelines. Which is even funnier because NIST says 12 digits are enough, user-generated 8 digits are fine, no complexity rules, and password changes only "when necessary" (i.e. security breaches).

https://sprinto.com/blog/nist-password-guidelines ff.

[–] Dirk@lemmy.ml 8 points 2 years ago

I've seen plenty of solutions. Sticky notes, a simple text file. External tools like barcode scanners. Using all letters and just 1! at the end (not that this is less secure on technical level than a completely random string, but it's easier to bruteforce - theoretically), etc. Some people use KeePass (with a stupid 5 letter password).

view more: ‹ prev next ›