Исходное сообщение
"Во FreeBSD 13 чуть не оказалась халтурная реализация WireGua..." Отправлено Аноним, 27-Мрт-21 19:25
Ваши сведения протухли лет на 20. А так - вот вам! The first step was assessing the current state of the code the previous developer had dumped into the tree. It was not pretty. I imagined strange Internet voices jeering, “this is what gives C a bad name!” There were random sleeps added to “fix” race conditions, validation functions that just returned true, catastrophic cryptographic vulnerabilities, whole parts of the protocol unimplemented, kernel panics, security bypasses, overflows, random printf statements deep in crypto code, the most spectacular buffer overflows, and the whole litany of awful things that go wrong when people aren’t careful when they write C. Or, more simply, it seems typical of what happens when code ships that wasn’t meant to. It was essentially an incomplete half-baked implementation – nothing close to something anybody would want on a production machine. Полный оригинал - as seen by Wireguard dev - https://lists.zx2c4.com/pipermail/wireguard/2021-March/00649... - удачи в рассуждениях про качество...

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> Ваши сведения протухли лет на 20. А так - вот вам! > [code] > The first step was assessing the current state of the code the > previous > developer had dumped into the tree. It was not pretty. I imagined > strange Internet voices jeering, “this is what gives C a bad name!” > There were random sleeps added to “fix” race conditions, validation > functions that just returned true, catastrophic cryptographic > vulnerabilities, whole parts of the protocol unimplemented, kernel > panics, security bypasses, overflows, random printf statements deep in > crypto code, the most spectacular buffer overflows, and the whole litany > of awful things that go wrong when people aren’t careful when they > write > C. Or, more simply, it seems typical of what happens when code > ships > that wasn’t meant to. It was essentially an incomplete half-baked > implementation – nothing close to something anybody would want on a > production machine. > [/code] > Полный оригинал - as seen by Wireguard dev - https://lists.zx2c4.com/pipermail/wireguard/2021-March/006494.html > - удачи в рассуждениях про качество...
	Введите код, изображенный на картинке: