bpfrh

They are but not as efficient and so most people don't bother(that I know of).

Depending on if he lives in a apartment some country/cities have laws against doing any work in the appartment that impacts the outside without permission from the house owner.

E.g. you can buy a heatpump but you can't drill the hole in the outer wall.

In germany and austria most if not all windows also either open fully to one side or basically bend inwards so you can't install the ac units you install directly into the windows[1].

[1]https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2F...

edit: qualified the law statement

Thanks, posted a comment with the link.

There is a more detailed statement in the chrome CCADB Public group:

https://groups.google.com/a/ccadb.org/g/public/c/29CRLOPM6OM...

Thanks, I wanted to submit that url earlier but thought this one provided more information.

I should have checked if it was already submitted.

They have a default web ui at least for the last 8 years.

Upgrading with non custom builds is a pain point as is removes the installed packages, which can lead to issues such as your remote router suddenly having no vpn connection.

That being said, I now prefer openwrt compatible routers as debugging and customization is soooo much easier.

Doesn't modern electronics require massive shielding?

e.g. you would need too much shielding and would go over the 1 gram restriction.

That kinda depends on your licencing agreement:

https://en.wikipedia.org/wiki/ARM_architecture_family#Licens...

You can either licence a IP Core block(Core, gpu,etc) to embedd in your device, our you can buy an architect licence and design your own cores as long as they comply with the arm architecture.

AFAIK the IP is actually buildable cores which arm get's by partnering with companies to get it right, e.g. there is not that much difference between them fully building them in house and selling them vs. letting partners build them(for the end user).

I agree with your firs point and I think that is the crux of the matter, but I goes a bit farther than only developed under a specific licence from Arm.

Arm seems to also have given Nuvia access to the technology behind their own cortex cores.

Arm sees anything that nuvia developed as a derivate of their IP and therefore subject to the agreed upon licencing term.

I think that removes some of the weird feeling around the idea of just sharing patents and entering a licensing agreement, but even if arm only gave patent(licences) rights, it would still mean that all of the products of nuvia would be based on that ip.

I don't think your example is applicable, in your situation the product is not a derivate of visual studio, but visual studio is just a tool.

I think this fits the situation better:

You want to write a custom video decoder and because you are small and new a bigger company allows you to use their super fast video decoder and some of their patents if you only sell your software for ios smartphones for a good price.

If you breach any of this, your licence to use their encoder as a base for your products expires and you can't use any of their patents.

Agreed, I think on your last point ARM is also trying for a fast case/settlement as they are in a difficult position:

They don't want to have a long fight expensive fight with qualcom and make other arm companies uneasy about investing in the arm platform.

They also don't want to open the door to have companies buy their IP for "cheap" by buying smaller companies with special arm licences instead of directly negotiating with them.

I don't think it is weird.

Imagine you buy a non profit which has a special windows licence and then you use that licence for all your for profit windows devices, I don't think that that would be possible.

AFAIK ARM gave Nuvia a licence to use their ip (and access to their IP) for a specific market.

imho Qualcom has the right to use the nuvia ip as laid out in the licence agreement, but not for markets where no licence exists e.g. laptops.

Edit: removed some nonsensical text

The argument is that Nuvia got a licence for server usage and development support from arm to develop custom arm processors.

Qualcom now wants to use technology developt under a specific licence agreement in use cases not covered in that licence agreement, because they have general licence agreement with arm.

The question is:

Does the general licence agreement from qualcom override the specific licence agreement between Nuvia and arm for this specific technology.

I found some sources which partially explains this:

https://www.ft.com/content/5535ce39-ab22-497a-a8d6-52a690d1b...

https://www.cnbc.com/2022/09/01/why-arms-lawsuit-against-qua...

(...Nuvia, a startup founded by former Apple and Google engineers, was developing a server chip with custom cores under an architecture license. It also had access to Arm’s core designs....)

From point 6a:

Struggles at Intel. Lasertec’s EUV mask inspection effort is Intel’s baby, which it sponsored with $300-500MM in advances >5 years ago as its “founding” customer after failing to convince KLA. Intel’s mask group is trying to save face and cover up that its investment has been a debacle, giving it supplier prizes for public PR while “blowing up” on Lasertec behind the scenes, according to multiple research sources

Intel currently has issues with marketshare from amd and arm maybe they don't want to post that loss and setback for some targets?

Edit: spelling

There were protests against the coal industry, but on the mining side. The first that I found was in 2008 against mining of brown coal[1].

I would argue that there are less targeted protest against coal because protest concerning climate change include being against using fossil fuels which includes brown coal.

Nuclear is a special case, as accidents have a higher risk with a bigger area affected, so there will be more people that are concerned about it(same as with having coal mined next door vs. having a power plant somewhere in your region).

[1] https://de.wikipedia.org/wiki/Tagebau_Garzweiler#Protest_und...

I'm curious on how you did the websocket part?

I thought php has a per request execution model.

Because there is unfortunately no "linux"

Sure, there is the linux kernel in different version and patch states, but everything else including on how to manage software(package manager) is something the distribution decides.

As there is no standard and for historic reasons, different distributions choose different package managers.

If you want to support linux you normally decide on which distribution you want to support and more importantly which version of them.

