| Key | Value |
|---|---|
| FileName | ./etc/init/maas-pserv.conf |
| FileSize | 417 |
| MD5 | 0AD591CF3960EC2E70D7738B0C1BBF6B |
| SHA-1 | AC4A6B0C2D23C6A0ABEAB39257452E744BF33575 |
| SHA-256 | 03F67651FDEAA97014E94E7F89AAF4535CBD2AD56EEE559694D0EA7BDD7B4615 |
| SSDEEP | 12:A5BWchUmqMnFydwmeVTSWGJ0YBlwdBX5X0:OWYfFtbXz0 |
| TLSH | T17EE02B10F60C30FA870E00A37EE48788057E7F0D22AAA9001BB7604272E22BC22F0C10 |
| hashlookup:parent-total | 2 |
| hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| FileSize | 6544 |
| MD5 | 27D4793AD116E22D0FA4B465A80DDCC1 |
| PackageDescription | Ubuntu MAAS Cluster Controller Ubuntu MAAS Server is the successor to Orchestra. It offers a nice UI to provision your Ubuntu servers. Each physical server (“node”) will be commissioned automatically on first boot. During the commissioning process administrators are able to configure hardware settings manually before an automated smoke test and burn-in test are done. Once commissioned, a node can be deployed on demand by name, or allocated to a queue for dynamic allocation to services being deployed on this MAAS. . This package contains the cluster controller, which is responsible for controlling remote DHCP/TFTP instances on their own subnets. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | maas-cluster-controller |
| PackageSection | net |
| PackageVersion | 0.1+bzr1264+dfsg-0ubuntu2 |
| SHA-1 | 8A2A78A6FD78AD7CD263208EC1005730CA8DA2E3 |
| SHA-256 | 404209902F3402817E79C96265DE67FA7F208188ABA5B499083CF55A1D9C17B1 |
| Key | Value |
|---|---|
| CRC32 | E46A6C6D |
| FileName | maas_0.1+bzr482+dfsg-0ubuntu1_all.deb |
| FileSize | 7002920 |
| MD5 | 6CFBE66255A651388897A9841E384AC3 |
| OpSystemCode | 362 |
| PackageDescription | Ubuntu MAAS Server Ubuntu MAAS Server is the successor to Orchestra. It offers a nice UI to provision your Ubuntu servers. Each physical server (“node”) will be commissioned automatically on first boot. During the commissioning process administrators are able to configure hardware settings manually before an automated smoke test and burn-in test are done. Once commissioned, a node can be deployed on demand by name, or allocated to a queue for dynamic allocation to services being deployed on this MAAS. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | maas |
| PackageSection | net |
| PackageVersion | 0.1+bzr482+dfsg-0ubuntu1 |
| ProductCode | 187351 |
| RDS:package_id | 187351 |
| SHA-1 | 8F1D20FCC0BE288031E44B27E0F292A29DF448F3 |
| SHA-256 | 8946B2C7867F983DAD9E44D00504099BB048ED077DF577713E55F10590E87188 |
| SpecialCode | |
| db | nsrl_legacy |
| insert-timestamp | 1648586625.894019 |
| source | RDS_2022.03.1_legacy.db |