524 karma · joined April 5, 2015
These blind (or "magic"; https://en.m.wikipedia.org/wiki/List_of_file_signatures) extractors can be handy is a very wide range of applications.
From firmware/device image hacking to reverse engineering to data recovery.
As someone who uses `binwalk` extensively in a professional setting, with tooling built around `binwalk`, it would be useful to see (a) how `unblob` would integrate and (b) if it could be a replacement or supplemental.
Cisco has owned an maintained ClamAV (and integrated it into their products) for a while.
He set a direction and it was executed, many layers of individuals were likely involved.
Note: I'm not a Musk fanboy, nor am I a hater. We can settle for relatively impartial.
> There's just no way for laypeople to evaluate the provenance of random QR codes.
Arguably, even seasoned veterans may have difficulty confirming the validity. Too often, it's a patchwork of random third parties before the order is completed.
> The restaurant industry often uses random third-party sites for their menus, so even that is a poor signal.
Which makes this all that worse, as it's contrary to all of the "verify" messaging we've been preaching from the security world.
But also, JS client-side validation is also client side, and therefore exposes the same amount of information to an adversary.
Either way, you need input validation on the backend.
Agreed. The ball is in Google's court. Consumers should (and clearly do) cast a vote of "no confidence" with their wallet.
So what's Google to even do?
* They could burn money and keep the offering afloat to "prove" they are serious (seems to be the case with Stadia).
* They can pivot/transition the offering (see Google Glass).
* Or they can use new offerings for R&D (and in some cases, like that of Stadia, be paid for that R&D), and then fold that technology/data somewhere else (see Wave) - this seems like the path most taken.
If we remember Google's core competencies, the revolving door of offerings as feeder into their larger services makes sense on paper, but I do agree that it's hurting consumer confidence and there is a hidden cost to that.
There are a lot of beneficial assets Netflix would bring to any potential buyer, especially media IP for an organization trying to become (or stay) relevant in that space.
But the potential move from AWS to Azure would be a huge case study for Microsoft.
Relatable. I rarely post or comment, as when I have something to contribute to the conversation I usually cannot (NDA, etc.). And for the times I could post, I don't really have anything of value to say; echoing into the void and all.
But then I do get value from the comment sections, oftentimes more than the original post/content.
So thank you to those who do comment and contribute!
This post is fairly high on the frontpage and seems to be suffering the consequences of interest. But a Slashdot/Sigh/Reddit/Hackernews clone in the federated space is awesome. Be sure to save for later.
I can smell the spamvertisement revenue!
But the link-relationship methodology is interesting (similar to something like PageRank through backlinks).
But it's not the methodology I'd have initially gravitated towards.
My first instinct would be relations based on subscription overlap. This seems like it should group commonalities based on the user interests. This may also have alleviated some of the SPAM issues.
Though it would have been interesting to see both approaches merged together.
But don't dismiss the merits of the idea. It's essential Risk Management[0], which is most certainly a relevant part of Information Security. Specifically, this is a form of Cost-Benefit Analysis (specifically, Qunatativie Risk Analysis[1]), a critical component in proper Risk Management; the reality is you cannot "fix" every issue.
Take a look at methods like Single Loss Expectancy[2] and Annualized Loss Expectancy[3]; you'll find that the Fight Club quote is very close to the real-world methodology. I cannot speak for the Automobile Insurance industry, but given Insurance is founded in Risk Management, it seems likely to be closer to reality than not.
[0] https://en.wikipedia.org/wiki/Risk_management
[1] https://csrc.nist.gov/csrc/media/publications/conference-pap...
[2] https://en.wikipedia.org/wiki/Single-loss_expectancy
[3] https://en.wikipedia.org/wiki/Annualized_loss_expectancy
The host ISP, the hostyoself.com ISP, the various routers, firewalls, networks between the two, and all the same for the end-user, any proxy servers on the path, etc. A lot of entities are hosting/enabling access to the content.
That's not to say they couldn't use the same approach to legally questionably or illegal content: If they have a proper complaint or takedown request, they stop forwarding to that content host.
I haven't looked at the code either. But the hosting seems to be handled in JavaScript. There are no required clients (though there does seem to be an optional one); this is all completed in the browser.
So you're not "uploading" content, you're providing the content to the client-side application so it can be shared through that same client-side solution.
This project, like many areas in technology (especially new or cutting-edge), are not well addressed in laws, regulations, or legal frameworks. The courts of the world have not provided much clarity either, but certainly have not provided any clarity on this particular project.
You did not reference your view in relation to a particular country or legal authority, but the site is hosted in the U.S. so that is the most relevant here.
The content is not hosted by hostyoself.com, it's hosted by the systems owned by the content sharer. The legal landscape has certainly shifted providing less coverage for user-generated (or uploaded) content but there are still some protections in place for solutions that do in fact host user content. But again, that's not the case here.
hostyoself.com is simply forwarding requests to the relevant destination. Not unlikely any other traffic routing or forwarding technology. In fact, the proxy comparison is particularly apt, and a solid defense.
Of course none of this absolves hostyoself.com from complete inaction. I could certainly see them compelled to cease forwarding requests to some destinations. But I do not see a clear path for hostyoself.com to be liable for the content a particular user is hosting. The user in question is the one in possession and performing the hosting/share of the content.
Of course... the courts are the ones who would decide in such a case.
> How often is someone looking over your shoulder when you type a password?
When I'm in the privacy of my own home? Rarely. When I'm using a mobile device (arguably where "unmasking" provides the most usability improvement) in public? All the time. No, random strangers are most likely not paying attention to your phone, but look around next time you go out there are cameras _everywhere_.
Even the helpful mobile keyboard feature that shows you the last entered character is a risk. Not to mention merely watching the interaction with the onscreen keyboard. However, both of those require a moderate amount of attention, versus just prominently displaying the full password unobstructed all at once on the screen.
You may not think those cameras matter, but let's be honest, many people have access to the data feed through those cameras. From the near-minimum-wage "security" guard (or loss prevention) employee to the corporate security teams storing the backed up footage.
Logging into your Hacker News account may present a low risk, but certainly, this could be catastrophic when logging into your bank account. It's one of the less acknowledged benefits of fingerprint readers and password managers (combined). Unmasking that password entered by the password manager would defeat this entirely.
Let it be an option, but don't do this by default.
That said, I would at least agree that this post is has a lack of any real substance and is low effort. Generally speaking, most people are familiar with Firefox, which holds even more accurate here on _Hacker News_. I would speculate many are also familiar with the initial "import" process offered by Firefox and competing browsers alike. So I am unsure of the goal of this post. I wouldn't go so far as to call it outright _spam_, but I do not think it warrants frontpage presence either.
maxScore = 0;
setInterval( function() {
if (score > maxScore) {
maxScore = score;
}
if (distance(hero.y, hero.x, ennemi.y, ennemi.x) < (vitesseEnnemi * 15 + 30)) {
hero.y += (hero.y - ennemi.y) * speedLimit / distance(hero.y, hero.x, ennemi.y, ennemi.x);
hero.x += (hero.x - ennemi.x) * speedLimit / distance(hero.y, hero.x, ennemi.y, ennemi.x);
}
if (spawn > PowerUpspawnRate) {
hero.y += (powerUp.y - hero.y) * speedLimit / distance(hero.y, hero.x, powerUp.y, powerUp.x);
hero.x += (powerUp.x - hero.x) * speedLimit/ distance(hero.y, hero.x, powerUp.y, powerUp.x);
} else {
hero.y += (reward.y - hero.y) * speedLimit / distance(hero.y, hero.x, reward.y, reward.x);
hero.x += (reward.x - hero.x) * speedLimit/ distance(hero.y, hero.x, reward.y, reward.x);
}
}, 25);
It's oddly fun to watch the little green guy pull off some sick dekes.If you want your green guy to flat-out avoid the enemy, just wrap the second set of conditions there in an else block.
edit: Formatting for readability/copy+paste