The big ones out there are probably ubuntu, fedora and arch.

Then you can decide between building packages for the different package managers or just build a static/dynamic binary that works on the distros and runs on them.

You can also use flatpack and snap which makes it easier to support different versions of the same distribution, but you run in a sandbox and afaik lower level access to the graphic stack(games) is a mess.

Yeah it is a mess, but at least most distributions have the same service/bootup manager

I would argue that if they bought a more expensive product because of the label "made in usa" then they lost the difference between what they would have paid for the cheaper product and what they paid for the product labelled "made in usa".

What about exporting to mathml?

https://developer.mozilla.org/en-US/docs/Web/MathML

afaik some free vpn providers use your own connection to offer residential ips for scrapping services or other vpn users.

I know I read a article about one where they at least routed some other traffic through the vpn app, but I can't find the article anymore.

nvm read the wrong message

>This take is bordering on not even wrong territory. The point of port knocking isn't to increase entropy of your password or authentication keys per se, it is to control who can send packets to your SSH daemon, either to limit the noise in your logs or to mitigate an RCE in the SSH daemon. The vast majority of potential attackers in the real world are off-path and aren't going to be in a position to observe someone's port-knocking sequence.

If you read my full sentence in the context it stands, I argue that authorizing access to your openssh instance is done by sending an authentication code in cleartext.

It does not matter if that authentication code is in the form of bits, tcp pakets, colors or horoscopes as long as your transmit that in clear text it is in fact no a secure mechanism.

Yeah but now you basically have to always run an vpn that only exists between your server and your client, because otherwise your clear text authentication code is visible and at that point just use wireguard and make a 1-1 tunnel only for ssh with no known attacks, even if the attacker is in the same network.

Yes a vpn that has no known reliably attack vector is definitely better than a protocol with a known working attack vector

That other programm is knockd, which needs to listen to all traffic and look for the specified packets.

Granted, that program is really small and could be easily audited, but that same time could have been spent on trying apparmor/seclinux + a good vpn and 2fa

>It seems that we now have a clear proof that it's actually helping versus certain type of attacks (including source-code supply chain attacks).

So would have a vpn or using a bastion host with a custom non standard ssh implementation...

At some point you have to make the choice to not implement a security measure and I would argue that should stop at vpn+standard software for secure access.

If you are a bigger company, probably add SSO and network segmentation with bastion hosts and good logging.

Port Knocking doesn't add any security benefit in the sense that there are known non avoidable security risk aka your transmit your password(knocking) in clear text over the network.

You also add another program with potential vulnerabilities, and as port knocking is not as popular as e.g. sshd, wireguard, maybe it gets less scrutiny and it leads to a supply chain attack?

Security measures are also not free in the sense that somebody has to distribute them and keep the configuration up to date, even if that person is you, that means syncing that connect-to-server-script and keeping it in a secure location on your devices.

sudo apt-get update?

thanks for fixing and explaining that, I thought '' would work and forgot about escaping characters.

thanks!

This version looks nice and short, any thoughts on prober error reporting to the end user?

My version has more feedback for the user which was important because the user was somebody not familiar with linux/bash, but even my version "swallows" errors.

Good catch with spectacle, I thought I fixed that already.

Why did you remove the -f parameter?

I use the same script as Dibby053, copied from stackoverflow but with some tweaks to work on kde,gnome and wayland as well as x11 and with some notifications on what state it is in.

I didn't test the x11/wayland check yet, but feel free to use it and report back.

  #!/bin/bash 
  # Dependencies: tesseract-ocr imagemagick 
  # on gnome: gnome-screenshot 
  # on kde: spectacle
  # on x11: xsel
  # on wayland: wl-clipboard

  die(){
  notify-send "$1"
  exit 1
  }
  cleanup(){
  [[ -n $1 ]] &&  rm -rf "$1"
  }

  SCR_IMG=$(mktemp)  || die "failed to take screenshot"

  # shellcheck disable=SC2064
  trap "cleanup '$SCR_IMG'" EXIT

  notify-send "Select the area of the text" 
  if  which "spectacle" &> /dev/null
  then
    spectacle -r -o "$SCR_IMG.png" || die "failed to take screenshot"
  else
    gnome-screenshot -a -f "$SCR_IMG.png" || die "failed to take screenshot"
  fi

  # increase image quality with option -q from default 75 to 100
  mogrify -modulate 100,0 -resize 400% "$SCR_IMG.png"  || die "failed to convert image"
  #should increase detection rate

  tesseract "$SCR_IMG.png" "$SCR_IMG" &> /dev/null || die "failed to extract text"
  if [ "$XDG_SESSION_TYPE" == "wayland" ]
  then 
  wl-copy < "$SCR_IMG.txt" || die "failed to copy text to clipboard"
  else
  xsel -b -i  < "$SCR_IMG.txt" || die "failed to copy text to clipboard"
  fi
  notify-send "Text extracted"
  exit

edit:

Formatting

The last point can be mitigated by a hardware based security key(nitrokey,yubikey,etc).

Key would then by not on your device so extraction would be difficult or impossible.

You would need to touch the key to grant the sign request which would prevent any signing without you noticing.