|
|
|
|
|
by h4ck3r3l
3120 days ago
|
|
Well, the point of this microservice is to determine which service is supposed to listen on which given port (or vice-versa).
Sure, /etc/services can be edited locally, but that means the local administrator already knows such service-port-protocol mapping. And a conflict may occur later on at any OS package update.
Also, this microservice is intended to be queried from anywhere, especially from restricted systems (e.g., from Android devices) where it is not possible to access such admin configuration files.
Actually, this was developed out of a real need in one of the Android apps I'm working on: DD-WRT Companion |
|