Синхронизируем Obsidian быстро, безопасно, удобно и бесплатно
гайд по синхронизации obsidian vault через git с шифрованием через git-crypt и gpg (заметки хранятся на сервере в зашифрованном виде, локально обычный markdown )
Синхронизируем Obsidian быстро, безопасно, удобно и бесплатно
гайд по синхронизации obsidian vault через git с шифрованием через git-crypt и gpg (заметки хранятся на сервере в зашифрованном виде, локально обычный markdown )
#nix flakes and git smudge filters:
https://discourse.nixos.org/t/flakes-and-files-behind-git-smudge-filters/58446
TL;DR: Is there a flag like nix flake check --just-behave that makes it eat files behind git smudge filters? It’s already known that flakes don’t like files behind git smudge filters such as git lfs, git-crypt, git-annex, the list goes on… Some references: open issue: flakes: git-crypt is now broken · Issue #5260 · NixOS/nix · GitHub Yann Büchau :nixos:: "@[email protected] You cannot referen…" - Fosstodon Yann Büchau :nixos:: "It seems that in #nix flakes one still can't use …" -...
So turns out if you rename a directory previously encrypted by #gitcrypt, the git-crypt config obiously doesn't change on its own...
Long story short: A bunch of, thankfully, non-mission critical passwords and the certs where accessible publicly for about day in my #dotfiles repository
They were accessed by the random IP from Singapore I talked about before. Let's hope I don't get fired 😬
If you are using #gitcrypt to protect your git files and suddenly it throws 'libssl.so.1.1: cannot open shared object file' then your favorite distro has moved to #openssl3 and libssl.so.1.1 has been uninstalled
Short fix : download openssl version that contains the file and addit to your LD_LIBRARY_PATH
Shorter fix : use this script https://tinyurl.com/3zw4amjm
Thanks to StackOverflow and FLOSS community for the answer
https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory
CC @ubernauten
Meine (nicht-öffentliche) Nextcloud und bald bestimmt mehr ist auf (A)steroiden, cause proudly hosted by uberspace.de. (Steroide sind natürlich nur für Maschinen OK, und auch nur so lange, wie sie sich nicht gewerkschaftlich organisieren, wie bei Stanislav Lem.)
Außerdem nutze ich @writefreely, @WordPress, @Codeberg,@cryptpad,#searx, @mxlinux,@keepassxc,#vnc+#ssh,@git,#gittfs,#gitcrypt,@libreoffice,#clawsmail, @librewolf,@[email protected],@fdroidorg,@libretube,@AntennaPod,#opencamera,@anysoftkeyboard,#quickdic,#transportr,@torproject,@signalapp,#jitsi,@Tusky,#mgit,#markor,#PilfershushJammer,#fosswarn,#vlc,#doublecmd,#powershell,#autohotkey,#xca,#openssl,#zapp,@privacybrowser,#UntrackMe,@veracrypt,#AuthPass,@newpipe,#radiodroid,#edslite,#SecScanQR,#sqlitedbbrowser,#avnc,@k9mail,openstreetmap.org,inv.nadeko.net,u.V.m., überhaupt privat fast nur und im Job so viel wie geht #floss , im Netz und lokal.
–––
Warum FLOSS? U.A. deshalb:
KI – Macht – Ungleichheit. https://media.ccc.de/v/ce4743cc-50ad-4597-bcc8-58e1a7e53c20
Is git-crypt still the recommended utility for storing encrypted data in your repo? Seems unmaintained at the moment...
#Git #GitCrypt #GitHub #GitLab #SoftwareEngineering #DevOps #CodeRepository #Code #Software #SoftwareDevelopment #VCS #Encryption #CyberSecurity