|
Bugzilla – Full Text Bug Listing |
| Summary: | Support store/forward and relay only to another logsrvd server | ||
|---|---|---|---|
| Product: | Sudo | Reporter: | Tyler <tyler.reese> |
| Component: | Log server | Assignee: | Todd C. Miller <Todd.Miller> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | mehmetgelisin |
| Priority: | low | ||
| Version: | 1.9.5 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Attachments: | logsrvd chaining example | ||
Initial support for store-and-forward relaying has been committed. Still missing is a periodic check for existing logs that need to be forwarded. Fixed in sudo 1.9.7 |
Created attachment 552 [details] logsrvd chaining example As a user I would like to have logsrvd store an IOlog and then forward that connection to another logsrvd server so I can have my IOlogs in two different places. As a user I would like to have logsrvd relay, without any storage, of an IOlog session to another logsrvd instance so I can have one egress point for all my IOlog forwarding. One real world use case is wanting to log EC2/Virtual Machine instances that are on a private network. By configuring logsrvd in this manner you could forward IOlogs from a sudo client on private subnet to a logsrvd instance on a public subnet to collect the iologs. Then forward those to another service that is running logsrvd that can store and analyze those files. See attached graphic.