2
I Use This!
Moderate Activity

News

Analyzed about 13 hours ago. based on code collected about 21 hours ago.
Posted about 4 years ago
IVRE v0.9.15 ‘lockdown’ release IVRE version 0.9.15 has just been released (seven months after version 0.9.14), and is available on Github, PyPI and AUR. Thanks a lot to the contributors! Changelog The most notable changes since version 0.9.14 ... [More] include: Support for ZGrab2 (HTTP) & ZDNS results. Improve Masscan integration (particularly with IVRE’s fork). Improve Nmap fingerprints handling (for Masscan & Zgrab2 results). Handle MAC addresses (in nmap, view and passive purposes). Add TinyDB support (you can test IVRE without a database server!). Add ivre auditdom tool (AXFR tests). Read more... [Less]
Posted over 4 years ago
IVRE v0.9.14 release IVRE version 0.9.14 has just been released (three months after version 0.9.13), and is available on Github, PyPI and AUR. Changelog The most notable changes since version 0.9.13 include: Support for the MongoDB backend in flow ... [More] (Vincent Ruello); the Neo4j backend is now deprecated and will be dropped in a near future. Support for an experimental Elasticsearch backend in view (Angélique Baille); while it is far from comprehensive for now, it is enough to store view data in an Elasticsearch database and access if from other Elasticsearch-based tools, such as Kibana (the documentation already has a section IVRE with Kibana covering this; see also the screenshots). IPv6 support in DNS blacklist answers (Olivier Croquin). Read more... [Less]
Posted over 4 years ago
IVRE v0.9.14 release IVRE version 0.9.14 (three months after version 0.9.13 has been released), and is available on Github, PyPI and AUR. Changelog The most notable changes since version 0.9.13 include: Support for the MongoDB backend in flow ... [More] (Vincent Ruello); the Neo4j backend is now deprecated and will be dropped in a near future. Support for an experimental Elasticsearch backend in view (Angélique Baille); while it is far from comprehensive for now, it is enough to store view data in an Elasticsearch database and access if from other Elasticsearch-based tools, such as Kibana (the documentation already has a section IVRE with Kibana covering this; see also the screenshots). IPv6 support in DNS blacklist answers (Olivier Croquin). Read more... [Less]
Posted almost 5 years ago
IVRE v0.9.13 release IVRE version 0.9.13 has been released, and is available on Github, PyPI and AUR. Changelog The most notable changes since version 0.9.12 include: Support for JA3 fingerprints and User-Agent values in view (Vincent Ruello) IPv6 ... [More] support: in utils.get_addr_type() (Vivien Venuti) DNS (AAAA) answers in passive (Angélique Baille) Support DNS blacklist answers in passive (Marion Lafon) Read more... [Less]
Posted almost 5 years ago
IVRE v0.9.13 release IVRE version 0.9.13 has been released, and is available on Github, PyPI and AUR. Changelog The most notable changes since version 0.9.12 include: Support for JA3 fingerprints and User-Agent values in view (Vincent Ruello) IPv6 ... [More] support: in utils.get_addr_type() (Vivien Venuti) DNS (AAAA) answers in passive (Angélique Baille) Support DNS blacklist answers in passive (Marion Lafon) Read more... [Less]
Posted over 7 years ago
IVRE: screenshot all the things! The title of this blog comes from a nice article from 2014 named Scan Internet and Screenshot all the things Some people have been asking us how the screenshots published with the Internet-wide Modbus scan had been ... [More] taken. Truth is, there was nothing to be proud of, and nothing worth publishing. As an example, I used a PhantomJS script to screenshot a Web-based RDP client… But there are some great news: four Nmap scripts are now integrated to IVRE to take screenshots, and handle four different protocols. Read more... [Less]
Posted over 7 years ago
IVRE: screenshot all the things! The title of this blog comes from a nice article from 2014 named Scan Internet and Screenshot all the things Some people have been asking us how the screenshots published with the Internet-wide Modbus scan had ... [More] been taken. Truth is, there was nothing to be proud of, and nothing worth publishing. As an example, I used a PhantomJS script to screenshot a Web-based RDP client… But there are some great news: four Nmap scripts are now integrated to IVRE to take screenshots, and handle four different protocols. Read more... [Less]
Posted over 8 years ago
IVRE has a new home! Together with a new logo, IVRE now has its own website: ivre.rocks! By the way, we have a demonstration instance there which is only accessible with an account. Just e-mail us to get an access! It runs the latest version from the ... [More] repository, using Docker images. For the record, the original domain (iv.re) has been deleted (after a one day notice!) because Afnic (who handles .re) discovered that the domain validity check for .re was broken and should not have allowed such a domain. [Less]
Posted almost 9 years ago
IVRE: new (cool) features Long time no post… so here is a Prévert-style inventory of some recent IVRE’s features. Read more...
Posted about 9 years ago
Mining public keys with IVRE Background In my previous post I explain how I have run a scan against Internet-exposed Modbus-enabled devices, and share the results obtained. I have been asked several times why had I chosen to run a Zmap + Nmap scan ... [More] instead of a Zmap + Zgrab, which would have been a lot faster. Here is my answer: I wanted to scan the other services running on the Modbus-enabled devices, because: They tells a lot about the device behind the IP address (the screenshots is a feature I really like, but anonymous FTP file listing is also great, for example) They often show intersting weaknesses. Read more... [Less]