Hello,we just wanted to use the OpenVuln API today, Webserver responds with 200 but an SSL encryption error.Any knows errors on your side ?It worked for one year without problems.kind regards,Kai Lohse
Hi,played around with the API with 7000 devices and 200 IOSes from my customers.I get some strange answers from the API what makes me start thinking about the Quality of the received data.Maybe someone can tell me why this happens, when i want to rea...
Hello,i want to use the Support API, i'm already using the OpenVulnAPI.I don't see the Support API in the "myAPI" page so it seems i need to be authorized to use it.i saw the PSS and SNTC onboarding process but it seems not to fit for me as a Gold Pa...
Hello,i just tried the IOS checker calls in the CERT API.When using the normal web page i get sometimes an output that says "combined fix" which is pretty useful.I don't receive it in the XML it seems, will it be included someday or is there a hint t...
Hi,i am using the CVRF and OVAL downloads in XML format. I saw that for example CVE-2016-6379 (cisco-sa-20160928-ipdr) shows more information when opened in HTML than in the CVRF and OVAL files, for example the affected products section is completely...
Hello, thanks for the info, i have the same task, WLCs in HA shall get a new IP.I was wondering that you have to break the HA, can't we just enter the 3 new IPs and apply the new setup?
Hi all,good News, it works again, updated OpenSSL.After googeling it seems I'm not the only one who had this problem.THANX FOR ALL THE HELP DELPHI FOREVER
Hi,did some more research, it is a recompiled OpenSSL to match Indy9.OAuth works, API access shows an error:OpenSSL> s_client -connect api.cisco.com:443Loading 'screen' into random state - doneCONNECTED(00000088)868:error:14077410:SSL routines:SSL23_...
Thanks for the suggestions.It's not OpenSSL, it is the free Indy V9.0.10I place two DLLs in the EXE directory and it uses TLSv1.0 . you are using TLSv1.2 , maybe this is a problem.ssleay32.dlllibeay32.dllUnfortunately the DLLs don't contain any versi...
Hi Mark-David,just tried again with a Wireshark, it shows a handshake failure:No. Time Source Destination Protocol Length Info 50 66.031697000 173.37.145.221 10.1.1.11 TLSv161 Alert (Level: Fatal, Description: Hand...
