Posts by pg@infosec.exchange
(DIR) Post #APKbbFSZ72vWm9SwWe by pg@infosec.exchange
2022-11-06T13:41:07Z
0 likes, 0 repeats
The sorting hat chose the right server for me.
(DIR) Post #APKbbGubiGx5HPaqsC by pg@infosec.exchange
2022-11-06T13:46:34Z
1 likes, 0 repeats
That's hilarious.
(DIR) Post #APOxm5EtorW1dqobYW by pg@infosec.exchange
2022-11-08T18:06:43Z
0 likes, 0 repeats
@wjmaggos @chris @davew @Therealdvorak I too was blocked by @davew on Twitter many years ago. No idea why - don't think we ever interacted.All I can think is he heard about the blasphemy of an XML-RPC implementation I created at HP and decided I was the devil.
(DIR) Post #APQuGLCD2wYQJjeJX6 by pg@infosec.exchange
2022-11-09T16:37:58Z
0 likes, 0 repeats
@leo Real downside to the WFH/hybrid change.I listen to a lot fewer podcasts each week.But I always listen to TWiT.
(DIR) Post #AVZUpJ94IovMj5X4oi by pg@infosec.exchange
2023-05-12T01:11:02Z
0 likes, 1 repeats
It's always DNS. aka #bard is garbage. A thread of Bard straight up lying on trivially checked data.I own secure.info domain name.Let's see if Bard can tell me that (note I'm logged in on my google account, so bard obviously knows, or has access to, who I am).1/n
(DIR) Post #AVZUpKr3wji41p7j1s by pg@infosec.exchange
2023-05-12T01:17:40Z
0 likes, 0 repeats
(this would go a lot smoother if snipping tool wasn't locking up windows)
(DIR) Post #AVZUpMZ3aeUlKYiNF2 by pg@infosec.exchange
2023-05-12T01:19:17Z
0 likes, 0 repeats
This is an incorrect answer.
(DIR) Post #AVZUpO9bgFKGGCp4qm by pg@infosec.exchange
2023-05-12T01:19:58Z
0 likes, 0 repeats
(DIR) Post #AVZUpPhJwNt733bW2S by pg@infosec.exchange
2023-05-12T01:21:13Z
0 likes, 0 repeats
OK, let's give it some clues...Still gets it wrong (looks like it is still stuck to the previous company name lookup)
(DIR) Post #AVZUpRLPonYQ9hN3Am by pg@infosec.exchange
2023-05-12T01:23:25Z
0 likes, 0 repeats
Maybe if we tell it is wrong again, it'll rethink.... nope, more wrongness. The domain was never registered, nor ever hosted at godaddy...
(DIR) Post #AVZUpSxNp7WF9k8szY by pg@infosec.exchange
2023-05-12T01:24:54Z
0 likes, 0 repeats
Guess we'll tell it to look at tucows:At least this is basically an accurate reply.
(DIR) Post #AVZUpUqimrNX1f2asy by pg@infosec.exchange
2023-05-12T01:26:13Z
0 likes, 0 repeats
Let's see if it can find my name in the DNS: What fresh hell is it doing now? This is just made up garbage:
(DIR) Post #AVZUpWRcr8UbyPJa2y by pg@infosec.exchange
2023-05-12T01:27:50Z
0 likes, 0 repeats
It said there were no TXT records... lets tell it that there are actually TXT records:Again, all the values printed here are garbage and bear no relation to reality.
(DIR) Post #AVZUpXzL7H3SlG61Ee by pg@infosec.exchange
2023-05-12T01:28:38Z
0 likes, 0 repeats
... express frustration with Bard
(DIR) Post #AVZUpZWLQ339VuXtJo by pg@infosec.exchange
2023-05-12T01:29:50Z
0 likes, 0 repeats
I share my output from digGuess it knows how to parse that, and ding ding it says my name.
(DIR) Post #AVZUpb5TaukKN9zSiW by pg@infosec.exchange
2023-05-12T01:32:01Z
0 likes, 0 repeats
And finally, wrap up with a #wtfBard
(DIR) Post #AVZUpchRbEi9NClIXI by pg@infosec.exchange
2023-05-12T01:33:21Z
0 likes, 0 repeats
My take from this is that new Bard just invents shit responses that look authoritative and throws it out there.
(DIR) Post #AVZUpeFrojqACFsIpU by pg@infosec.exchange
2023-05-12T01:53:00Z
0 likes, 0 repeats
This was a fun reply where I guess it just had no idea what I said.
(DIR) Post #AY16dXJDii2DoVPRA0 by pg@infosec.exchange
2023-07-24T10:43:12Z
0 likes, 0 repeats
@dave U+1D54F š¯•¸Can he really trademark that?