sledgehammer999 | 19 Dec 22:56 2014

Crashing on Mac OS X

I have a new packager for Mac OS X. He uses homebrew to build/package a
qbittorrent .dmg file.
There are 3 users that report crashing upon launch.
I link below the crash reports from those users. All seem to stem from
libtorrent. However I am not really sure if this is a libtorrent problem or
a compilation/linking/packaging problem. The packager cannot reproduce it
and I don't have access to Mac hardware.
IIRC you(arvid) develop on MAC. If it isn't too much trouble can you help
resolve this?

First 2 reports are with 0.16.17, the 3rd one is with 0.16.18
Report 1: http://pastebin.com/FDBXMvic
Report 2: http://pastebin.com/GgLryjWS
Report 3: http://pastebin.com/ih6WMykt
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
Heiko Becker | 19 Dec 12:30 2014

[PATCH] Fix build with LibreSSL >= 2.1.2

Hello,

attached is a patch that fixes building against libresll >= 2.1.2. Feel
free to modify it if necessary.

--

-- 
Best regards,
Heiko Becker
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Libtorrent-discuss mailing list
Libtorrent-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
Super SpaceMarines | 18 Dec 20:58 2014
Picon

Possibility of using libtorrent as a distributed data storage.

Hello libtorrent,

Our team here is trying to build a completely p2p serverless iphone/android
application for storing hashtables or data in a distributed fashion like
the way skype does or used to do. We are planning to use libtorrent.

Our goal is to store files(or any data) in a p2p fashion so that we could
just .put(data) into the network swarm so that we can later .get(dataID)
from the network swarm. In the meantime, data could be distributed to many
nodes (and kept for few days) so the probability of complete retrieval is
high at anytime after putting the data given a reasonably high churn rate
(because of mobiles).

Can this be done (or emulated using torrents) using libtorrent. it it
possible to just use the kademlia DHT part of libtorrent alone that does
exactly that to do this or is it achievable in any way at all? or are you
aware of any opensource MIT/BSD libraries out there that does this or
similar things.

Regarding the NAT traversal part, I read the previous mailing lists' answer
and using libtorrent+pwnat combination is it possible to achieve a
Skype-like unstoppable super-amazing NAT traversal or will it require more
patches to libtorrent to do it. and pwnat is a separate proxy server that
should be implemented as a central server correct?

Your reply would be really useful.
Thank You.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
(Continue reading)

Ramana Anand | 17 Dec 22:47 2014
Picon

libTorrent NAT traversal and its practical applications on Mobile phones.

Hello Everyone,

I came to know that libtorrent has built in support for NAT traversal, it
is awesome!. How practical is it to develop a libtorrent based application
for iphones and androids. aren't most mobiles behind a NAT therefore in a
mobile p2p say 99% of the peers will be NATted so how well would such a
system perform under libtorrent and are there any apps that already use
libtorrent on mobile? In real life, how many percent of them are truly
behind a NAT(in case my 99% assumption is wrong?).

Your reply would be really useful to me.
Thank You.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
Angel Leon | 18 Dec 03:44 2014
Picon

documentation typo fix patch

Here's a typo fix on the documentation related to file priorities.
https://github.com/gubatron/libtorrent/commit/b46cbc9a96874335aacf7a99ff99df412c4b5896.patch

Cheers,

Angel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
sledgehammer999 | 11 Dec 22:02 2014

Is no_connect_privileged_ports really that useful?

I finally used the extra info in the peer_block_alert(libtorrent v1.0x) to
see why each peer block happens. (qbittorrent log)

The vast majority happens because of privileged_ports. I read the
documentation of no_connect_privileged_ports. It doesn't really make sense
for me. This is supposed to be a security feature to not DDOS a peer (by
us).
Is it supposed to protect the remote peer? How and why? If the remote peer
has chosen to listen to a privileged port isn't this HIS problem? Or
possibly he knows what he's doing. Why are we supposed to protect him? (if
we assume that all bt clients used this library)

Unless the meaning of this setting is something else. Or unless there is a
DDOS situation that I can't imagine. Can you enlighten me?

Thank you.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
arvid | 7 Dec 07:58 2014
Picon
Picon

libtorrent 1.0.3 released (and 0.16.19)

