Ah ok. Was confused. Cause that would have made the community edition mostly useless.

Maybe you mixed that up with the Tenant System in the enterprise Edition?

I do not think that this is correct. Otherwise multiple permission features that are part of the community branch would not make sense. Like “impersonate”.

Do you have a link to the part in the documentation?

As of now, i keep them basically for ever, but granularity gets less over time. (restic forget)

Before you go nuts about files you want to exculde the “churn” as you said it, go ahead and actually check how much space this actually takes up. Text and especially logs are highly compressible and will most likely end up taking up almost no space.

Be sure you backup everything you actually need, rather backup a file more then a file too less.

The charging cirtuit that also tries to guess the battery percentage can be the problem. The ‘guessed percentage’ will depending on the chip and programming go down even if you solder in a dc power supply. When it hits the 0% it will shutdown.

Thats the case for some smart phones.

Consumer Hardware has feature enterprise/datacenter Hardware does not have and the otherway around.

High End Consumer CPUs for example clock way higher and therefore have better single core performance, which can be a benefit.

Non ECC memory and overclocked memory like on Consumer Hardware is often faster, especially when you compare price to performance.

Especially when things like a minecraft server is not optimized for a 128-core CPU or even 32-core CPU.

My guess, auto updates for major versions is not good practice. Installations potentially corrupt and users come screaming to the project maintainers instead of searching the blame by themselfe.

forgejo defined the lifecycle for every version so just add a calendar entry for when the supports runs out and then update the 3 characters in the docker compose file.

netbird uses wireguard as vpn protocol

To my knowledge:

• File Versions only 30 days available.
• -> Everything older and deleted than 30 days gone.
• Slow and manual Restore Process
• -> Web downloads max. 500 GB manual selection.

B2 is data storage, Backblaze Personal is a service. 2 Completely different things.

You can share albums with other users, or even with a public link.

That is not what i have asked.

I doubt that this applies to files smaller than the pack size or a for example bitwise unique 17MB file would result in a (overly simplified) 16 MB and a 1 MB chunk or am i wrong here?

I use B2 for my restic Backup. Currently i have about 100GB stored there and it says i have about 100,000 files stored.

With the adjusted calculation of the blog you posted for 10TB of 50KB files, adjusted to the mean file size of my restic repository 10 TB of 1MB files:

Transaction fees: 10,000,000 / 10,000 x $0.004 = $4

My Laptop has a mean file size of about 16 MB per file on the local restic repository.

EDIT: Forgot a resume, i do not think you need to worry about it too much. But maybe verify the amount and type of data you want to backup and use calculators to calculate the real cost, also you can always test it by creating a test dataset and then do a backup and recovery scenario and then use this to derive an estimate.

As I said, when you know the exact path of a media item on the server then you can check if the item exists.

If you choose a none standard filepath its not an issue.

Should that be fixed yes.

Whats the scenario? A law firm could brute force check all media items on open jellyfin servers? Highly illegal to exploit something like this in a lot of jurisdiction. And would also not proof the existence of the media on the server, just a file named like it.

Mitigation? Just add another random letter in the docker-compose mount path.

Have you even read the issues and understood them?

Yes, those should be fixed, but unless you are worried about someone hijacking a video stream when you use a generic media path, there is not that much to worry about.

deleted by creator

7.0-rc7 is probably due to the 7.0 release early mid april. So the fix was in the mainline on 1st of April. The commit on 11th from GKH was probably due to the release.

I am not that familiar with the commit and release structure to get more into detail. But to me it clearly looks like the statement on copy.fail is correct, that the fix was in mainline on 1st of April.

From my point of view, I would suggest that maybe the communication downstream to the distros was not handled that well? But who would be to blaim? The researches that would need to communicate this issue to most existing distros? Linux maintainers? Distro maintainers?

Hard to say, without knowing the communication of the related mailinglists and disclousre etc.

Honestly, thats a really bad take. Yes obviously, you should not let attackers access the terminal, but there are linux servers that rely on multiuser operations, like Servers that are meant for terminal access, like HPC.

Then services get hosted via container these days, so even with rootless containers you get root access if you only get RCE on one service. And even if there are additional VMs for more isolation between host, you still get root on the whole VM.

Looking at the CVE on NIST,i found following commit which dates to 30.03

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5

The patches where proposed over a month ago and the patch to the kernel was commited on 1th of April.

Either the Vulnerability was not proper communicated to the distro maintainers or they were the ones sleeping.

This was probably executed as a responsible discllsure where clear timelines and release dates get communicated from the beginning.

I find it hard to blame the security team here when there was 1 month of time between first commited patch and release of the PoC.

I have q xyz Domain as my main Domain. And there are basically no issues here. But in 1 or 2 places i noticed that the domain gets blocked, a couple of free/open wifis or a couple of DNS servers. But nothing major imho.