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.
===> The following configuration options are available for pidgin-otr-4.0.2_3:
NLS=on: Native Language Support
===> Use 'make config' to modify these settings
accessibility/at-spi2-core: update to 2.46.0
What's new in at-spi2-core 2.46.0:
* Fix GetInterfaces documentation on org.a11y.atspi.Accessible
interface.
What's new in at-spi2-core 2.45.91:
* Send device event controller events using the same signature as other
events.
* Document the Accessible, Action, and Cache dbus interfaces.
* Fix license of atspi-gmain.c (#87).
What's new in at-spi2-core 2.45.90:
* xml: Add some documentation.
* xml: Fix event arguments.
(Only the first 15 lines of the commit message are shown above )
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
security/pidgin-otr: Update to 4.0.2
Changes:
- Fix use-after-free issue during SMP
- Updated Spanish, German, Norwegian Bokmal translations
- New Danish translation
- The Windows binary has been linked with updated versions of libotr,
libgcrypt, libgpg-error, and other supporting libraries
MFH: 2016Q1
Security: CVE-2015-8833
Security: http://www.vuxml.org/freebsd/77e0b631-e6cf-11e5-85be-14dae9d210b8.html
Part 2 of adding USE_GNOME=intltool to ports that require it.
The reason for this is that in the GNOME 3.16 update, USE_GNOME gtk20 and
gtk30 don't pull intltool in anymore.
PR: 201980
Exp-run by: antoine@
security/libgcrypt: 1.6.1 -> 1.6.2, bump depends
Changes:
- src/sexp.c (do_vsexp_sscan): Return error for invalid args.
- cipher/md.c (_gcry_md_info): Fix a segv in case of calling
with wrong parameters.
- cipher/primegen.c (_gcry_generate_elg_prime): Change to return an
error code, possible NULL deref in call to prime generator.
- cipher/dsa.c (generate): Take care of new return code.
- cipher/elgamal.c (generate): Change to return an error code. Take
care of _gcry_generate_elg_prime return code.
- ecc: Support the non-standard 0x40 compression flag for EdDSA.
- mpi: Extend the internal mpi_get_buffer.
- mpi: Fix regression for powerpc-apple-darwin detection.
- Fix bug inhibiting the use of the sentinel attribute in src/gcrypt.h.in
(Only the first 15 lines of the commit message are shown above )
Convert net-im/libpurple (and slave ports net-im/finch and net-im/pidgin)
to "USES=libtool tar:bzip2". Bump PORTREVISION on all dependent ports
and modernise them as well (USES, LIB_DEPENDS, staging).
audio/pidgin-musictracker:
- Replace LIBS with LDFLAGS.
- Disable static plugin.
net/online-desktop: Remove obsolete patches.
net-im/mbpurple:
- Drop pkgconf dependency.
- Replace post-patch with MAKE_ARGS.
- Use standard do-build.
(Only the first 15 lines of the commit message are shown above )
Throw my ports back in the pool, and make my intentions clear for the
various ports that I've created.
I bid fond fare well
A chapter closes for me
What opens for you?
Work around a problem on stable/[89] with libotr generating an
"undefined reference to `__stack_chk_fail_local'" error. None
of the usual remedies work (such as making sure that gcc is used
instead of ld for the linker) so on those releases we simply
disable that option.
pointyhat logs confirm that pidgin-otr (the only consumer of libotr
atm) is failing on 8 and 9 with the same configure error that I am
seeing on 8, so this patch should at least allow it to build on those
releases.
Bump PORTREVISION for libotr to err on the side of caution.
While I'm here, remove a now-spurious mod to the pidgin-otr configure.
Update libotr and pidgin-otr to 4.0.0
The main new features in 4.0.0:
* Support v3 of the OTR protocol
* The plugin now supports multiple OTR conversations with the same buddy
who is logged in at multiple locations. In this case, a new OTR menu
will appear, which allows you to select which session an outgoing
message is indended for. Note that concurrent SMP authentications with
the same buddy who is logged in multiple times is not yet supported
(starting a second authentication will end the first).
* During a private conversation with a buddy, an incoming unencrypted
message will now trigger the regular incoming message notifications.
(Only the first 15 lines of the commit message are shown above )
Revert the unauthorized conversion of pkg-config from a proper build dep
to the new macro (r301539). Convert pkg-config to pkgconf.
Add a build dep on pkgconf to pidgin-otr to handle libotr's .pc files
Versions 3.2.0 and earlier of the pidgin-otr plugin contain
a format string security flaw. This flaw could potentially be
exploited by a remote attacker to cause arbitrary code to be
executed on the user's machine.
The flaw is in pidgin-otr, not in libotr. Other applications
that use libotr are not affected.
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Update to version 3.2.0, released June 15th. The configuration and
"OTR button" functionality have been moved to a menu. Also, "Buddy
authentication has been revamped, based on the user study published
in SOUPS 2008." The old authentication methods are still allowed.
This version adds locale files for ar, de, hu, and ru.
Drop the specific library version number for libpurple to
(hopefully) avoid churn down the road.
Assume maintainership, and add my website to MASTER_SITES.
Approved by: Maintainer timeout
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
1. Update to 3.1.0
2. Update the MASTER_SITES
3. Add a verify target for the PGP signature, and download the signature
4. Add USE_GMAKE
5. Add an unconditional USE_GETTEXT since there is no way to disable it
6. Update pkg-plist with the *.mo files
Approved by: maintainer timeout
PR: ports/115664 (pkg-plist fix)
Submitted by: Matthias Andree <matthias.andree@gmx.de>