Hacker Newsnew | past | comments | ask | show | jobs | submit | adrianmonk's commentslogin

If their slogan isn't "The Sole of a New Machine", I'll be disappointed.

> Crawlers do not use the browser back button or browser history.

Couldn't you instrument the crawler's browser engine to observe whether (while crawling) the page does any behaviors that would result in back button hijacking? No back buttons have to be clicked.

You just have to watch whether the mousetrap is set. Since you know how mousetraps work, you don't have to grab the cheese.


Maybe this logic should be built into the "kill" command (or some other standard command). Given that this is the right way, it shouldn't be more tedious than the wrong way!

It could also monitor the target process and inform you immediately when it exits, saving you the trouble of using "ps" to confirm that the target is actually gone.


Different programs may take different amounts of time to cleanup and close. To know if a signal failed takes human judgment or heuristic. A program receiving a signal is even able to show a confirmation dialog for the user to save stuff, etc. before closing.


That's a valid point. Another example is SIGHUP, which will cause some programs to exit but other programs to reload their config file. In certain very specific cases, that could even cause harm.

So really what "kill" would be doing is automating a common procedure, which is different than taking responsibility for doing it correctly. It would need to be configurable.

I still think it would be a net benefit since right now incentives push people toward doing something the wrong way (even if they know better). But I can also see how it might give people a false sense of security or something along those lines.


> automating a common procedure

It's not common. If `kill` on its own (which does just SIGTERM) doesn't work, you're already in "something wrong is happening" territory, which is why:

>>> Given that this is the right way, it shouldn't be more tedious than the wrong way!

is also the wrong way to think about this. Trying a sequence of signals is not so much "the right way" as it is "the best way to handle a wrong situation". The right way is just `kill` on it's own. SIGTERM should always suffice. If it doesn't to the user's satisfaction for a nonjustifiable reason, then you can just `kill -9`, but this should be rare.

Trying a sequence of SIGINT, SIGHUP, and SIGABRT is technically better than SIGKILL but not really important unless you also want to write a bug report about the program's signal handling or fix it yourself. About SIGINT and SIGHUP, if SIGTERM doesn't work, it's unlikely that SIGINT or SIGHUP would. Likely, it would only be through oversight and the execution of default handlers.

`kill -9` is just like `rm -rf`. I wouldn't suggest that `rm` automatically run with `-r` or `-f` when `rm` on its own didn't work, and I wouldn't call automatically trying those flags "the right way".


Kill is not a command to kill processes, it is a misnomer. Kill is meant to send signals to processes.


Hopefully nobody thinks "I'll save even more if I get two!" and plugs them both into the same circuit.

Perhaps they could somehow detect each other and shut off.


I think that's the reason why the total allowed panel power is only 800W, any more than that and you have to get it properly installed. At least that's ~ the way it is in Austria, it's also pretty easy to check whether you have ~800 or way more hanging on off your balcony.


This part of the press release seems pretty crucial:

> Producers of consumer-grade routers that receive Conditional Approval from DoW or DHS can continue to receive FCC equipment authorizations.

In other words, foreign-made consumer routers are banned by default. But if you are a manufacturer, you can apply to get unbanned ("Conditional Approval").

