[-] Ooops@feddit.org 3 points 5 hours ago* (last edited 5 hours ago)

I would also like to know how a large, expensive, relatively cumbersome, vehicle can possibly defend itself against hordes of cheap, mass produced flying explosives.

Soft kill systems (e.g. MUSS2.0), hard kill systems (Trophy, Strike Shield), independent remote-controlled weapon stations with anti-air capabilities (KNDS' Leopard 2-A-RC3.0 demonstrator for example came with one with a 30x113mm calibre).

(Bonus points for the smaller profile and the lower weight at the same or better protection level enabled by using remote turrets...)

The war in Ukraine is more defined by the lack of high-tech to neutralize drones (vehicles and air-defense being old -or available in very small numbers-, air-defense in Russia also not even close to performing to the standards they should on paper) than by the drones themselves. Future military planning will be more defined by adding those anti-drone capabilities already existing but not yet widely used than by mass spammed cheap drones themselves.

(For reference: Maybe you remember the Bayraktar hype in the beginning days of Russia's invasion... and then it just died quickly and silently. Because the actual factor was not the drone itself but the initial failure to close the gap exploited by the drone. And then Russia adapted by moving air-defense capable of handling those drones closer.)

[-] Ooops@feddit.org 6 points 6 hours ago* (last edited 6 hours ago)

Yes, the system expects regular updating. But Arch is entirely pragmatic. What has enough popularity and a mainainer to do the work will be kept in the repositories, even more if you include the AUR (also stuff moving between them when popularity and/or demand of packages changes). And because it is constantly moving on with new packages a lot is kept in parallel: There are a lot of packages in the repos in different versions, one being cutting edge, one being the lower version dependency for other packages not upgraded yet.

For reference: Yes, Arch for example expected you to update to the new open source NVIDIA drivers the day NVIDIA dropped the Volta, Pascal and Maxwell cards (GTX 1080 and below). But at the same moment the nvidia-580xx driver was introduced to the AUR, including explicitly being supported officially still. And the same happened every time a set of hardware got dropped (nvidia-470, nvidia-390, nividia-340), still kept unofficially for legacy reasons as long as it's technically feasible. So I can in fact still run graphics cards from 2006 20 years later...

Or for another example: Yes, Arch runs kernel 7.0.12 right now and updates the kernel on a weekly basis. Yet it also has the LTS version 6.18 (guaranteed to get support until end of 2028 upstream) fully supported in the repos. And again, including the AUR I can still run the oldest still officially supported (until end of this year) long-term-support Linux kernel 5.10.

And those are basically the most extreme examples in terms of losing support, one being the constantly developed core of the whole system, the other on proprietary drivers of a private company. Otherwise the amount of 1990s tech still support by Linux is actually insane.


Written on an ancient toaster (AMD FX series from 2011, gtx750ti from 2014, non-EFI motherboard) running Arch... which nowadays runs -given: older- games with better performance than years ago, because "the newest stuff" does introduce constant improvements and optimisation instead of new drains on your ressources like you are used to because they want you to buy new stuff.

[-] Ooops@feddit.org 2 points 6 hours ago

Also both Ukraine and Russia currently have some really strong air defence systems right now

Ukraine's strongest air defense is new systems in very low amounts and short supply, Russia's air defense is constantly failing to meet even a fraction of the capabilities they should have on paper.

In exercise with Ukraine NATO soldiers showed that they have serious issues dealing with drones.

But there is a massive difference between "the future of war is cheap mass produced drones" and "the future of war is closing the gap that cheap mass produced drones like to exploit". The 'but tanks are obsolete"-opinion is very popular with clueless people arguing the former.

[-] Ooops@feddit.org 12 points 9 hours ago* (last edited 9 hours ago)

Tanks won't be dead until there is another system that can fullfil it's role. It's easy as that.

Everything else is just adaption to changing threat environments while doing it's job on the battle field. Which specifically means more active defenses over passive armor, so soft- and hard-kill APS and probably an highly-automated small calibre remote weapon station.

Also, no matter how hard people try to delude themselves: The war in Ukraine is NOT a modern war shaping future combat. It's primarily characterised by obsolete static and trench warfare with both sides severely lacking capable air defense and experience in proper combined arms warfare. Then Russia aggrevates that situation even further as "We can't compete on the high-tech end of things so we drag everyone down to our level via a massive electronic warfare campaign" is part of their main strategy since the cold war.

That's the reason drones are so successful there, because they perfectly exploit an existing gap of lacking air defenses and a very taxing environment that benefits cheap mass spam over electronically impaired high-precsion tech. That's also the reason the Ukrainian side learning and adapting more quickly will win this.

The actual aspect of this war shaping future combat is detailed information on how to not make the same mistakes and close the existing gap cheap drones so perfectly fit into. So no, the tank isn't even close to obsolete. The next generation will show APS alongside limited in-build anti-air capabilities (small calibre gun against small drones probably alongside a few missiles that can double against out of range/LOS ground targets) and be accompanied by more dedicated anti-air assets once again (see: how those old German Gepards that were designed for that support role back then performed in Ukraine against drones half a century more modern)... and by IFVs nearly as well protected and basically being their flanking protection against infantry/ATGMs (see: active and passive protection levels of modern IFVs and their precisely timed burst-capable auto-guns - basically oversized battle field shotguns to clear the flanks off mobile but fragile threats).

[-] Ooops@feddit.org 1 points 10 hours ago* (last edited 9 hours ago)

Sure, if you simplify actual reality ad absurdum your strawman "suddenly" looks different 😂

In reality you can be for age restrictions yet acknowledge that the planned implementation is pure bullshit and obviously not meant to work and just a pretense for yet another surveilance escalation. But that would require actual thought and arguments instead of treating everything with polemics usually reserved for the blind loyality in team sports, so this probably goes over your head.

[-] Ooops@feddit.org 7 points 1 day ago

Right-wing populist and neo-fascist won't close one of the main pipelines for right-wing and fascist recruitment? How surprising... 🥱

[-] Ooops@feddit.org 5 points 1 day ago

Das wäre in der Tat ein super Deal

...für Atomkraft-Verhältnisse zumindest. Aber du must sowohl bei Bauzeit als auch bei Kosten wohl eher nochmal 'nen Faktor von 2-3 einrechnen.

[-] Ooops@feddit.org 6 points 1 day ago

Selbes Problem: dafür müssten sie ihr Hirn wieder einschalten.

Absolut niemand hat heutzutage das Problem, dass ihm Informationen fehlen. Am Willen, ihm gegebene Informationen auch zur Kenntnis zu nehmen oder gar nach ihnen zu handeln, hapert es jedoch.

[-] Ooops@feddit.org 16 points 1 day ago

Das halte ich für eine Falschmeldung. In der Union sorgt sicher nicht die menschenfeindliche Äußerung für Entsetzen, sondern nur, dass sie bekannt wurde und Konsequenzen hat.

Und ich fürchte sogar, selbst bei den Konsequenzen wägen sie in Wahrheit die negativen Reaktionen gegen die dadurch höhere Attraktivität für Nazis gegeneinander ab.

[-] Ooops@feddit.org 6 points 1 day ago

Sobald der Wähler anfängt, sein Hirn zu benutzen und nicht immer und immer wieder die selben bekannterweise korrupten Menschenfeinde wählt. Also wohl nie...

[-] Ooops@feddit.org 5 points 1 day ago* (last edited 1 day ago)

Well... People finding and disclosing security flaws are often much closer to hackers than what happened with the AUR.

Calling people adopting outdated and orphanded packages hackers is like calling the guy that finds a banknote on the ground a bankrobber.

[-] Ooops@feddit.org 31 points 2 days ago

The term "hacked" seem to have lost all meaning...

31
submitted 2 weeks ago by Ooops@feddit.org to c/unixporn@lemmy.world

26
submitted 2 months ago* (last edited 2 months ago) by Ooops@feddit.org to c/selfhosted@lemmy.world

As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

So a (very simplified) nginx server-block that looks like this:

# serve stuff internally (without a hostname) via http
server {
	listen 80 default_server;
	http2 on;
	server_name _; 
	location / {
		proxy_pass http://localhost:5555/;
                \# that's where all actual stuff is located
	}
}
# reroute http traffic with hostname to https
server {
	listen 80;
	http2 on;
	server_name server_a.bla;
	location / {
		return 301 https://$host$request_uri;
	}
}
server {
	listen 443 ssl default_server;
	http2 on;
	server_name server_a.bla;
   	ssl_certificate     A_fullchain.pem;
    	ssl_certificate_key A_privkey.pem;
	location / {
		proxy_pass http://localhost:5555/;
	}
}
#actual content here...
server {
	listen 5555;
	http2 on;
    	root /srv/http;
	location / {
        	index index.html;
   	} 
    	location = /page1 {
		return 301 page1.html;
	}
    	location = /page2 {
		return 301 page2.html;
	}
        #reverse proxy for an example webdav server 
	location /dav/ {
		proxy_pass        http://localhost:6666/;
	}
}

Which works well.

And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

So long story short...

How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?

view more: next ›

Ooops

0 post score
0 comment score
joined 2 years ago