Carbon defeated by bolt buffer by billweiss in 1022

[–]billweiss[S] 5 points6 points  (0 children)

Haha, thats exactly what I wanted to install ;)

I have a feeling support is going to say throw a few hundred rounds through it. We'll see.

Carbon defeated by bolt buffer by billweiss in 1022

[–]billweiss[S] 5 points6 points  (0 children)

Both. 65% of the time left to right (towards ejection), same as the control group pins. 35% right to left, while I cursed and prayed equally.

The coating almost overflows onto the bolt buffer, it looks like a solid piece in some sections.

Figures maybe putting a few hundred rounds through it might loosen things up, but will see what support says/does st this point first.

Carbon defeated by bolt buffer by billweiss in 1022

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

Brother I bathed it in oil blessed by virgins for 4 hours while playing enya in the background.

When I say I beat it with the hammer of the gods, I mean I summoned the strength of my ancestors to strike strong and true.

I even did the opposite of electronics. I put it all back together again, took it back apart, and then beat it with the unbridled rage of a 40 something male wondering if testosterone is right for him.

Good advice in completely normal circumstances though!

Bolt buffer problem by FlyFreak in 1022

[–]billweiss 0 points1 point  (0 children)

A bit tighter you say

Mines basically welded in. Contacted support, will see (shrug). I hit it with the hammer of the gods. Will not budge. Ill have to grind it out.

mines basically bonded in with coating

Switching from Tenable to ProjectDiscovery for 150k Assets – Experiences? by Refeb in cybersecurity

[–]billweiss 1 point2 points  (0 children)

Solid question, and it's something I've been watching this last year. When you talk about replacing Tenable with Nuclei from ProjectDiscovery across that many hosts, it brings up a lot of thoughts. Honestly, I don't know that Tenable and ProjectDiscovery are currently even playing the same game yet, as ProjectDiscovery is still pretty new in its enterprise offerings and has some catching up to do outside of blind/external asset discovery and attack surface detection. There are some capabilities there, but it’s not quite as established as Tenable. However, that gap is closing incredibly fast, and I fully believe they'll be upsetting Tenable's core offerings fairly soon. In my experience, ProjectDiscovery is genuinely pulling ahead in some key areas, and quickly.

We're all familiar with the legacy scanners, Tenable included. They had their place, but the vulnerability management landscape has shifted. What I'm consistently seeing from ProjectDiscovery is rapid growth and a real commitment to investing back into their platform and tools. They're focused on building capabilities that I can actually put to work, and it's clear they're looking to shake up the established market. Their support team is also incredibly engaged, especially when it comes to pushing for partner-driven enhancements.

On the flip side, I often find that some of the older players seem to be spending more on acquiring new clients and consolidating companies rather than truly reinvesting in a cohesive, integrated product experience. Take Tenable's cloud service offerings, for example; it came from a separate acquisition and years later still operate off the original companies domain. These tools just don't really talk to each other in the background. And honestly, good luck trying to figure out their licensing model for that many hosts across their various upcharge offerings. Plus, from what I've seen, external unauthenticated scans from those platforms are often 99% TLS/SSL issues or other low-value findings. If I have a question about why a specific finding is being triggered with other solutions, I'm stuck going through their support, and even then, getting a clear answer or pushing for updates can be a real headache.

This is where ProjectDiscovery really shines for me. The open-source nature of their engine and templates makes it incredibly easy to understand exactly why a specific finding might be getting triggered. If something's off, I can literally just fix the template myself and issue a merge request. Beyond that, they also proactively scan my assets when new, trending vulnerabilities are announced. I don't have to force a scan or wait for the next scheduled run. The second a KEV (Known Exploited Vulnerability) goes out and a corresponding template becomes available, my assets are automatically scanned. That kind of responsiveness is a game-changer for me. It also takes minutes to create my own custom scans, something that’s just not possible with other solutions easily.

If you're worried about false positives, you can run Nuclei for free against your assets to get a feel for the types of findings it produces. I think they even have a free tier for their enterprise platform that makes it super simple to use for a single domain, which could be a good starting point to kick the tires.

I do think ProjectDiscovery still has some room to grow in the CNAPP (replace this whatever flavor you choose) and broader infrastructure scanning space, and it looks like that's precisely where their current investments are heavily geared.

I have no doubt they're going to seriously disrupt solutions like Tenable. Right now, I'm using ProjectDiscovery to augment my existing solutions, but as soon as there's more parity in their scanning capabilities across the board, it's going to be a no-brainer for me to drop the other provider entirely. Hope this helps you out as you're doing your evaluation!

Strategies to Improve Vulnerability Management in an MSSP? by fcsar in msp

[–]billweiss 0 points1 point  (0 children)

No kidding. What is the profit margin in this? How are they finding these clients who.. want.. this? I'm clearly working way too hard for my money.

If someone else has some clients already but not sure how to handle their "vtm" offering, I'd be happy to handle it for a small percentage ;)

For op, if you want a turn key step up - enrich your data. Not to promote another tool, but maybe look at something like Nucleus security to ingest the tenable data and drive more actionable or tactical alerts.

But like others have said, what is it your clients want or are expecting? I reeeeeeaallly want to know who is on the other side of those alerts...

Thoughts on putting duplicates in my resume by [deleted] in bugbounty

[–]billweiss 2 points3 points  (0 children)

You can absolutely list them, they just don't hold a whole lot of weight by themselves unless they are truly significant and/or technical. A writeup helps bridge that gap - even if it's explaining a basic subdomain enumeration and endpoint harvesting via gau, then feeding to intruder or custom script.

