The funny part about the removal of networking from the default #keepassxc package on #debian, is that they did it for "security" reasons, without thinking that the MOST INSECURE way to transfer a #password to your #browser is via the CLIPBOARD. Absolutely every running app or service can read the clipboard! And yet, that's the default way they expect users to do it now!
@keepassxc Are there any issues with your Patreon account? My yearly support package is not working anymore and the money has been charged back. All tries to recover it failed and it does not seem to be a Patreon issue. It more seems like the support packages of the KeePassXC project have been removed completely. 😅
Wenn der Package-Maintainer die Software die er packertiert selber nicht nutzt... Ich hab schon wieder massive Kopfschmerzen...
"...schreibt Klode, dass er die [...] diese Funktionen entfernt. Diese dienten vermutlich dem Nachladen eines favicon einer Webseite, meint der Maintainer. Er gehe davon aus, dass die meisten Leute nicht wollten, dass ihre Passwort-Manager irgendwohin verbinden, wovon sie nichts wüssten."
Schade das der Maintainer des Debian-Paketes nicht ansatzweise die Funktionalität eines Passwortmanagers verstanden hat. Meiner Meinung nach missbraucht hier ein Paketbetreuer seine Kompetenzen. Letzlich schadet er mit seiner Vorgehensweise Debian insgesamt als Linuxdistribution.
Who should be software packaging is a tough problem, I can see the value in #linux distros pushing for better changes downstream, encouraging upstream to change (double click in #KDE) but then I see cases like KeepassXC where the Debian package is now by default broken, actively damaging the reputation of upstream but then I remember #XZ where upstream was left unchecked and hid bad code in plain sight and I go back around in a circle.
Yes, I find reporting to downstream packagers (a.k.a. distributors) extremely relevant! When your favorite #SoftwareCenter or #PackageManager is all for linking to upstream, but not to those who directly affect your package in a supply chain, as a result, tops like in #KeePassXC get all the pinecones: there is no enthusiasm in an average user to link back those issues to downstream, not with the p(l)ain text and how derivatives are communicated anyway... :blobcat_flop_woozy:
The whole #KeePassXC#Debian thing is kinda giving me second thoughts wrt. the whole #Linux distro and #opensource packaging thing in general. My understanding of the implied agreement between me as a dev and a distro's package maintainer is: the maintainer, to the best of their ability, tries to make my software work "as intended". In return, they get to publish it under my software's name.
That's clearly not how Debian views things. And I can't accept distros publishing broken sw w/ my name.
If you run #KeePassXC, there is an option to minimize to system tray on close, and setting this option means you won't need to keep a window open in the background for your browser integrations to keep working.
Ein Argument mehr, um @keepassxc endlich auch in der Firma einzusetzen. Des öfteren höre ich von ihnen, dass es anscheinend zu "kompliziert" und "umständlich" sei.
»Einträge zwischen KeePassXC-Dateien kopieren:
Das Übertragen von Schlüsseleinträgen zwischen zwei KeePass-Dateien ist nicht offensichtlich, funktioniert aber.«
– von @ralfhersel auf @gnulinux