Jump to content

jknoll

Moderators
  • Posts

    60
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by jknoll

  1. To those who have concerns about the security of updates to torrents, see this excerpt from BEP 39, to which I linked to in the introductory message.

    Basically, the first torrent in a chain must be signed, and all subsequent updates must be signed with the same cert. If you trust the originator, we interpret this to mean trust in updates from the same source.

    http://www.bittorrent.org/beps/bep_0039.html

    Because in many cases it's preferable for clients to be able to download new content without user interaction, the torrent pointed to by the feed URL should be signed. For a client to download new torrents automatically, they need to be signed by the torrent originator, who should be specified by an "originator" key within the info dict. The value of this key should be a byte string containing the originator's DER encoded X.509 certificate. See BEP 35 [1] for details regarding torrent signing.
  2. Thanks for the feedback, everyone. It looks like we have around 20 peers in the swarm and some valuable UI feedback. Please post if you have any other issues or questions.

    1. Compatibility to other clients - can any other BT client participate in that test now, either an earlier version of uTorrent or external?

    The torrent files are regular .torrent files with some new infodict keys (as specified in the BEPs), so other clients can download them, but the ability to poll for an update and the UI is unique to uTorrent 3.4. The 3.4 build AdamK supplied will give us the best feedback.

    2. Does libtorrent support this new feature, as a source for other clients to embed it?

    Not presently, though I suppose it could be added.

    3. Does this feature rely on the existing RSS feature and maybe is similar to it's existing smart-episodes-filter, and will any of those existing RSS related issues - get any attention as well anytime soon?

    It does not rely on the existing RSS feature. I'm not the right person to comment on future plans for RSS.

  3. Greetings uTorrent Forum,

    As Adam mentioned, I'm available to answer any questions you might have about this "updatable torrent" test. Please let me know if you have any questions or run into any difficulties. I'll monitor this forum for feedback.

    It's worth noting that the features we're testing are not limited to being used in "BitTorrent Bundles" — there are two related BEPs linked to below. We hope the ability to update a torrent file is a useful general purpose feature for the torrenting community, so please help us test even if you're not interested in BitTorrent Bundles. Thanks.

    http://bittorrent.org/beps/bep_0038.html

    http://bittorrent.org/beps/bep_0039.html

  4. @darkwedder First, please use http://web.utorrent.com/ instead. The http://falcon.utorrent.com/ hostname is deprecated. That doesn't explain your current problem, but you should do it anyway.

    You've downloaded and installed the µTorrent 3.0 Alpha and set up the "Web" (not "WebUI") preferences? When you filled out the username and password fields did it say "Registering" and then "Accessible"?

    I see no "darkwedder" in our database. If you're using another username and you don't wish to keep it secret, you can tell it to me and I can search for it for you to see if the system believes you've registered successfully.

  5. Thanks for the info. We've identified a bug where users will sometimes see the 401 errors when they attempt to login, even when they provide the correct username and password.

    We have a fix for the bug which is in testing right now. We'll update Falcon as soon as it passes.

    In testing, we see the 401's intermittently. Usually if we attempt to login a few times it will succeed. I haven't seen it happen consistently, as you describe.

    It happens for a known reason, when the random values used in SRP have certain properties. Thus it's random; you might never see it, or you might see it a few times in a row. In theory, you could see it every time, but it's highly unlikely. I'd recommend you retest after we fix the known bug, and if it's still not working we can try to reproduce what you're seeing.

    Thanks for your patience during the beta.

    EDIT:

    A fix for the 401 issue was pushed to Falcon this afternoon (2010-03-01). You should no longer see 401's except in cases where the username or password is actually incorrect. If you continue to see the issue, please clear your browser cache. If you still see it after that, let us know and we'll look into your case further.

  6. doug2h: If you send us an email at falcon@utorrent.com with your username we can "free" it to be re-associated with another system.

    To everyone who's been getting the "username already in use" error, we discovered a misconfiguration last week and corrected it. You should be able to connect if you'd been seeing this error. Please give it another shot, and thanks for your patience during the beta.

  7. @xatr0z, bykovk: I'm not sure why your uTorrent clients can't connect. I'll ask around to see if there's anything else we can ask you to help debug it. As for the web site, you definitely won't be able to log in with no client connected. You're right about the error message — the web form was showing the wrong description for some error conditions ("username not found"). This will be fixed in the next Falcon site release.

    @Lord Alderaan: Yes. 2.1 now supports multiple sessions. Each session uses a GUID cookie for identification, and each session has its own token (and AES key for Falcon).

    @ezmac1964: There's nothing special about the Falcon-compatible uTorrent which would prevent you from being able to run it in a VM.

    @cruiser78: We're working on mobile device support, but need to balance the privacy/encryption requirements of Falcon against their capabilities. For now, I'd recommend using the regular WebUI for your Windows Mobile phone and keeping an eye on Falcon.

    @SIRavecavec: Give it a try now, I've reset some of your user data. FYI, usernames are tied to a specific uTorrent client install, so you can't "move" your username from one computer to another, at least not without some settings.dat hacking.

  8. @revanmj: iPhone support (near term) and browse and upload a torrent (longer term) are both planned, but not supported right now because of our privacy requirements.

    @acmodeu, xatr0z: Are you still having the same problem? Can you browse to:

    http://falcon.utorrent.com/

    I've passed your report along to a client engineer. We'll report back with further questions or instructions.

    @ezmac1964: There's no Falcon-enabled Mac uTorrent as of now, and I can't comment on when or if one might become available.

  9. Shift,

    Okay, so you are able to get to raptor and get the expected certificate warning. That warning should not cause any problem for uTorrent, so it's not the cause of your issue. I'm looking into it further with one of the client engineers right now.

    Can you translate the Russian after "Proxy connect error:"?

    Have you set a proxy server in the Preferences > Connection > Proxy Server uTorrent pref panel?

    Do you know if your web browser routes requests through a proxy because of your ISP or school, etc?

×
×
  • Create New...