In the FAQ (https://www.fcc.gov/faqs-recent-updates-fcc-covered-list-reg...), they even include guidance on how to apply: https://www.fcc.gov/sites/default/files/Guidance-for-Conditi...

If you (a manufacturer) apply, they want information regarding corporate location, jursidiction, and ownership. They want a bill of materials with country of origin and a justification for why any foreign-sourced components can't be domestic. They want information about who provides software and updates. And they want to hear your plan to increase US domestic manufacturing and progress toward that goal.

So, foreign-made consumer routers can still be sold, but they are going to look at them with a fine-tooth comb, and they are going to use FCC approval as leverage to try to increase domestic manufacturing.


> foreign-made consumer routers can still be sold, but they are going to look at them with a fine-tooth comb, and they are going to use FCC approval as leverage to try to increase domestic manufacturing

That is not what's going to happen. What's going to happen is that anyone coughing up payola to the current executive in chief's people will get approved, and anyone that doesn't will remain blocked. This practice is currently widespread, in the form of tariffs.


We're going to keep seeing this in all kinds of industries throughout the next three or so years: "Your products are banned or your country is tariffed, but if you pay enough in bribes, er I mean undergo our approval process, then you'll be exempt."


to me the greatest damage the trump admin is doing is bringing out corruption in the open.

if there's really one thing that destroys countries is corruption. being originally from a 3rd world country - I have seen it. now the US is heading towards the same path.

having worked in the IOT industry before - I can tell even domestic manufactures will be forced to pay bribes soon cloaked in 'state secrets' - there's already export laws etc - but now they will be forced to pay for compliance e.g maybe donating the president's vanity project.


Bonus points if the ‘approval’ process exempts them from liability if misused - and there is no actual checking done as part of approval.


You know that's exactly how it's going to be. There are two attributes of this administration that are just as prominent as corruption -- laziness and incompetence.


That descriptions already fits the payola model. It's almost never about directly handing money to a politician. That's illegal, so it's not worth doing when there's legal ways to do it. Instead, payola usually involves regulations requiring using some kind of product or certification, then the organizations that sell the product or perform the certification contribute to the politicians.

Also, the biggest benefactors of payola aren't the politicians, it's the rent seekers, that is the businesses already in place that want to prevent competition. Because of this, they usually directly contribute to the politicians that promise to restrict the path to doing business.

For example, if you want a newest-generation extremely-efficient air conditioner in the US, you won't be able to buy it and even if you could, you wouldn't be able to get anyone to install it. Any given model of air conditioners needs to be on an approved list to be sold in the US, and the installer needs to be on an approved list, too. This means that by the time an air conditioner makes it onto the list, it's already old. Also, installers can require you buy it from them, and almost all do, so by the time time an installer on the list has it for sale, it's even older than that. Ironically this is all enabled by the EPA, on the auspices that they are ensuring that it's energy inefficient, when in reality they are preserving the market for the older, more expensive, and inefficient models.


> That descriptions already fits the payola model.

The old payola model. This new model encompasses the old one and adds a neat layer of outright politician bribery on top.


> It's almost never about directly handing money to a politician. That's illegal

According to SCOTUS in Snyder v. United States, if the payment occurs after the official act, it's a perfectly legal "gratuity."


Trump made $4B last year. It's open and direct bribery at this point. He's said he plans to hide behind qualified immunity and pardons for people he pays (with tax money) to break the law on his behalf.

Dario (CEO of Anthropic) said the DoW contract violations and threats were direct retaliation for not paying Trump "campaign" money. Later, he was forced to apologize for speaking the truth.


> If you (a manufacturer) apply, they want information regarding corporate location, jursidiction, and ownership. They want a bill of materials with country of origin and a justification for why any foreign-sourced components can't be domestic. They want information about who provides software and updates. And they want to hear your plan to increase US domestic manufacturing and progress toward that goal.

Wow NGL this sounds great if you ignore the reality that it'll be used as a partisan backdoor to enriching the administration.


> but they are going to look at them with a fine-tooth comb

This comb likely is designed to extract loose $1M checks from the foreign manufacturers.


> So, foreign-made consumer routers can still be sold, but they are going to look at them with a fine-tooth comb, and they are going to use FCC approval as leverage to try to increase domestic manufacturing.

You're assuming a non-partisan technocratic process, which this administration has amply shown is neither capable nor willing to provide. This requirement becomes another opportunity for Pay-to-Play, either in cash or quid pro quo, to the government directly (see, e.g., NVidia and AMD export allowances) or to Trump's inner circle (see, e.g., crypto venture regulation, merger approvals).


This is the problem with erosion of norms. We’ve all known for decades that consumer routers have shit security. We’ve all known about the risk of implants or intentional backdoors in the supply chain. And now when the FCC appears to be finally doing something about it, there’s a massive cloud of mistrust hanging over the whole idea.


The FCC ain’t doing nothing about it. If anyone thinks they are, then I have an amazing US made router to sell them.


If they cared about security, US-made routers wouldn't be exempt.


The mistrust comes from those doing it, and the clearly corrupt ways they are operating. The maggot movement is basically rooted in a lot of very real frustrations from very real longstanding problems, but the only thing it offers as solutions is performative vice signalling.

People who care about the problems of digital security are not going to lean into the idea of simply banning devices based on where they were manufactured. Rather they would work at general standards and solutions to actually solve the problems - things like untying the markets for hardware/firmware/services, requiring firmware source escrow, mandating LAN protocols and controllers so every single IoT device isn't backhauling to its own mothership, and so on.

Likewise people who care about domestic manufacturing first and foremost are not going to champion applying steep blanket tariffs two decades after all of that industry has already left, or using regulatory agencies to shake down manufacturers for unrelated concessions.


> You're assuming a non-partisan technocratic process

No, of course I'm not assuming that. That's not the administration's pattern of behavior, so it would be a crazy assumption.

I agree it'll be abused. I just didn't feel it necessary to state the obvious.


I’m reading this as “tariffs didn’t work, so now we need different pain levers to wield against trading partners to bully them at the expense of consumers”.


> But if you are a manufacturer, you can apply to get unbanned ("Conditional Approval").

by giving daddy trump his taste, no doubt.


Any router made by a company that "donates" (bribes) to Trump's "ballroom" or other vanity projects will get approved. Irrespective of anything else. This is just another grift.


Their comment proposed something that would "be the answer here".

What does "here" mean? It's logical to expect "here" to refer to a scenario that includes cases like the one in the article. If it's some scenario that excludes cases like the one in the article, then it's not actually relevant to the discussion.

(Tangents are OK. It's just confusing if they're introduced with phrasing that makes them sound like they're not tangents.)


"here" in that comment is not referring to any specific scenario. It is referring to the problem discussed in the sentence immediately following it, that public prediction markets can shape the outcome of the events they are predicting.


It makes me think of the 1978 movie "The Wiz" starring Diana Ross, Michael Jackson, and Richard Pryor. Despite the big stars, it isn't generally regarded as a very good movie. Maybe updating "The Wizard of Oz" with disco music wasn't a good idea after all.


That movie was based on the stage musical, FWIW.


I actually like the concept behind it. It just doesn't have "this is going to be a success" vibes.


You can just add a second line to /etc/passwd with a different username but the same numerical uid. Like this:

    altroot:x:0:0:Alternative Root User:/:/bin/sh
Then, of course, run (as root) "passwd altroot" to set a password.

We used to do this all the time for users who needed root access to their own workstation. It allowed us to avoid telling them the common root password used on all the machines in the organization.

In your case, doing this might be beneficial in case there is a network problem because you'll have a way to log in as root locally.


Back in the day we would've just added our IP to the .rhosts file and no password would be required at all!

It does have me thinking about what versions of SSH would run on such an old OS. I'm sure there were versions available at one time... and since it's vulnerable to remote exploit anyways the version wouldn't really matter.


SSH v1 protocol would work; but it’s still considered insecure by SSH clients of the last two decades :-)


OK, now that you have this data, give me a "prefer safer routes" option in Google Maps navigation!

While you're at it, give me an option to avoid unprotected left turns and to avoid making a left turn across a busy road where cross traffic does not stop. (But only during heavy traffic; it's fine when nobody is on the road.) Not only are these more dangerous, they're also more stressful and they also introduce annoying variation into my travel time.


I think Lyft already does this for their driver navigation.


There's probably a strong survival advantage in convincing whoever is leading a meeting that it's time to adjourn.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: