You can subscribe to this list here.
| 2002 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(28) |
Nov
(89) |
Dec
(37) |
| 2008 |
Jan
(78) |
Feb
(37) |
Mar
(21) |
Apr
(3) |
May
(10) |
Jun
(3) |
Jul
(13) |
Aug
(7) |
Sep
(9) |
Oct
(3) |
Nov
(4) |
Dec
|
| 2009 |
Jan
(2) |
Feb
(7) |
Mar
(16) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(8) |
Sep
|
Oct
(5) |
Nov
(4) |
Dec
(1) |
| 2010 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2012 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2026 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Schimon <ss...@ai...> - 2026-05-05 05:34:19
|
Greetings. My name is Schimon, and I develop XMPP software. I am interested to compile an XEP to integrate ADC with XMPP. Currently, it is recmmended to utilize URI links that are not of XMPP (e.g. Magnet Link) with XEP-0066: Out of Band Data. However, because both platforms are based upon XML, I think that an XEP which be specifically of ADC be of a significant value. Please advise. Kind regards, Schimon |
|
From: Schimon <ss...@ai...> - 2026-05-05 02:56:17
|
Greetings. My name is Schimon, and I develop a publication platform which is intended to be integrated with PPN. I am interested to know of the URI and hash types of ADC and DC. Please advise. Kind regards, Schimon |
|
From: emtee11 <em...@gm...> - 2022-09-19 12:50:46
|
hi translators, translation templates for the upcoming DC++ 0.880 have been updated on <https://translations.launchpad.net/dcplusplus>. <https://translations.launchpad.net/dcplusplus>.> changelog: <https://sourceforge.net/p/dcplusplus/code/ci/default/tree/changelog.txt> <https://sourceforge.net/p/dcplusplus/code/ci/default/tree/changelog.txt>> feel free to drop by the dcdev hub at <adcs://hub.dcbase.org:16591 <http://hub.dcbase.org:16591>> for any clarification / pre-release build. emtee |
|
From: poy <po...@12...> - 2018-11-25 22:49:16
|
hi, the DC++ website <http://dcplusplus.sourceforge.net/> includes Google Analytics tracking in most of its pages. the obvious plus side is we get to gather stats about people interested in DC++, though we seldom (if ever?) actually use them in any meaningful way. the negative side: our users feel unwelcome. they simply want to know about DC++ yet they are forced to participate into data collection by a company whose main revenue comes from that data. in the spirit of championing freedom, I would like our website to stop exploiting its users by removing Google Analytics tracking. I know this sounds like I have drunk too much RMS-kool-aid but I am simply echoing what I have been hearing more & more lately in free software (or simply just developer) conventions. curious to know what you guys think about this. poy |
|
From: poy <po...@12...> - 2018-11-06 19:43:35
|
hi translators, translation templates for the upcoming DC++ 0.868 have been updated on <https://translations.launchpad.net/dcplusplus>. changelog: <https://sourceforge.net/p/dcplusplus/code/ci/default/tree/changelog.txt> feel free to drop by the dcdev hub at <adcs://hub.dcbase.org:16591> for any clarification / pre-release build. poy |
|
From: poy <po...@12...> - 2016-09-06 20:38:37
|
Hello friends, It's been a while! DC++ 0.860 is nearly ready; translation templates on <https://translations.launchpad.net/dcplusplus> have been updated. They will be extracted from launchpad and included into DC++ on Sept 14th. Changelog: <https://sourceforge.net/p/dcplusplus/code/ci/default/tree/changelog.txt> Test builds: <https://builds.dcbase.org/> Thanks for helping out with the translations! poy |
|
From: poy <po...@12...> - 2015-03-22 20:11:27
|
hey, DC++ translations on <https://translations.launchpad.net/dcplusplus> are being updated for a release of DC++ 0.851 in about 1 week. poy |
|
From: poy <po...@12...> - 2015-02-05 19:52:40
|
:) -------- Forwarded Message -------- Subject: Congratulations! Your project is a Project of the Week on SourceForge! Date: Thu, 5 Feb 2015 11:07:48 -0800 From: Elizabeth Daniels <eda...@sl...> To: sfcommunity <com...@so...> Hello, My name is Elizabeth Daniels and I am the senior content editor for SourceForge. I am writing to inform you that your project is a featured Project of the Week and will be listed on the front page of our site next week. This means your project may be included in this month's Community Project of the Month vote, depending on the number of downloads it gets. Projects are chosen based on a variety of considerations, such as recent releases, interesting blog activity, or other related things. Front page features tend to result in increased traffic to your project page so you may want to take this opportunity to make sure you have the latest project description, screenshots, and project logo. And, here is the link (/*that will go live Monday*/) to the blog post notifying the community of your accomplishment: http://sourceforge.net/blog/projects-of-the-week-february-9-2015 Here are all of the Projects of the Week for February 9, 2015: taskcoach <https://sourceforge.net/projects/taskcoach/> dcplusplus <https://sourceforge.net/projects/dcplusplus/> simutrans <https://sourceforge.net/projects/simutrans/> texstudio <https://sourceforge.net/projects/texstudio/> gns-3 <https://sourceforge.net/projects/gns-3/> ipcop <https://sourceforge.net/projects/ipcop/> tencoder <https://sourceforge.net/projects/tencoder/> librecad <https://sourceforge.net/projects/librecad/> kmeleon <https://sourceforge.net/projects/kmeleon/> Thanks for being part of the SourceForge community! And best of luck. -- Elizabeth Daniels Senior Content Editor SourceForge.net <http://sourceforge.net> | 415.713.0229 |
|
From: poy <po...@12...> - 2015-01-11 20:46:48
|
Hey,
I will now be using the following compilers to build DC++.
poy
-------- Original Message --------
Subject: [Mingw-w64-public] [Project News|New Builds]
Date: Mon, 22 Dec 2014 10:19:09 +0300
From: niXman <i.n...@au...>
Reply-To: min...@li...
To: mingw-w64-public <min...@li...>
Hi,
Builds of MinGW-W64 based on GCC-4.9.2 is updated.
MinGW-w64 is updated to a7568802417737ace73abfe12a682d1b6481a0d0
Links:
32-bit:
[...]
win32-dwarf:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-win32/dwarf/i686-4.9.2-release-win32-dwarf-rt_v3-rev1.7z
64-bit:
[...]
win32-seh:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/seh/x86_64-4.9.2-release-win32-seh-rt_v3-rev1.7z
--
Regards, niXman
|
|
From: poy <po...@12...> - 2015-01-04 22:51:38
|
Hey, Translations on <https://translations.launchpad.net/dcplusplus> have been updated in preparation for a release of DC++ due very soon. Please update the languages you can handle! :) poy |
|
From: poy <po...@12...> - 2014-03-23 22:37:18
|
Hey translators, Translation templates on <https://translations.launchpad.net/dcplusplus/trunk> have been updated in preparation for a release of DC++ 0.840 at the end of the week. Enjoy! poy |
|
From: poy <po...@12...> - 2014-03-23 22:25:32
|
Hey, The DC++ code repository has been migrated from Bazaar to Mercurial and is now available at <http://sourceforge.net/p/dcplusplus/code/>. poy |
|
From: poy <po...@12...> - 2014-03-03 20:18:12
|
Hey,
I will be using the following compilers from now on.
poy
-------- Original Message --------
Subject: [Mingw-w64-public] [Project News | New Builds]
Date: Tue, 07 Jan 2014 22:16:05 +0400
From: niXman <i.n...@au...>
Reply-To: min...@li...
To: mingw-w64-public <min...@li...>
Hi,
Builds based on the GCC-4.8.2 rebuilded due to winpthreads bug[1].
Links:
32-bit:
win32-dwarf:
i686-4.8.2-release-win32-dwarf-rt_v3-rev2.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-win32/dwarf/i686-4.8.2-release-win32-dwarf-rt_v3-rev2.7z)
64-bit:
win32-seh:
x86_64-4.8.2-release-win32-seh-rt_v3-rev2.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-win32/seh/x86_64-4.8.2-release-win32-seh-rt_v3-rev2.7z)
[1] https://sourceforge.net/p/mingw-w64/bugs/373/
--
Regards, niXman
|
|
From: poy <po...@12...> - 2013-09-16 19:15:52
|
Hi translators, The templates on <https://translations.launchpad.net/dcplusplus> are being updated for a release of DC++ 0.830 at the end of the week if all goes well. As usual, test builds are available on <http://builds.dcbase.org> and the dev hub is at <adcs://hub.dcbase.org:16591> should you have any question regarding the new features. Enjoy, poy |
|
From: poy <po...@12...> - 2013-07-19 17:05:23
|
Hi translators, Strings on <https://translations.launchpad.net/dcplusplus> have been updated for an imminent release of DC++ 0.828 (around next week). There is only 1 new string in libdcpp (a typo that has been corrected) and a few more in dcpp-help. poy |
|
From: poy <po...@12...> - 2013-05-13 19:14:16
|
Hey translators, The release of DC++ 0.820 is getting close; translation templates on <https://translations.launchpad.net/dcplusplus> have been updated to that end. You have about a week to translate before the release. Should you want to experience the new changes, test builds of DC++ are available on <http://builds.dcbase.org/>. poy |
|
From: poy <po...@12...> - 2013-01-22 17:31:19
|
Hi translators, Translation templates on <https://translations.launchpad.net/dcplusplus> are being updated for a release of DC++ 0.810 around next week. Test builds are available on <http://builds.dcbase.org/?dir=dcpp> if you want to see the upcoming changes in detail. Enjoy, poy |
|
From: poy <po...@12...> - 2012-09-09 15:21:48
|
hey translators, translation templates on <https://translations.launchpad.net/dcplusplus> have been updated in preparation of a release of DC++ 0.800 around next week. <http://builds.dcbase.org/?dir=dcpp> has snapshots that should be close enough to the upcoming release if you want to try your changes. thanks in advance for your contributions, poy |
|
From: poy <po...@12...> - 2012-04-12 16:24:49
|
Hi, DC++ 0.797 is around the corner and should be released next week. Translation templates on <https://translations.launchpad.net/dcplusplus/trunk> have been updated (27 new strings over DC++ 0.791); you can start translating right away! The dev hub is at <adcs://hub.dcbase.org:16591> if you have any question or want test builds to see what's new. poy |
|
From: klondike <klo...@kl...> - 2012-03-04 03:38:53
|
Hi, For now and thanks to Lanowen inspiration I'll propose an improvement over the current password storage scheme based on how tiger processes data that allows storage of unpadded encrypted passwords from which the only guessable data is the password length. The current state of art is as follows: S tells C GPA randomdata (at least 24 byte long) C tells S PAS base32(h(password|randomdata)) S calculates h(password|randomdata) and checks if it matches. This basically means that we have to either store the password in plain text to be able to check the value of the hash or keep random data constant and force a particular session hash in order to check the password allowing for replays. What we can do when h is the tiger algorithm is instead pad the password with enough data, which we'll call salt or S, to make a whole number of blocks (for example for an 16 character password this means 48 bytes of data) and store the result of the first iterations of tiger_block over said blocks along with this random data and the total number of iterations done. To prevent dictionary attacks we must ensure that salt is long enough (for example 16 bytes). Thus the protocol will work as follows: S tells C GPA salt|randomdata (at least 24 byte long) C tells S PAS base32(tiger2(password|randomdata)) S calculates tiger2(res,its,randomdata) and checks if it matches. Where tiger2 is a special implementation using res as initial values and adding its to the message length used for padding. For efficiency reasons randomdata shouldn't be longer than 55 bytes which ensures that no extra blocks are added when padding making hashing faster. Now the question is, what vulnerabilities does this proposal have? Well, since salt is constant along connections a passive eavesdropper may be able to guess the length of the password (modulo 64) by looking at which bytes on the GPA command are constant. Similarly somebody with access to the password database can know the exact password length by looking at the values of S and its. Obviously since passwords longer than 64 bytes are rare this usually means the eavesdropper can know the exact password size which can make dictionary attacks slightly easier against unsecure passwords by limiting the passwords to those of that fixed length. Please note that even when using a random data the attacker can still use dictionary attacks but they may be a bit harder since the password length will be unknown. So well, this still means we need something safer for password based authentication that allows the server to store the data in an unusable (for the attacker) state and ensure zero knowledge password proof is used for safety reasons, in my case my propossal is SRP with PBKDF2 though I'd like to hear some discussion. Yet for now and whilst we get this safer method into ADC (and wait for clients and servers to support it) we can use this proposal here to keep the passwords stored in an encrypted state (though usable for authentication against the server if guessed) whilst minimizing the amount of information we give to a passive eavesdropper. And now as usual, DISCLAIMER: Usually attacks on hashing functions tend to be independent from the padding used on the last block but this doesn't means attacks against the unpadded hash function are unexistant thus if any appears against unpadded tiger as used here don't say you weren't warned. |