{"action":"created","issue":{"url":"https://api.github.com/repos/abonander/buf_redux/issues/5","repository_url":"https://api.github.com/repos/abonander/buf_redux","labels_url":"https://api.github.com/repos/abonander/buf_redux/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/abonander/buf_redux/issues/5/comments","events_url":"https://api.github.com/repos/abonander/buf_redux/issues/5/events","html_url":"https://github.com/abonander/buf_redux/issues/5","id":309102221,"number":5,"title":"Avoid moving bytes to the beginning of the buffer","user":{"login":"gnzlbg","id":904614,"avatar_url":"https://avatars0.githubusercontent.com/u/904614?v=4","gravatar_id":"","url":"https://api.github.com/users/gnzlbg","html_url":"https://github.com/gnzlbg","followers_url":"https://api.github.com/users/gnzlbg/followers","following_url":"https://api.github.com/users/gnzlbg/following{/other_user}","gists_url":"https://api.github.com/users/gnzlbg/gists{/gist_id}","starred_url":"https://api.github.com/users/gnzlbg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gnzlbg/subscriptions","organizations_url":"https://api.github.com/users/gnzlbg/orgs","repos_url":"https://api.github.com/users/gnzlbg/repos","events_url":"https://api.github.com/users/gnzlbg/events{/privacy}","received_events_url":"https://api.github.com/users/gnzlbg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":29,"created_at":"2018-03-27T19:27:45Z","updated_at":"2018-04-23T08:35:22Z","closed_at":null,"author_association":"NONE","body":"Would it make sense to use something like the [slice_deque](https://github.com/gnzlbg/slice_deque) crate to avoid having to move bytes to the beginning of the buffer? \r\n\r\nIf that cannot be used due to a problem with the library, I'll be happy to try and fix it. I was looking for crates that could potentially benefit from `SliceDeque` since I am just trying to improve it for fun."},"comment":{"url":"https://api.github.com/repos/abonander/buf_redux/issues/comments/383497754","html_url":"https://github.com/abonander/buf_redux/issues/5#issuecomment-383497754","issue_url":"https://api.github.com/repos/abonander/buf_redux/issues/5","id":383497754,"user":{"login":"abonander","id":3198595,"avatar_url":"https://avatars1.githubusercontent.com/u/3198595?v=4","gravatar_id":"","url":"https://api.github.com/users/abonander","html_url":"https://github.com/abonander","followers_url":"https://api.github.com/users/abonander/followers","following_url":"https://api.github.com/users/abonander/following{/other_user}","gists_url":"https://api.github.com/users/abonander/gists{/gist_id}","starred_url":"https://api.github.com/users/abonander/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abonander/subscriptions","organizations_url":"https://api.github.com/users/abonander/orgs","repos_url":"https://api.github.com/users/abonander/repos","events_url":"https://api.github.com/users/abonander/events{/privacy}","received_events_url":"https://api.github.com/users/abonander/received_events","type":"User","site_admin":false},"created_at":"2018-04-23T08:35:22Z","updated_at":"2018-04-23T08:35:22Z","author_association":"OWNER","body":"The main concern with \"uninitialized\" memory is when it may have been cached by a userspace allocator after a free, so you could have confidential information in there that could leak if you fail to zero the buffer and then mistakenly read from it. It's one of those things you never think about until it gets a CVE and then everyone's asking why it happened in the first place. "}}
{"actor":{"display_login":"abonander"}}