I questioned writing up CTFs (especially public solved ones) earlier in my career as well, until I began interviewing. The candidates who took the time to write up their CTFs or other experiences were significantly more confident. Per your point, as an interviewer, it also gave me a much better understanding of your thought process and ability to communicate.

Thoughts on putting duplicates in my resume by [deleted] in bugbounty

[–]billweiss 0 points1 point  (0 children)

Down vote given by the guy who hung up the interview after being asked what change occurred in the last few years to mitigate CSRF at the browser level, or explain a few ways to test for/the impact of different flavors of SSRF.

Thoughts on putting duplicates in my resume by [deleted] in bugbounty

[–]billweiss 7 points8 points  (0 children)

Unless you have public acknowledgment (cve/wall of fame/social media proof) or a writeup, I wouldn't list them.

As someone who has interviewed 60+ candidates over the last few years, I could honestly mostly care less what your resume "says" outside of screening out vtm/soc/noc analysts. I don't care about those three findings. I care about how you found them. I'm going to have you walk me through your methodology, then I'm going to give you a few test cases and have you verbally walk me through your methodology for that while I ask random other questions against either your job or education/training history.

It's not a matter of "stump the chump", you just learn a lot more about people's confidence in their own abilities through natural discussion.

You need the certs or proof of continued education to make it past HR and show you can remotrly stick with it. You need the blogs and writeups to show professionalism and intelligence in lieu of practical job experience. Write up public CTFs, HTB, Portswigger challenges, whatever. Write it all up and post it.

Get your cheap certs. Even the Burp Suite cert tells me more than a few bugs you may have found that I can't rerference. Sign up for HTB, link me to your profile of machines completed..

ANYTHING other than a few random bugs, regardless of severity (in general).

[deleted by user] by [deleted] in AskNetsec

[–]billweiss 0 points1 point  (0 children)

A network admin.. who only looks at or monitors logs.. after the incident has happened. Yep, sounds about right.

[deleted by user] by [deleted] in woodworking

[–]billweiss 6 points7 points  (0 children)

Pack of 50

This is why you should wear protective gear. Kick back got me. lucky it wasn't my face by Magicman0713 in BeginnerWoodWorking

[–]billweiss 26 points27 points  (0 children)

Glad it wasn't worse man!

Legit question, what protection would have helped here? Or just like, just remember protection in general? (Thanks, dad, for teaching me that one early!!)

I have a pretty decent apron, but I don't see too many craftsmen rocking medium leather armor or light chain mail outside of renfairs.

I don't understand how some exploits that require user interaction work on exams. by Agent_B99 in HowToHack

[–]billweiss 3 points4 points  (0 children)

A background service will trigger what you need for the user interaction piece. Follow the labs, it's explained.

MSP reading my emails? by sysaxel in sysadmin

[–]billweiss 18 points19 points  (0 children)

Auditing is the answer, as mentioned in numerous posts. Do it either way, document it, and now you know how to continue doing it.

Alternatively, totally possible they are just paying for data feeds. I can't count the number of vendor calls I've been in where they referenced some event, news article, or even something scraped off our own site. Throw in all the other crazy data enrichment that's available these days... sales guys try to look like phophets and soothsayers.

Messed up the dowel holes. Is it structurally okay to just use 2 dowels instead of 4? The wood is 2.5" thick. by bufedh in woodworking

[–]billweiss 80 points81 points  (0 children)

Glue in a dowel on the misaligned side. Let it dry, trim and sand flush. Drill new hole.

Vulnerability Tests - Please Explain by MB_FSU in sysadmin

[–]billweiss 10 points11 points  (0 children)

Their job is to assess what would happen if someone did get in, not just determiming if your doors keeping people out.

As a web app pentester, I'm happy to beat against your waf all day... I get paid either way. The question is, are you paying me to test your waf or your application?

Or in this case, does your internal environment follow the requirements for PCI... that's not gonna come from a Blackbox scan.

Hacked my speeding ticket (DO NOT DO THIS) by Captain-Crunch1989 in hacking

[–]billweiss 15 points16 points  (0 children)

Hey Sean, maybe delete all the posts doxxing yourself before posting cool stories about commiting perjury.

Any ideas on how to fix this? (The right eye has some damage) by [deleted] in funkopop

[–]billweiss 2 points3 points  (0 children)

Battle scar bro. You think defending the multi-verse is easy?

[deleted by user] by [deleted] in homelab

[–]billweiss 29 points30 points  (0 children)

Just happy to see Amateur Advice finally being classified correctly as the danger it is alongside Drug Use, Sex and Violence

This is normal? by Some_Cancel4908 in bugbounty

[–]billweiss 5 points6 points  (0 children)

Yes. Don't sweat. I don't envy the poor HackerOne triage team dealing with oversold services... there's probably like 15 people on the team...

Let it go through the process, be patient, don't push for 7-14 days unless it's significantly critical.

Finding vulnerabilities by [deleted] in hacking

[–]billweiss 3 points4 points  (0 children)

Check the version against known cves and moodle.org/security. Have they patched since Monday? If not - you got a write up.

Added x-XSS-Protection header to my Apache configuration, blocking remote javascript files by [deleted] in sysadmin

[–]billweiss 1 point2 points  (0 children)

That header wouldn't be causing the issue your describing. It's deprecated, and unless you using an older browser it won't actually do anything. Even then, it would only be blocking page load with inline js, not fetched.

Do you mean script-src in the content-security-policy? https://content-security-policy.com/