Great visualization of the libc singleppoint of failure problem. The weighted graphs showing call frequency are particularly useful for risk assessment since not all dependencies carry equal criticality in practce. Would love to see how Sossy handles circular dependencies if they show up in more complex application ecosystems.
Thanks, yes from the visualization we see clearly how important the libc shared library is. However, this should not come as a surprise, pretty much every application written in C has a #include<stdio. h> somewhere in the source code for handling inputs and outputs, as well as #include<stdlib.h> for memory allocation... The stdio.h and stdlib.h header files are components of the libc library.
We avoid circular dependencies by ensuring that the sossy-crawler only records each visit between a pair of nodes only once future requests to visit the same pair of node are ignored.
Great visualization of the libc singleppoint of failure problem. The weighted graphs showing call frequency are particularly useful for risk assessment since not all dependencies carry equal criticality in practce. Would love to see how Sossy handles circular dependencies if they show up in more complex application ecosystems.
Thanks, yes from the visualization we see clearly how important the libc shared library is. However, this should not come as a surprise, pretty much every application written in C has a #include<stdio. h> somewhere in the source code for handling inputs and outputs, as well as #include<stdlib.h> for memory allocation... The stdio.h and stdlib.h header files are components of the libc library.
We avoid circular dependencies by ensuring that the sossy-crawler only records each visit between a pair of nodes only once future requests to visit the same pair of node are ignored.