Notices by Xavier Ashe :donor: (xavier@infosec.exchange)

#privacy #digitalsovereignty #kidsact #chatcontrol

@ryanc nice. I'm only kinda gay. And a tad bit high.

@ryanc <in my Joey voice> How you doin'?

@inthehands That not always true, especially when dealing with BYO LLM stacks. Very often I am tracing the request to find out that if it called any tools (or was supposed to). I often ask my LLM why a specific call was made.

Sounds like commercial LLMs don't give you this insight.

@martijn_grooten Here's why he did it: https://infosec.exchange/@jerry/115136713853460437

#vibecoding #meme #startrek #stng

An #infosec drama, in two screenshots.

@GossiTheDog And this article is the most recent thing I've seen. Good bits of details here.
https://nguard.com/sa-microsofts-recall-saga-continuous-coverage-and-latest-news/

@GossiTheDog Here's one tool that may help you figure out a plan of attack.
https://github.com/xaitax/TotalRecall

@b0rk What should be the correct behavior?

I have a #fedi question. How can I follow my #loops account from #mastodon ?
https://loops.video/@xavier

I've been seen. #meme #oversharing #fediverse

What's the difference in #mastodon and #pixelfed? On the surface, Mastodon supports text posts and picture posts, so why would I need Pixelfed? If I find Pixelfed profiles I like, I can follow them on Mastodon, right?

What am I missing? Besides preferences for text/pic vs. only pics, what's the difference?

@molly0xfff Does this settle things, or will this be challenged in higher courts?

@tek I do those a few times a month. In my city, there's a core group of security leaders that seem to be at all those. As sad as it is, they are one of my social groups. 100% funded by vendors.

@ryanc
(config)# vlan 69
(config-vlan)# name Nice

@patrickcmiller FYI... "Sponsored and written by #Varonis."

@patrickcmiller From @troyhunt's original blog post:

So, here's where that leaves us: this data is a combination of information sourced from public LinkedIn profiles, fabricated emails address and in part (anecdotally based on simply eyeballing the data this is a small part), the other sources in the column headings above. But the people are real, the companies are real, the domains are real and in many cases, the email addresses themselves are real. There are over 1.8k HIBP subscribers in the data set and this is folks that have double opted-in so they've successfully received an email to that address in the past. Further, when the data was loaded into HIBP there were nearly a million email addresses that were already in the system so evidently, they were addresses that had previously been in use. Which stands to reason because even if every address was constructed by an algorithm, the pattern is common enough that there'll be a bunch of hits.

https://www.troyhunt.com/hackers-scrapers-fakers-whats-really-inside-the-latest-linkedin-dataset/

@patrickcmiller I agree with Google on this one ;)

@patrickcmiller That's what I'm calling my datacenter ops manager from now on. He has a dashboard that we review weekly that measures physical capacity, electrical capacity, and heat capacity.

He's tired of me calling it a heat map.