As BitlBee 3.0 is released and has now included OTR support :), I don’t have to maintain bitlbee-otr anymore. For FreeBSD, I noticed, the SRV DNS records lookup support is not compiled in by default, so I submitted a diff to upstream and the maintainer. For users of irc/bitlbee port, who want to try SRV lookup support can try the port diff.
Let me know if you experience any issues or have any questions.
Just finished integrating OTR support code from bitlbee-otr into bitlbee-1.2.8, and is available as bitlbee-otr-1.2.8.tar.bz2 (sha256sum: f09a88be7d995a0cc489ee9bea4ac49dc326c1b2e9396a8e7cc886b3894883a3 , md5sum: 1273e7861f393473c5060f5ec5d6c214). PR for FreeBSD port is not needed anymore. The tarball can be downloaded from:
Thanks to SourceForge and Veniamin (aka zloidemon) for hosting the tarball.
UPDATE: FreeBSD port irc/bitlbee-otr is updated.
Just finished integrating OTR support code from bitlbee-otr into bitlbee-1.2.7, and is available as bitlbee-otr-1.2.7.tar.bz2 (sha256sum: 2cb8817e98e5ac40dda1f3e8c7a76ae1ed421c265c85e2455c4f3080b9e99982, md5sum: 063d849c4011c599c4980eda87f0e0b4). PR for FreeBSD port needs to be submitted. The tarball can be downloaded from:
Thanks to SourceForge and Veniamin (aka zloidemon) for hosting the tarball.
UPDATE: The corresponding FreeBSD PR is ports/146666.
Just finished integrating OTR support code from bitlbee-otr into bitlbee-1.2.6, and is available as bitlbee-otr-1.2.6a.tar.bz2 (sha256sum: ab8bb786fcd34f87c4b8056b3786d896ee7aeae7fc21d09a49d3be920891c135, md5sum: 3419f352a8dfc06b1bd1954ddeb9ee34). The corresponding FreeBSD PR is ports/145911. The tarball can be downloaded from:
Thanks to SourceForge and Veniamin (aka zloidemon) for hosting the tarball.
Just finished integrating OTR support code from bitlbee-otr into bitlbee-1.2.5, and is available as bitlbee-otr-1.2.5.tar.bz2 (sha256sum: 93d283ff829decf6ee8c89d23f4ad441f3a6c24820bba8ea9580e738865bf605, md5sum: 26c20921ff586fcd5253a324f33bde1b). The corresponding FreeBSD PR is ports/144975. The tarball can be downloaded from:
Thanks to Veniamin (aka zloidemon) for hosting the tarball.
Anyone can become angry — that is easy; but to be angry with the right person, to the right degree, at the right time, for the right purpose and in the right way — that is not easy. — Aristotle
If you’re having problem capturing on any device with tcpdump. Then you can patch the libpcap with the diff at: http://github.com/mcr/libpcap/commit/8fa17a5a554aaeb85d3ec4118b45a31f1efd6808 and rebuild your libpcap package.
Happy sniffing on any device.
I’m using xterm in 256-color mode since a month. And I noticed that whenever I log in to any of the remote boxen (via ssh) from my xterm, I started getting WARNING: terminal is not fully functional, whenever I use less, screen, etc. curses applications. So this means xterm-256color (xterm in 256 color) terminfo is not available in the remote box. Now in most of the remote boxen, I don’t have superuser access, which means I can’t install this terminfo systemwide. So after going through terminfo(5) I figured out that I need to install this terminfo in my $HOME (at remote end) to get desired functionality. For that I did:
% ssh server mkdir -p .terminfo/x % scp /usr/share/terminfo/x/xterm-256color server:.terminfo/x/
Thats it. Now I don’t get that warning anymore and I can use Emacs/vim in 256-colors :) . What more do you want from 256-colors life…:)
weblog d'un abbe 