Getting the app with an exclamation, and the website itself shows the cert expired a few hours ago.
Hopefully just an oversight and they will realise when they wake up.
u/stingbot
Getting the app with an exclamation, and the website itself shows the cert expired a few hours ago.
Hopefully just an oversight and they will realise when they wake up.
I have our cloud screenconnect connected to OpenObserve via the splunk addon(via a n8n webhook to reformat it) so all the events gets streamed to that and I pickup on flagged events like login failures.
There are a few failed logins today where someone is using what seems to be a logged in genuine Connectwise SSO account(otherwise we only have SAML and Connectwise SSO enabled), and then trying SQL injection for the username.
As far as I can tell Connectwise SSO sends you to the Connectwise website to authenticate, so not sure how they can try and authenticate on our system with that unless logged in already.
Seems they are trying to access the api now, where previously there was no referr
Is it possible to request the pricing on Hudu Radar be clarified?
Is it per Hudu Instance, or per client documented inside of Hudu?
Otherwise keen to see it, as Domotz and Auvik seem to be on paths of enshittification and continually have less benefits.
Referring to this: https://duo.com/docs/microsoft-eam
I can only find a recent reference from this post but it doesn't mention partners or GDAP: https://new.reddit.com/r/msp/comments/1e4lkzu/migrate_from_custom_controls_to_external/
We would love to be able to move to Duo MFA integrated natively into the auth flow, but I cannot find any info on whether this is allowed per this: [https://learn.microsoft.com/en-us/partner-center/security/partner-security-requirements-mandating-mfa](https://learn.microsoft.com/en-us/partner-center/security/partner-security-requ
Hi,
I'm not having much luck finding a way to match the clients name in the email subject so it can be mapped against their client in service desk.
The use case is for Blumira alerts, the clients name is in the subject line after the @ symbol, currently every email is going to the unknown catch all.
We have it match the client name exactly thinking we could just parse into Halo.
It doesn't seem there is a way to match the client name without it explicitly saying "client:" so the formatted email option could work.
Is there a way to match the client name after the "@ clientname" part in the subject line?
It seems there needs to be an option along the lines of match to "@ $AREA", but I've
Hi,
Seems there is no data for any stations around Melbourne, about 20 stations around here, line is completely flat, shows a slight blip around 4 hours ago then flat again.
Is there an issue with PurpleAir?
Local data is working fine
Is the air just that clean? There are planned burns around and a fire in the northern suburbs but still showing nothing.
Seems odd for all of Melbourne to have super clean air and nowhere registering even a 1.
Loving the Tempest for Temperature, lightning and when it starts raining, but it makes no sense after a rain event for it to show almost 100mm of rain when the official weather here shows 14mm.
I even take the rain calc from Tempest with Home Assistant and run it into an "energy meter" to accumulate the precipitation sensor from the Tempest integration, and it showed 16mm which is more realistic.
Why is the Tempest app so far out?
Also had other rain events where it was barely 1mm of official rain, but tempest showed 20mm.
Other units around me show equally wild numbers, some with 40 to 90mm.
I'm sure if we had 100mm of rain in the 45mins of rain time we just had most of South Australia
Anyone know how/where in the code to add "ForceAuthn=true" to the SAML request so that every SAML login is required to full MFA reauth when using Azure as the IdP? Self hosted instance.
Failing that can we still put in feature requests?
So far Conditional access policy set to 1 hour reauth is as good as it gets, but ForceAuthn would be the ideal scenario.
Hi,
Had a weird one today where multiple Fortigate(firmware from 6.0 to 7) all started blocking genuine SSL certs.
started about 10:55am and kept blocking things like Xero, Dropbox, Spotify, Trello, Twitter, Banks, Huntress.
The only common thread I could find was that the units that did this were still pointing to Fortiguard for their DNS.
I did have to allow "Invalid Certs" in the SSL inspection(not deep) policy to let the sites work again in the first instance.
Was only 6 or so units, so a small fraction of the fleet, but most are configured the same, even with Fortiguard as their DNS so that might be a red herring.
Is there a way of working out why the cert was blocked as Qualys SS
Hi,
Had a weird one today where the voltage in the PW went to 0 for about 10mins today and then rebooted itself. I lost power for a little bit when this happened.
/api/status shows that it reset itself at the time the power glitches, but I can't tell if it was a fault, or if it rebooted for a firmware update.
Firmware shows 23.12.2 which seems to be from around April, but I can't find that specific version number anywhere for an exact date.
I can't contact Tesla directly to ask what happened, the app is pointing me back to the installer who won't reply for a while.
Is there any way to find out why it did the reboot?
This seems like it should have a simple answer, but I've done that many Google searches that Google stopped me to make sure I was human, and there wasn't a simple answer amongst all the searches I tried.
If I have a NPS/Packetfence/Clearpass/FreeRadius running in a VM(HyperV) and I have a single 802.1x capable switch and I want port auth on every port on the switch including the one that NPS is running from, how do I deal with the NPS authorising itself?
This sounds right but seems wrong: is it as simple as having a management VLAN that the switch can talk to NPS on and that VLAN in HyperV NIC for that VM is either tagged/untagged so that the switch can communicate without needing to autho
Seems that in recent versions FortiOS has changed the local rating lookup from a GET to POST, which is fine, but the response is now somewhat useless and has no usable information in the response.
Previous response to: https://192.168.10.1/api/v2/monitor/utm/rating-lookup/select?access\_token=xxx&url=dodgy.url was:
{
"http_method":"GET",
"results":{
"url":"https:\/\/dodgy.url",
"category":"Security Risk",
"subcategory":"Phishing"
}
Now the URL is simply echo'd back without any category or subcategory info:
{
"http_method":"POST",
"results":[
{
"url":"https:\/\/dodgy.url"
}
I'm posting the corre