Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Replace dataenc with sandi. | Magnus Therning | 2015-05-07 |
| | | | | | | The library dataenc is unmaintained and has been superseded by sandi. Signed-off-by: Magnus Therning <magnus@therning.org> | ||
* | metadata: Fix encoding problem that led to mojibake when storing metadata ↵ | Joey Hess | 2015-03-04 |
| | | | | | | | | | | | | | | | | | | | | | | | | | strings that contained both unicode characters and a space (or '!') character. The fix is to stop using w82s, which does not properly reconstitute unicode strings. Instrad, use utf8 bytestring to get the [Word8] to base64. This passes unicode through perfectly, including any invalid filesystem encoded characters. Note that toB64 / fromB64 are also used for creds and cipher embedding. It would be unfortunate if this change broke those uses. For cipher embedding, note that ciphers can contain arbitrary bytes (should really be using ByteString.Char8 there). Testing indicated it's not safe to use the new fromB64 there; I think that characters were incorrectly combined. For credpair embedding, the username or password could contain unicode. Before, that unicode would fail to round-trip through the b64. So, I guess this is not going to break any embedded creds that worked before. This bug may have affected some creds before, and if so, this change will not fix old ones, but should fix new ones at least. | ||
* | update my email address and homepage url | Joey Hess | 2015-01-21 |
| | |||
* | relicense general utility library code to BSD | Joey Hess | 2014-05-10 |
| | | | | | Omitted a couple of files what have had significant contributions from others. | ||
* | allow to build when sandi is installed (don't use it yet) | Joey Hess | 2013-11-11 |
| | |||
* | tag xmpp pushes with jid | Joey Hess | 2013-03-06 |
| | | | | | | | | | | This fixes the issue mentioned in the last commit. Turns out just collecting UUID of clients behind a XMPP remote is insufficient (although I should probably still do it for other reasons), because a single remote repo might be connected via both XMPP and local pairing. So a way is needed to know when a push was received from any client using a given XMPP remote over XMPP, as opposed to via ssh. | ||
* | finished where indentation changes | Joey Hess | 2012-12-13 |
| | |||
* | rename | Joey Hess | 2011-07-05 |