<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pounce, branch 1.0p2</title>
<subtitle>IRC bouncer
</subtitle>
<id>https://git.causal.agency/pounce/atom?h=1.0p2</id>
<link rel='self' href='https://git.causal.agency/pounce/atom?h=1.0p2'/>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/'/>
<updated>2019-12-09T01:43:56+00:00</updated>
<entry>
<title>Don't send self-PMs to the server</title>
<updated>2019-12-09T01:43:56+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-12-09T01:43:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=bb2db515dbeba6f2ece3aee3c8d5a81f385fd2e0'/>
<id>urn:sha1:bb2db515dbeba6f2ece3aee3c8d5a81f385fd2e0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Reference openssl(1) by absolute path</title>
<updated>2019-11-27T19:36:29+00:00</updated>
<author>
<name>edef</name>
<email>edef@edef.eu</email>
</author>
<published>2019-11-27T17:45:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=973f19b4fe73ef956fbb4eeaf963bbb83c926203'/>
<id>urn:sha1:973f19b4fe73ef956fbb4eeaf963bbb83c926203</id>
<content type='text'>
This still allows using openssl(1) from PATH, but defaults to using
${LIBRESSL_PREFIX}/bin/openssl.
</content>
</entry>
<entry>
<title>Simplify Linux.mk</title>
<updated>2019-11-27T05:16:53+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-11-27T05:16:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=b7dc2e3439a37d23d4847e130b37ece39b8efdd7'/>
<id>urn:sha1:b7dc2e3439a37d23d4847e130b37ece39b8efdd7</id>
<content type='text'>
This should just be what is definitely necessary, and all distros have
their own problems. This works on Void Linux at least.
</content>
</entry>
<entry>
<title>Don't always create ${ETCDIR}/rc.d</title>
<updated>2019-11-27T04:59:43+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-11-27T04:59:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=db65889605a2fa5352e90a573b7584a6b7a59dd5'/>
<id>urn:sha1:db65889605a2fa5352e90a573b7584a6b7a59dd5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Link calico with libcrypto on Linux</title>
<updated>2019-11-21T21:45:40+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-11-21T21:45:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=3051555d4e7975bcc05a9fef86b4016637a14832'/>
<id>urn:sha1:3051555d4e7975bcc05a9fef86b4016637a14832</id>
<content type='text'>
For the strlcpy implementation.
</content>
</entry>
<entry>
<title>Fix wordcmp return value when the words have differing lengths</title>
<updated>2019-11-21T21:26:43+00:00</updated>
<author>
<name>Michael Forney</name>
<email>mforney@mforney.org</email>
</author>
<published>2019-11-20T09:45:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=a17b38979617e8799da58be83699ea64dbed4503'/>
<id>urn:sha1:a17b38979617e8799da58be83699ea64dbed4503</id>
<content type='text'>
Otherwise, the result of strncmp gets converted size_t, since size_t
has greater rank than int.

Since wordcmp is only ever used as a boolean condition, this poses
no real issue, but presumably, it is meant to behave like the other
*cmp function and return a value less than, equal to, or greater
than 0 depending on the result of the comparison.
</content>
</entry>
<entry>
<title>Declare globals as extern in headers, and define in source file</title>
<updated>2019-11-21T21:26:37+00:00</updated>
<author>
<name>Michael Forney</name>
<email>mforney@mforney.org</email>
</author>
<published>2019-11-20T09:22:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=f4b0d09e3f782511b99626104ca960dd5decd4b8'/>
<id>urn:sha1:f4b0d09e3f782511b99626104ca960dd5decd4b8</id>
<content type='text'>
Otherwise, each source file that includes the header gets its own
definition, and according to the C standard (C99 6.9p5):

&gt; If an identifier declared with external linkage is used in an
&gt; expression (other than as part of the operand of a sizeof operator
&gt; whose result is an integer constant), somewhere in the entire
&gt; program there shall be exactly one external definition for the
&gt; identifier

Most compilers use the .bss section for zero data, but if it uses
.data instead, or if -Wl,--warn-common is used, this will cause a
linking error.
</content>
</entry>
<entry>
<title>Zero temporary SASL PLAIN buffer</title>
<updated>2019-11-21T21:26:08+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-11-21T21:26:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=407adf0ddd1be0b80de206d012b944b8113d02d2'/>
<id>urn:sha1:407adf0ddd1be0b80de206d012b944b8113d02d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use a static buffer for plainBase64</title>
<updated>2019-11-21T21:25:09+00:00</updated>
<author>
<name>C. McEnroe</name>
<email>june@causal.agency</email>
</author>
<published>2019-11-21T21:25:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=cb38ad54eb54c1b3d3f0adbcf7b60eb50d6a3394'/>
<id>urn:sha1:cb38ad54eb54c1b3d3f0adbcf7b60eb50d6a3394</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use a fixed buffer size for SASL PLAIN authentication</title>
<updated>2019-11-21T21:14:10+00:00</updated>
<author>
<name>Michael Forney</name>
<email>mforney@mforney.org</email>
</author>
<published>2019-11-20T09:13:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.causal.agency/pounce/commit/?id=113a33bdf883602313fa33fd323fe1af80b1c620'/>
<id>urn:sha1:113a33bdf883602313fa33fd323fe1af80b1c620</id>
<content type='text'>
handleAuthenticate only sends a single AUTHENTICATE message, so
according to https://ircv3.net/specs/extensions/sasl-3.1.html, its
maximum length is 399. So, we know that the authentication string
can be at most 299 bytes.
</content>
</entry>
</feed>
