Interests: News, Finance, Computer, Science, Tech, and Living

  • 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • Supply chain attacks also show one reason that using older software like Debian stable may be a better plan for things that matter. All new software versions need some time to be tested and vetted.

    It also shows the importance of security in depth. That less is more in terms of code dependencies and complexity. That knowing dependencies is as important as knowing your code.

    I would consider the xz incident to be a success. The supply chain attack was found pretty rapidly. We have already seen many of these and we will see more. Ones I remember off the top of my head include Linux Kernel, NodeJS, Python PyPI.

    I would not over blow this. Security is an ongoing activity and all security is porous.


  • My wife and I have used GnuCash for 20 years. We used Quicken before that. Like GnuCash way better since it is actually double entry accounting. The major limitation of GnuCash is that it is not concurrent. So to people cannot be modifying the ledger at the same time. Not sure about viewing. It can be SQL database backed though I have never used that functionality. The other place where FOSS stuff probably lags is integrations.

    Edit: Another area in which GnuCash is weak is basis tracking. Fine on accounting for gains and losses but for tracking the basis is limited. At least my version is. I am on 3.x which is the version in the repos of my near end of life Debian 10 distro and latest is 5.5. At least my version there is no way to show true returns either.






  • Yes but it does have some editing and metadata management features. Personal opinion is everyone should start with a photo manager and then only use another program if you need more. On Linux Shotwell is another photo manager and Digikam is cross platform. I know my wife uses just Shotwell. She has never needed more. I use Digikam because it is a little more powerful and flexible but less elegant. My wife is into photos… me not as much too.





  • Browsers are very complex and fast moving tech. This means expensive. This implies professional paid staff. Then comes how to raise money. The big companies have revenue streams. Smaller groups have to do it any way they can which is always compromising something.

    Mozilla too makes compromises… setting default search to places I would not use. Trying to offer a subscription set of services which is actually not a bad plan but is not exactly to the point. So I trust them more and want to see them succeed but they have challenges too.

    Some ways huge parts of tech relies on questionable income streams including the tracking, ad, and personal information broker business. Google of course but Mozilla is funded largely by Google as far as I know. Apple may get similar funding but larger. Microsoft even in Windows installs crapware from partners. So it is everywhere. HP laptops typically do too.


  • Thanks, I did not see that before.

    Other interesting thing is that about:config is disabled on mobile except maybe nightly. Wonder why?

    The other advantage of Brave is that it is more secure out of the box. From privacy point of view that should be better at blending in to the crowd depending on user base size. In Firefox I usually add an extension and configure it and some about:config settings. Somewhat minimal but probably quite unique.


  • I did not find any justification of why they arbitrarily did not considered Gecko browsers in privacyguides. They just made that statement. I am not surprised that certain chromium browsers are more secure simply because Google has a bigger budget, but I did not see any justification for it. Then again the EFF will say that Tor Browser is better then Brave so we can argue about these minor points forever.

    Then again none of that minor stuff matters to me. I care more about the goals of the organizations themselves and I am not convinced that any of the Chromium browsers take us down a sane path. So I will be staying with Firefox thank you very much.



  • ssh plus sshd is available already or can easily be installed on any Linux system. It can do many things: Remote terminal sessions and remote login (for admin for example), file transfer, directories can be mounted as shares too over ssh, remote execution, you can also even do tunneling, graphical application UI forwarding, and even implement VPNs via ssh. Every Linux admin knows about and uses ssh all the time.

    It is interesting a lot of people forget you can use any Linux box as a file server via SSH, in addition do a lot of other things. I also have an ssh app on my cell phone, and can just mount the file system their on Linux too. There are clients for SSH for Windows also.



  • Yes, you can sync between two on devices anywhere in the world as long as a connection path can be found.

    The downside of this is that both devices have to be on. If not on the LAN it may go though some unknown gateways too which makes me nervous (though it should be all encrypted). It can take some time too for the devices to find each other and then do the transfer (even on the LAN).

    Some people place syncthing on their NAS so it is the always on device. Also if you do not want your connection to go through other peoples bridges then you can disable that feature (and loose the global WAN transfer capability), or you can put up your own bridge in a VPS on the WAN.

    I am no expert on this. For me I use syncthing only sometimes and only on my LAN. Mostly I use SSH, Nextcloud, or Bitwarden Send myself. I’d like to play more with some of the other options though. Seafile or placing Send on my VPS for example seems interesting to me.



  • flatbield@beehaw.orgtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    10 months ago

    You get an IT staff that is MS and Windows certified, what sort of answer do you expect them to give? As far as IT staff where I worked, they often had issues with resolving Windows problems say nothing about Linux. Generally for Windows, I had to get to level 3 support before they knew anything. Even then I often had to tell them what needed to be done rather then them actually knowing. Some of this is lack of skill, some if it is under staffing, some of it is restrictive processes, and some organizational issues. You had to know how to work the system on one hand, and which issues just to not waste time on. Not saying they did not try hard, but without facilitation their results were often insufficient.

    That does not mean you cannot use Linux however. Just means the main IT group does not support. We had a separate group that ran the Linux compute cluster we used. I also typically always had a Linux VM on my workstation too to use FOSS tools. Not sure that would be allowed these days since IT has gotten nuts about security, and with that they have generally grabbed a lot of power regarding what can and cannot be done on “their” hardware and on “their” networks. You can also get exceptions to a lot of those rules if you can justify it and if your management is willing to run it up the flag pole. If not, your working for the wrong people.