summaryrefslogtreecommitdiff
path: root/chat/libotr
AgeCommit message (Collapse)AuthorFilesLines
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-2/+2
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-02-13Update to version 3.0.0salo5-63/+12
From Jason White, via PR pkg/32451 Changes: - Support for OTR protocol version 2; will still interoperate with version 1 clients (though with a warning to the user), fixes identity-binding flaw http://www.cypherpunks.ca/otr/Protocol-v2-3.0.0.html
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-2/+4
2005-09-09remove "BUILDLINK_DEPMETHOD.libotr?= build", because dependinggdt1-2/+1
packages can dynamically link libotr and thus must depend on it. reviewed by wiz@
2005-07-30Added a patch to fix void* arithmetic.rillig2-1/+53
2005-07-27update to 2.0.2:gdt2-6/+6
* src/privkey.c (otrl_privkey_hash_to_human): Avoid writing a NUL one byte past the end of the buffer
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-25I put this package in security, not chat; update the buildlink file tonathanw1-2/+2
match.
2005-03-24Initial import of libotr-2.0.1.nathanw5-0/+86
This is the portable OTR Messaging Library, as well as the toolkit to help you forge messages. Off-the-Record (OTR) Messaging allows you to have private conversations over instant messaging by providing: Encryption No one else can read your instant messages. Authentication You are assured the correspondent is who you think it is. Deniability The messages you send do not have digital signatures that are checkable by a third party. Anyone can forge messages after a conversation to make them look like they came from you. However, during a conversation, your correspondent is assured the messages he sees are authentic and unmodified. Perfect forward secrecy If you lose control of your private keys, no previous conversation is compromised.