summaryrefslogtreecommitdiff
path: root/toxencryptsave
AgeCommit message (Collapse)Author
2020-05-04Fix typo: `NAC_LIBS` -> `NACL_LIBS`.iphydf
This is working, so probably `NACL_LIBS` is entirely useless, but I can't be bothered to figure out what this was supposed to be, so here we are.
2020-05-02Add a check that we don't have any unused functions.iphydf
This check puts all of our code in a C++ anonymous namespace, which is effectively making all functions `static`. This allows the compiler to determine that a function is unused, so we can delete it.
2020-04-16Remove tokstyle exemptions from build files.iphydf
We put some tokstyle exemptions into the source files themselves, instead. This way we can check some of the code in those files, and more in the future when tokstyle supports more constructs (like apidsl). Also: hacked ping_array.api.h to not emit `_array` as parameter names. We'll need to fix apidsl to do this better. This works for now.
2020-03-14Use spdx license identifier instead of GPL blurb.iphydf
2018-10-09Consistently use camel case enum names.iphydf
Including in tests and implementation files.
2018-09-14Standardise header guards.iphydf
Using the full path including the repo name.
2018-08-26Update copyright to 2018.iphydf
2018-07-05Make tox.c unambiguously parseable.iphydf
Rules: 1. Constants are uppercase names: THE_CONSTANT. 2. SUE[1] types start with an uppercase letter and have at least one lowercase letter in it: The_Type, THE_Type. 3. Function types end in "_cb": tox_friend_connection_cb. 4. Variable and function names are all lowercase: the_function. This makes it easier for humans reading the code to determine what an identifier means. I'm not convinced by the enum type name change, but I don't know a better rule. Currently, a lot of enum types are spelled like constants, which is confusing. [1] struct/union/enum
2018-06-25Remove utils.c and utils.h from toxencryptsave build.iphydf
These were deleted earlier.
2018-06-25Fixes to the imported sodium sources to compile without warnings.iphydf
2018-05-20Move system header includes from network.h to network.ciphydf
2018-01-30Use nullptr as NULL pointer constant instead of NULL or 0.iphydf
This changes only code, no string literals or comments.
2018-01-28Avoid clashes with "build" directories on case-insensitive file systems.iphydf
2018-01-22Publish a single public BUILD target for c-toxcore.iphydf
2018-01-21Make BUILD files more finely-grained.iphydf
This allows us to precisely see which libraries depend on which and lets us split them up more, if necessary.
2018-01-18Use C99 standard in bazel builds.iphydf
2018-01-18Add bazel build scripts for c-toxcore.iphydf
This allows us and users to reproducibly build verified versions of the library with checksums. It will power the toktok-stack continuous build with checked-in checksums at specific git revisions.
2017-12-29Change toxencryptsave API to never overwrite pass keys.iphydf
2017-10-27Adjust docs of few toxencrypt function to the codeDiadlo
Add correct information about behaviour if input pointer is NULL Fix #590
2017-03-30Implement missing TES constant functions.iphydf
Fixes #503.
2017-01-19Update license headers and remove redundant file name comment.iphydf
"All rights reserved" was incorrect. The project was licensed under GPL3, which means a lot of rights are licensed to everybody in the world, i.e. not reserved to the "Tox Project".
2017-01-18Setup autotools to read .so version info from a separate fileSergey 'Jin' Bostandzhyan
We want to use the same libtool style .so versions in both build systems, ideally both systems should read the version information from the same configuration file. This commit introduces an so.version configuration file and sets up the autotools to use it. The version numbers in so.version define the ABI compatibility and should be updated prior to each release. implements #323
2017-01-12Clarify that the pass key `new` function can fail.iphydf
Also clarify that passwords can be empty or NULL.
2017-01-08Set up autotools build to build against vanilla NaCl.iphydf
Fixes #363.
2016-12-22Improve documentation of crypto_core.iphydf
2016-12-22Wrap all sodium/nacl functions in crypto_core.c.iphydf
2016-12-19Remove unused get/set salt/key functions from toxencryptsave.iphydf
2016-12-17docs(TES): correct docs to reflect how many bytes fns actually requireZetok Zalbavar
2016-12-14Fix unresolved reference in toxencryptsave API.iphydf
Also, make sure this won't happen again by checking for it in format-source.
2016-12-13Add apidsl file for toxencryptsave.iphydf
This breaks the toxencryptsave API. It hides the Tox_Pass_Key struct definition.
2016-12-09Improve toxencryptsave documentationMaxim Biro
2016-09-28v0.0.0 => v0.0.1Gregory Mullen (grayhatter)
2016-09-02Do not use `else` after `return`.iphydf
http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code
2016-09-01Sort #includes in all source files.iphydf
2016-08-31Add braces to all if statements.iphydf
2016-08-12Check code formatting on Travis.iphydf
We run astyle on Travis and check if there is a diff. The build terminates if git finds a difference.
2016-02-26Add missing files so that archive for make dist is completeRoman Yepishev
2016-02-13lets define this correctlly insteadGregory Mullen (GrayHatter)
2016-02-13added the dropped ;Gregory Mullen (GrayHatter)
2016-02-13added versioning to toxencryptsaveGregory Mullen (GrayHatter)
2016-01-30Fixes.irungentoo
Fixed bug from merged PR. Don't build useless files when building with libsodium.
2015-05-27Allow empty keys in toxencryptsave.irungentoo
2015-05-26These parameters should have been const.irungentoo
2015-04-01Merge branch 'master' of https://github.com/dubslow/toxcoreirungentoo
2015-04-01Enough pestering me pleaseDubslow
2015-03-31Make keys into a struct for more programmer safetyDubslow
2015-03-31Fix minor code duplicationDubslow
2015-03-31Merge branch 'master' of https://github.com/dubslow/toxcoreirungentoo
2015-03-31Fix toxencryptsave to be consistent with new_apiDubslow
Upon my own decision, the two tox_encryped_new convenience functions were removed due to basically needing two different sets of error codes. At iphydf's suggestion the corresponding tox_get_encrypted_savedata convenience functions were removed as well.
2015-03-26Making tox_encrypted_new() use the same error codes as tox_new was a bad idea.irungentoo
They now have their own error codes.