Cybersecurity

10060 readers

34 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 3 years ago

MODERATORS

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

Why am I seeing this? How do I know if it is safe to accept? (sh.itjust.works)

submitted 1 day ago by pixeldaemon@sh.itjust.works to c/cybersecurity@sh.itjust.works

9 comments fedilink hide all child comments

This popped up in Conversations today and I'm concerned

you are viewing a single comment's thread
view the rest of the comments

[–] elmicha@feddit.org 3 points 1 day ago

It would be valid if it would be served by the XMPP server, but it is not:

% openssl s_client -connect xmpp.jp:5222 </dev/null -starttls xmpp
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = E8
verify return:1
depth=0 CN = xmpp.jp
verify error:num=10:certificate has expired
notAfter=Jun  5 10:51:05 2026 GMT
verify return:1
depth=0 CN = xmpp.jp
notAfter=Jun  5 10:51:05 2026 GMT
verify return:1
***
Certificate chain
0 s:CN = xmpp.jp
i:C = US, O = Let's Encrypt, CN = E8
a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
v:NotBefore: Mar  7 10:51:06 2026 GMT; NotAfter: Jun  5 10:51:05 2026 GMT
...