somethingsomethingidk @ somethingsomethingidk @lemmy.world

Posts

3

Comments

116

Joined

2 yr. ago

Was thinking "Oh shit now I have to become vegan", but the article is paywalled so I didn't have to go on the guilt trip.

Yeah you're right, it's time for bed lol

The default start timeout is disabled by default for oneshot.

You could try setting TimeoutStopSec="infinity" for the service. There may be a default timeout for services and its killing rclone before it can finish because the oneshot type is considered "starting" until the program exits.

Can you share your service file?

However, to exploit the flaw requires a "a time-based blind approach" on the part of attackers to extract database information, which is "an intricate, yet frequently successful method to obtain information from a database when exploiting SQL Injection vulnerabilities," according to Wordfence.

I wouldn't call that intricate. It's pretty standard to try it since you get immidiate feedback that you can inject sql statements.

I haven't yet! Today I did a kernel update with it, I was kind of hoping something would go wrong so I would have a bug to report. But nope. Everything worked flawlessly. I'm not really sure how to break it but I'm going to try (in a vm lol)

Yeah pretty much, but it's wayyyy faster. There's times where it feels like dnf is hanging trying to download metadata that's 25KB. I have 1Gb down and it takes like 2 minutes, its ridiculous. I know in the grand scheme of things I'm being petty. But it's frustrating when the metadata step takes longer than downloading 500MB of packages lol

I've been using dnf5 for a few weeks now. I never want to go back. If you use fedora, seriously consider checking it out. The only thing I'm missing is the provides subcommand.

Just to offer the other perspective. I started with podman years ago. I knew very little about containers and I would say it made the learbing curve a lot steeper. Most guides and README's use docker and when things didnt work I had to figure out if it was networking, selinux, rootless, not having the docker daemon, etc... without understanding fully what those things were because I didn't know docker. But when I started running stuff on kubernetes, it was really easy. Pods in podman are isomorphic to kubernetes pods. I think the pain was worth it, but it was definitely not easy at the time. Documentation, guides, and networking have improved since then, so it may not be as big of a deal now

I think librewolf scrubs most of that stuff out. I'm basing that off of using burpsuite's proxy server though. On vanilla firefox it captures so much crap going out. I havent tried with wireshark though.

Quadlets with podman have completely replaced compose files for me. I use the kuberentes configs. Then I run a tailscale container in the pod and BAM, all of my computers can access that service without have to expose any ports.

Then I have an ansible playbook to log in to the host and start a detached tmux session so my user systemd services keep running. Its all rootless, and just so dang easy.

Is that a 32 bit cpu?

If you run in distrobox you should not have issues with dependencies

For every sever install I've had, flatpak defaults to the system install which requires a password. You have to explicity pass the --user flag.

I'm not sure how to make it the default

I'm surprised it booted lol

I think nmcli is the easier way to go but this article from redhat has what your looking for in 6.4

Can you be a little more specific? Does the installer not launch?

You could try dmesg -w in a terminal before you start firfox and see if any messages come through.

Can you still access the internet with another program?

This could be a firefox issue, and not a flatoak issue as I assumed. Do you have another version of firefox on the system? If so what version?

The only thing that came up was some memory allocation/cgroup/.slice stuff for the container.

I'm not on that network anymore, and the problem is gone. So I cant reproduce.

Maybe I should have run wireshark?

The card is Realtek. I found an askubuntu thread where all flatpak commands were hanging, and their solution was to disable the nic.

This has only happened on this network. I didnt mention at first because I didnt think it mattered, but I'm visiting someone and moved networks.

The instant I take the dev down, the browsers pop up. I would bet money that when I go to my home net everything will work.

The flatseal angle didnt work either. The only reference is names on system bus.