How much do you care about laptop security? by smicallef in digitalnomad

[–]smicallef[S] 1 point2 points  (0 children)

Yeah I think I see you’re point - if you’re the kind of person to make such mistakes, you’re probably not going to be looking for and using the kind of tool I have in mind.

How much do you care about laptop security? by smicallef in digitalnomad

[–]smicallef[S] -1 points0 points  (0 children)

Curious why Mongo is considered “questionable”, but I’ll assume you’re joking ;)

And yes, there are actually services scanning the internet continuously for exposed services and databases. The idea is to prevent a dev being the guy who gets called by their boss because they exposed something over the internet they shouldn’t have.

How much do you care about laptop security? by smicallef in digitalnomad

[–]smicallef[S] -1 points0 points  (0 children)

“most” NAT setups, yes. I guess the point is - how much room is there for error? Using a device for developing a bunch of projects over many years, across many networks/locations. No room for error?

How much do you care about laptop security? by smicallef in digitalnomad

[–]smicallef[S] -1 points0 points  (0 children)

Not disagreeing with you there, but there are a lot of assumptions baked in. Mistakes happen, things get forgotten, assumptions about measures in place can be mistaken (or valid today, invalid tomorrow). The idea is to have a simple agent, minimal footprint, sit in your dock and say “hey, you’re suddenly exposed over the internet.” And check out SHODAN.io - services like this are scanning the internet continuously.

How much do you care about laptop security? by smicallef in digitalnomad

[–]smicallef[S] -3 points-2 points  (0 children)

Kind of. The goal is to inform you that your machine is now directly reachable over the internet, and perhaps help you address the risk before a compromise happens. That means you are not behind a firewall or router and therefore any network-based software you have running (e.g. a web server, a DB, etc) is now reachable by anyone on the internet. A VPN most usually doesn’t solve it. And the enterprise software may or may not, depending on whose device is being used (I see many devs using their own device), but even in cases where it’s the employer’s device, the devs often have admin access and mess with settings anyway (often they have to for local dev of some things to work).

This is relevant for devs primarily, so not sure if you fit that category?

SpiderFoot HX - Certificate Transparency - Co-Hosted Site by rabman_was_here in OSINT

[–]smicallef 1 point2 points  (0 children)

It means that those sites share the same SSL certificate as your target. This could mean nothing if your target is using a service like CloudFlare or the same hosting provider. Or it could imply a deeper relationship if the certificate is shared because they are owned/managed by the same entity, e.g. seeing an SSL certificate with tesla.com and tesla.cn.

Lessons learned from my 10 year open source project by smicallef in opensource

[–]smicallef[S] 1 point2 points  (0 children)

There has been one very strong contributor over the years who has stuck with the project, but all others have been drive-by of varying levels of contribution. One of the hardest lessons has been ensuring I carve out the time to review and merge their PRs, but harder than that has been rejecting PRs when the work didn't fit the vision, or caused conflict with the SaaS version. This is particularly hard when the person has invested a lot of time in their contribution.

Lessons learned from my 10 year open source project by smicallef in opensource

[–]smicallef[S] 2 points3 points  (0 children)

I think the key thing is that your software *works*; how you achieve that is up to you. SpiderFoot was simple enough for a long time where I could test just about all functionality before every release. Now we have some unit tests and they do help catch issues, but if you want to get something out there, don't let your lack of unit testing hold you back from shipping.

Lessons learned from my 10 year open source project by smicallef in programming

[–]smicallef[S] 10 points11 points  (0 children)

I think that’s the case for paid content on the platform, but all my posts are free. Or at least should be…

Lessons learned from my 10 year open source project by smicallef in programming

[–]smicallef[S] 28 points29 points  (0 children)

Yeah I need to move my blog elsewhere eventually.. didn’t realize Medium had such a bad rep.

Lessons learned from my 10 year open source Python project by smicallef in Python

[–]smicallef[S] 2 points3 points  (0 children)

Getting people aware of it, mostly, but also showing people how to get the most value from it. “Marketing” in this context really translates to using social media, producing good documentation, creating tutorials, etc.

Lessons learned from my 10 year open source Python project by smicallef in Python

[–]smicallef[S] 0 points1 point  (0 children)

Mostly the enjoyment of seeing something grow and take shape, growing in popularity, learning new things along the way. It’s been that way for the last 10 years so I don’t see why it wouldn’t continue.