You can download it from here:

   
http://sourceforge.net/projects/libtorrent/files/libtorrent/libtorrent-rasterbar-1.0.3.tar.gz/download

Here are the changes since 1.0.2:

1.0.3 release

	* python binding build fix for boost-1.57.0
	* add --enable-export-all option to configure script, to export all 
symbols
	  from libtorrent
	* fix if_nametoindex build error on windows
	* handle overlong utf-8 sequences
	* fix link order bug in makefile for python binding
	* fix bug in interest calculation, causing premature disconnects
	* tweak flag_override_resume_data semantics to make more sense (breaks
	  backwards compatibility of edge-cases)
	* improve DHT bootstrapping and periodic refresh
	* improve DHT maintanence performance (by pinging instead of full 
lookups)
	* fix bug in DHT routing table node-id prefix optimization
	* fix incorrect behavior of flag_use_resume_save_path
	* fix protocol race-condition in super seeding mode
	* support read-only DHT nodes
	* remove unused partial hash DHT lookups
	* remove potentially privacy leaking extension (non-anonymous mode)
	* peer-id connection ordering fix in anonymous mode
	* mingw fixes
(Continue reading)

Bedeho Mender | 6 Dec 10:35 2014
Picon

Connecting to a peer

Hi,

Whenever a new peer is added to the peer list of a torrent, as detected
through torrent_plugin::on_add_peer(), I want to try to connect to that
peer.

torrent::connect_to_peer(policy::peer* peerinfo, bool ignore_limit = false)

seems to do this, however regarding the peerinfo parameter

1) it has constructor peer(boost::uint16_t port, bool conn, int src), but
it is not clear what these arguments mean, and in particular if/how the
peer end point to connect to is present?

It does have an libtorrent::address member which is not part of the
constructor, should this be
set manually perhaps? if so, what else should be set to initiate a proper
bittorent connection?

2) Who owns the object? If user code should delete it, when can this be
done?

best
Bedeho
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
(Continue reading)

Jeff Waller | 5 Dec 06:40 2014
Picon

User Agent String

I think this was mentioned earlier, but changing from .16.x to 1.0.x causes the user_agent to set to a 
random block of data.  If set via session::set_settings, is there a new way, a new encoding that
must be followed?

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
Jeff Waller | 5 Dec 00:12 2014
Picon

Proactive seed

So the scenario is.

A client is running without any previous peer information.

It does have arbitrary outbound connectivity.

It is behind a firewall that does support outgoing sessions, no
incoming port forwarding, unknown/minimal upnp capabilities, 
and practically speaking can not be changed.

It has 1 torrent and is a seed.

It is the only seed.

There is no tracker (it uses the DHT).

The infoHash has been communicated out-of-band, and announced
through the DHT, so there are peers interested but they can
not contact the seed because of the firewall.

===================

Is there a way to make the seed proactive?  Push connections to the
peers.  Theoretically, it can get a list of peers using the DHT.  I saw
some reference to NAT holepunch mode, which seems like what this problem
is about, but didn’t see a why to turn it on.

I do have a workaround in mind, which is simply contact a known, alway
available peer for PEX info, but that really a workaround.  I’d like to
think through the best way.
(Continue reading)

arvid | 4 Dec 02:33 2014
Picon
Picon

Re: libtorrent: upnp permanent leases

On 2014-12-03 13:11, David Chappelle wrote:
> What would you consider to be public API in libtorrent? For example, if 
> I
> wanted to use libtorrent::upnp or libtorrent::natpmp directly outside 
> of
> the scope of a session would that be frowned upon or present any
> compatibility issues?

Anything with the TORRENT_EXPORT prefix is part of the public API.

prior to 1.0 this was not quite as well defined because only on windows
were other symbols hidden from DLLs.

Symbols with the TORRENT_EXPORT prefix are also all supposed to be 
documented
in the reference documentation.

upnp and natpmp used to be considered part of the public API (but only 
for
fringe uses). They no longer are and have been replaced by

   session::add_port_mapping
   session::delete_port_mapping

The reason to keep the public API small is partly simplicity and focus 
on
what libtorrent is supposed to do, but also to keep the binary size 
down.
When all symbols were exported (as is default on gcc and clang) lots of
symbols had names significantly longer than the code behind them (esp.
(Continue reading)


Gmane