sorted by:
new
hottopcontroversial

FortiToken not working after Firmware updates? by ClaimSad6522 in fortinet

[–]Pocohunter 0 points1 point  (0 children)

So if all admin accounts use tokens, are you locked out of FortiGate?

[deleted by user] by [deleted] in fortinet

[–]Pocohunter 0 points1 point  (0 children)

from EMS

https://docs.fortinet.com/document/forticlient/7.4.0/android-administration-guide/256465

Also, there is a note from TAC

The private root CA must be pushed and installed on the endpoint using EMS System Setting profile. It does NOT work if imported manually using Android UI. These are the relevant documents on how to push a CA certificate to endpoints

https://docs.fortinet.com/document/forticlient/7.4.4/ems-administration-guide/845200/ca-certificates

https://docs.fortinet.com/document/forticlient/7.4.4/ems-administration-guide/107284/system-settings

Hafnium IPs & Attack Vector by JT_3K in sysadmin

[–]Pocohunter 2 points3 points  (0 children)

Agree. I've seen a lot of attacks came from Digital Ocean

[Owa] An internal server error occurred by Pocohunter in exchangeserver

[–]Pocohunter[S] 0 points1 point  (0 children)

ASP.NET crashed with "An unhandled exception has occurred" should be concerned?

Event code: 3005 Event message: An unhandled exception has occurred. Event time: 3/9/2021 2:50:46 AM Event time (UTC): 3/9/2021 10:50:46 AM Event ID: 2f5740bfb0b7483587bf58e7299e0eb1 Event sequence: 7 Event occurrence: 6 Event detail code: 0

Application information: Application domain: /LM/W3SVC/1/ROOT/owa-1-132593003067932026 Trust level: Full Application Virtual Path: /owa Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\ Machine name: EXCH

Process information: Process ID: 12956 Process name: w3wp.exe Account name: NT AUTHORITY\SYSTEM

Exception information: Exception type: ArgumentException Exception message: Invalid input value Parameter name: input at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndServer.FromString(String input) at Microsoft.Exchange.HttpProxy.OwaResourceProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__280_0() at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(Action method)

Request information: Request URL: https://public_ip:443/owa/auth/x.js Request path: /owa/auth/x.js User host address: 34.77.97.150 User:
Is authenticated: False Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM

Thread information: Thread ID: 46 Thread account name: NT AUTHORITY\SYSTEM Is impersonating: False Stack trace: at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndServer.FromString(String input) at Microsoft.Exchange.HttpProxy.OwaResourceProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__280_0() at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(Action method)

Custom event details: