HN user

joelesler

147 karma
Posts18
Comments35
View on HN

So let's say a startup was funded through a Chase bank account and now everyone on this thread is saying "yeah don't do that"...

Let's say that a friend of mine has a startup funded account at Chase, and where should they go?

As the former community manager for ClamAV, there could have been some work done here to correct the situation and make both parties happy. I know ClamAV doesn't want to see third party utilities go away, and it's beneficial to the community for them to exist. Trolls exist, but there are ways to deal with them. I ran ClamAV and Snort for about 15 years, and we had plenty of heat over the years. This could have been avoided.

"Confirmation. So the question in my mind is: is the UK Government attempting to cover-up its previous advocacy of ADP, by censoring this old document? Or does it instead want the UK legal profession to avoid use of ADP and to what end?"

No, they just changed their advice/webpage. They aren't trying to "cover-up" anything. They just changed their stance in the face of current requests and laws. It's not a conspiracy.

TL;DR:

The author recounts their experience as an intern building software for the Department of Defense, unaware of its intended use. The software, designed to locate WiFi signals, utilized algorithms like R^2, Gaussian estimation, and Kalman Filters to improve accuracy and tracking capabilities. Despite the technical intrigue, the author acknowledges the software’s purpose was to aid in killing people, highlighting the ethical implications of their work.

The author recounts a past experience working on a project for a Department of Defense contractor, where they were tasked with creating a tool to locate phones, ultimately realizing it was intended for targeting and potentially killing individuals. This experience, along with examples like a deceptive quiz and Uber’s “greyball” feature, highlights the potential for code to be used unethically or even illegally. The author emphasizes the importance of developers considering the ethical implications of their work, as software increasingly impacts various aspects of society.

Developers have a responsibility to consider the potential misuse of their work, as unethical applications can have serious consequences. While there is no universal solution, developers should critically evaluate project requests, consider worst-case scenarios, and prioritize ethical considerations over deadlines. Ultimately, developers must decide whether to build a product, even if it has the potential for misuse, or to prioritize ethical concerns and potentially face consequences.

Code can have serious consequences, even death.

As a board member of an organization that was benefiting from Amazon Smile, this is just the lamest set of excuses I've ever seen. Amazon should have said: "We're cutting this because we don't want to maintain it, it hasn't been staffed, and isn't focused in our core business (making money)"

I would have believed that.

http://blog.snort.org/2012/02/vulnerability-research-team-is...

The Vulnerability Research Team is hiring, we want YOU.

Have you ever written a Snort rule? or wanted to?

Like messing about in the newest vulnerabilities or malware? Like writing exploits? Enjoy challenges like "Here's a file that crashes -application- , figure out why"? Want to work with us to design what is next in Snort? ClamAV? Razorback? Or any of the above topics?

We want you.

Let me talk about what I like.

The smartest people I've ever met all in one room. We get to bounce ideas off of each other, figure out strange ways of fixing a problem, and come up with a solution. That means anything from controlling EIP to how to write a rule to compare two things from two different streams using flowbits.

We pride ourselves in doing things not only better than the competition, but in the open too.

We work hard. We play hard. For instance, today, during break, we played kickball (remember that?) with a big yoga ball, and the ball got stuck in a tree. Yours truly climbed said tree and retrieved the ball. Then I came back inside and pulled apart some malware. Beware of nerf darts, RFI readers, and the 6lb sand-filled ball of doom.

Like working in an environment where it doesn't matter how you wind up at the result, as long as you get the correct results? Tired of being told what OS to use? Like debating the merits of C, perl, or ruby? Have a strong opinion between bash and zch?

If there's a problem that we don't have a solution for, we invent one. Last thing we invented resulted in patents that have our people's name on them.

Working on next years projects this year.

Being the best.

When you write protection for a vulnerability or malware here, you cover IDS/IPS, a NGFW, and two antivirus systems. You protect networks from endpoint to border and into the cloud.

If you gag when you hear the word cloud or synergy.

Vegetarian? Paleo? Meat eater? There is someone here that will sympathize with you.

Working for the fastest growing company in security Honestly there's way too many things to list.

Our currently open job listings are here. https://sourcefire.silkroad.com/epostings/index.cfm?fuseacti...

But that's not even the complete list. We're a growing company, with lots of projects under our purview, and we need people, both junior and senior to be able to fill these roles.

If you like Snort, or ClamAV, or think you can learn, and want to learn, shoot us your resume at research [at] sourcefire [dot] com.

Challenge yourself. Challenge us.

If you have a mac, you can just right click on a url, which osx detects automatically, even if it's not "a href"'ed, and using the easy popup services menu, you can click OpenURL.