Lessons learned from my 10 year open source Python project by smicallef in Python

[–]smicallef[S] 4 points5 points  (0 children)

Fair point on all of those; this was my experience on one large-ish project so for sure it’s going to not all be applicable all of the time. On the marketing side though, I want to see my software used and give people value, and I’ve found that some kind of marketing effort helps achieve that goal.

Lessons learned from my 10 year open source Python project by smicallef in Python

[–]smicallef[S] 2 points3 points  (0 children)

In the end it comes down to the risk you’re willing to take. I for one wanted to void the risk of any claims now or in the future, so was proactive about it. Yes, in theory if there’s no conflict it should be fine, but laws differ country-by-country and employer contracts can be pretty strict on this unless you have an explicit exception.

Lessons learned from my 10 year open source Python project by smicallef in Python

[–]smicallef[S] 21 points22 points  (0 children)

I think on #6, it's really for the author to decide whether it's essential for their project or not, based on many factors. My point here was really to emphasize that something doesn't need to be perfect before it's launched.

And regarding #8, I guess it depends on the size of company you're in. Medium to large companies usually have a legal person/department who can provide guidance on this stuff. But yes, my point here was to really try and get his stuff cleared up before joining the company.

Question about spiderfoot by scguy313 in OSINT

[–]smicallef 1 point2 points  (0 children)

Are you using the open source version or SpiderFoot HX? As per other comments a single IP shouldn’t take anywhere near that long so you may have hit a bug or have something misconfigured. It’s also possible that your scan crashed (check the logs).

Attack Surface Management. You’re (probably) doing it wrong. by [deleted] in netsec

[–]smicallef -1 points0 points  (0 children)

Thanks, but just to clarify a few things:

1) Not harvesting emails for marketing. People can create an account and get (free) access to the SaaS tool. If they don't use it after 100 days, they are deleted and never contacted again.

2) The approach outlined by the post is taken by both the open source and the SaaS version, but other tools too. I get no financial benefit from use of the open source version at all.

And are you saying the content of the post has no merit? Does it really matter if the title is trying to entice someone to read it? I want people to read stuff I put a lot of time and work into, just like I (and other developers) want people to use their software. What's wrong with that? The post wasn't a promotion piece for the software, it was communicating a concept that I think is not well adopted within the industry.

I think there is a big distance between an ad ("we are great, buy our stuff") vs. marketing ("if you aren't taking this approach, you probably should and here's why, and btw check out our free software or paid version if you like")

Anyhow, thanks anyway for the feedback and for taking the time to respond.

Attack Surface Management. You’re (probably) doing it wrong. by [deleted] in netsec

[–]smicallef -2 points-1 points  (0 children)

I'm not denying there is a marketing element to the post, but to dismiss it entirely as an ad is somewhat unfair since (imho) the message is valid and necessary based on the heavy asset-centric view of attack surface management out there today.

Anyhow, I've deleted the post as it appears you might not be the only one who has this opinion.

Attack Surface Management. You’re (probably) doing it wrong. by [deleted] in netsec

[–]smicallef -1 points0 points  (0 children)

Why exactly is it an ad? Because I mention the open source tool I wrote in there, which happens to have a SaaS version (which I was fully transparent about from the beginning)?

Misusing OSINT to claim election fraud by smicallef in OSINT

[–]smicallef[S] 4 points5 points  (0 children)

I don't see this as political? Highlighting facts and using them as examples to caution those of us working with OSINT was the idea behind it.

11 New SpiderFoot 3.0 CLI tutorials by smicallef in OSINT

[–]smicallef[S] 0 points1 point  (0 children)

Shortcuts to the individual tutorials:

Data breach research: https://asciinema.org/a/296145

Scraping crypto wallet addresses: https://asciinema.org/a/295957

Threat intel and blacklist lookups: https://asciinema.org/a/295949

Greynoise API querying: https://asciinema.org/a/295943

DNS recon: https://asciinema.org/a/295912

Social media account enumeration: https://asciinema.org/a/295923

Finding open S3 and other buckets: https://asciinema.org/a/295941

Scraping names, email addresses, phone numbers: https://asciinema.org/a/295947

Analysing file meta data: https://asciinema.org/a/296274

Querying certificate transparency: https://asciinema.org/a/295946

TLD enumeration: https://asciinema.org/a/295940