You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
(273) |
May
(271) |
Jun
(173) |
Jul
(108) |
Aug
(163) |
Sep
(232) |
Oct
(251) |
Nov
(116) |
Dec
(104) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(223) |
Feb
(117) |
Mar
(80) |
Apr
(31) |
May
(43) |
Jun
(103) |
Jul
(90) |
Aug
(21) |
Sep
(26) |
Oct
(5) |
Nov
(7) |
Dec
(11) |
2005 |
Jan
(6) |
Feb
(5) |
Mar
(37) |
Apr
(4) |
May
(30) |
Jun
(7) |
Jul
(6) |
Aug
(6) |
Sep
(4) |
Oct
(11) |
Nov
(5) |
Dec
(2) |
2006 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
(14) |
2007 |
Jan
|
Feb
(8) |
Mar
(18) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
(22) |
Sep
(7) |
Oct
(19) |
Nov
(8) |
Dec
(2) |
2008 |
Jan
|
Feb
|
Mar
(17) |
Apr
(8) |
May
(3) |
Jun
(13) |
Jul
(9) |
Aug
(19) |
Sep
(4) |
Oct
(12) |
Nov
(8) |
Dec
(1) |
2009 |
Jan
|
Feb
|
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
(8) |
Aug
(27) |
Sep
(37) |
Oct
(35) |
Nov
(9) |
Dec
(16) |
2010 |
Jan
(48) |
Feb
(3) |
Mar
|
Apr
(5) |
May
(2) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(20) |
Nov
|
Dec
|
2011 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Zhouyang J. <jia...@gm...> - 2018-02-27 12:33:27
|
Hi, I found more potential API (including chdir, fopen, listen, pipe and socket) bugs, which may cause bad results like crash due to the lack of proper error handling. Attached please find the patch against version 0.6.3 :) 2017-08-04 11:56 GMT+08:00 Philip Tellis <phi...@gm...>: > On 3 August 2017 at 23:50, Zhouyang Jia <jia...@gm...> wrote: > > > I'm new to Ayttm, I analyzed the source code and found two potential > bugs that may cause crashes. > > Welcome to the project, and thanks for looking into this. > > > 1. In ayttm-0.6.3/modules/utility/custom_message.c:158:7, if "open" > failed to open "custom_away_msg", "read" would cause a crash since "fd" is > -1. > > > > 2. In ayttm-0.6.3/libproxy/ssl.c:93:12, if "SSL_CTX_new" failed to > initialize the SSL context, "SSL_CTX_set_default_verify_paths" would > cause a crash since "ssl_ctx" is null. > > > > I think it's unsafe to assume that the library functions would be > correct. It would be better if we could handle the errors properly. > > You're correct, and I've reviewed both your patches and they appear to be > good. > > @Siddhesh, would you be able to merge these in? I'm temporarily away from > my box with the necessary credentials. > > Philip > |
From: Philip T. <phi...@gm...> - 2017-08-04 03:56:31
|
On 3 August 2017 at 23:50, Zhouyang Jia <jia...@gm...> wrote: > I'm new to Ayttm, I analyzed the source code and found two potential bugs that may cause crashes. Welcome to the project, and thanks for looking into this. > 1. In ayttm-0.6.3/modules/utility/custom_message.c:158:7, if "open" failed to open "custom_away_msg", "read" would cause a crash since "fd" is -1. > > 2. In ayttm-0.6.3/libproxy/ssl.c:93:12, if "SSL_CTX_new" failed to initialize the SSL context, "SSL_CTX_set_default_verify_paths" would cause a crash since "ssl_ctx" is null. > > I think it's unsafe to assume that the library functions would be correct. It would be better if we could handle the errors properly. You're correct, and I've reviewed both your patches and they appear to be good. @Siddhesh, would you be able to merge these in? I'm temporarily away from my box with the necessary credentials. Philip |
From: Zhouyang J. <jia...@gm...> - 2017-08-04 03:50:19
|
Hi, I'm new to Ayttm, I analyzed the source code and found two potential bugs that may cause crashes. 1. In ayttm-0.6.3/modules/utility/custom_message.c:158:7, if "open" failed to open "custom_away_msg", "read" would cause a crash since "fd" is -1. 2. In ayttm-0.6.3/libproxy/ssl.c:93:12, if "SSL_CTX_new" failed to initialize the SSL context, "SSL_CTX_set_default_verify_paths" would cause a crash since "ssl_ctx" is null. I think it's unsafe to assume that the library functions would be correct. It would be better if we could handle the errors properly. Attached please find the patches against version ayttm-0.6.3. Hopefully, they can solve these potential bugs. Best, Zhouyang |
From: Philip T. <phi...@gm...> - 2016-03-30 15:29:03
|
On 30 Mar 2016 10:43 a.m., "Detlef Graef" <det...@ya...> wrote: > > The following happens, described (simplified) in own words: > > > DNS query: vcs2.msg.yahoo.com type A ipv4 > DNS query: vcs2.msg.yahoo.com type AAAA ipv6 > > http request to: http://vcs2.msg.yahoo.com/capacity > > http Response: > COLO_CAPACITY=1 > CS_IP_ADDRESS=66.196.114.227 > > new tcp session to: 66.196.114.227 destination port 5050 > [snip] > > The difference seems to be in the http://vcs2.msg.yahoo.com/capacity > request. Connection to port 5050 is made to the ip address from > http://vcs2.msg.yahoo.com/capacity > Yes, it looks like they are now doing load balancing via the first request. This probably explains why you got a 999 by connecting to SCS. Changes will have to be made in libyahoo2, and if you do make those changes, then also submit them to the libyahoo2 project. Thanks for investigating. Philip |
From: Philip T. <phi...@gm...> - 2016-03-21 20:14:42
|
On 21 March 2016 at 15:23, Detlef Graef <det...@ya...> wrote: > > I have to run the configure script with the option > "--enable-posix-dlopen" then the build is successfull. > > At the moment I cannot connect to yahoo, I get the error code 999. > > Error code 999 from Yahoo could mean that you're being blocked as a bot or a potential DoS threat. Try comparing ayttm's packets with the official Yahoo! Messenger packets/ports/hosts, etc. |
From: Philip T. <phi...@gm...> - 2016-03-20 16:23:42
|
On 20 March 2016 at 10:28, Detlef Graef <det...@ya...> wrote: > > It seems PLUGIN_SO_EXT is not set properly in the file plugin.h for my > build environment. [snip] > > I will try to find the root cause. Thanks for trying to get to the bottom of this. I currently don't have access to a system where I can test it out easily, so will have to rely on your help :) Philip -- hello world |
From: Philip T. <phi...@gm...> - 2015-08-24 16:58:04
|
Ok, I've looked through the code, and these are my findings: 1. The code should have been inside an #ifdef block, but for some reason it is inside a #ifndef block, which inverts the meaning of the condition. 2. The snprintf and debug_print statements should really just be merged into a single statement with no actual need for debug_buff Unfortunately this code dates back to the very first revision, so it probably inherited from "everybuddy", but I don't have the time to go into the cvs history for EB. I've fixed this and hope someone can test it thoroughly. Philip |
From: Philip T. <phi...@gm...> - 2015-08-22 21:10:02
|
I'll look into it... Might also move to github. Makes contributions much easier. On 22 Aug 2015 4:51 pm, "Kaleb" <dj...@gm...> wrote: > > Considering the last commit was dated 2011-12-15 03:07:28, I doubt anything will be changed. > > It would be cool if somebody were to pick this back up, but I don't see it happening. > > On Sat, Aug 22, 2015 at 4:24 PM, Kapil Anand <kap...@gm...> wrote: >> >> Hi, >> >> I work in information flow analysis of programs and my analysis gave a possible warning with respect to format string vulnerability in ayttm. I had pointed out this behaviour earlier, so wanted to check whether code base has been modified to fix this vulnerability. >> >> Function "http_connect" populates "debug_buff" through "inputline". "inputline" is populated through an external "recv" command. "debugf" is passed directly to printf without a format string. >> >> >> Code: (in http_connect) >> >> //Populates inputine through recv call >> ay_recv_line(sockfd,&inputline) >> >> //Moves inputline to debug_buff >> snprintf(debug_buff, sizeof(debug_buff), <%s\n",inputline); >> >> >> //Passes to debug_print a.k.a printf >> debug_print(debug_buff) >> >> Our analysis flagged this behavior. >> >> However, we are not sure whether ayttm developers are aware of this behaviour. This might very well be a false positive. We just wanted to confirm our analysis. >> >> Any response in this regard will be appreciated. >> >> Thanks >> >> Regards, >> Kapil >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Ayttm-users mailing list >> Ayt...@li... >> https://lists.sourceforge.net/lists/listinfo/ayttm-users >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Ayttm-users mailing list > Ayt...@li... > https://lists.sourceforge.net/lists/listinfo/ayttm-users > |
From: Kaleb <dj...@gm...> - 2015-08-22 20:50:56
|
Considering the last commit was dated 2011-12-15 03:07:28, I doubt anything will be changed. It would be cool if somebody were to pick this back up, but I don't see it happening. On Sat, Aug 22, 2015 at 4:24 PM, Kapil Anand <kap...@gm...> wrote: > Hi, > > I work in information flow analysis of programs and my analysis gave a > possible warning with respect to format string vulnerability in ayttm. I > had pointed out this behaviour earlier, so wanted to check whether code > base has been modified to fix this vulnerability. > > Function "http_connect" populates "debug_buff" through "inputline". > "inputline" is populated through an external "recv" command. "debugf" is > passed directly to printf without a format string. > > *Code: (in http_connect)* > > *//Populates inputine through recv call* > *ay_recv_line(sockfd,&inputline)* > > *//Moves inputline to debug_buff* > *snprintf(debug_buff, sizeof(debug_buff), <%s\n",inputline); * > > > *//Passes to debug_print a.k.a printf* > *debug_print(debug_buff)* > > Our analysis flagged this behavior. > > However, we are not sure whether ayttm developers are aware of this > behaviour. This might very well be a false positive. We just wanted to > confirm our analysis. > > Any response in this regard will be appreciated. > > Thanks > > Regards, > Kapil > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Ayttm-users mailing list > Ayt...@li... > https://lists.sourceforge.net/lists/listinfo/ayttm-users > > |
From: Kapil A. <kap...@gm...> - 2015-08-22 20:25:20
|
Hi, I work in information flow analysis of programs and my analysis gave a possible warning with respect to format string vulnerability in ayttm. I had pointed out this behaviour earlier, so wanted to check whether code base has been modified to fix this vulnerability. Function "http_connect" populates "debug_buff" through "inputline". "inputline" is populated through an external "recv" command. "debugf" is passed directly to printf without a format string. *Code: (in http_connect)* *//Populates inputine through recv call* *ay_recv_line(sockfd,&inputline)* *//Moves inputline to debug_buff* *snprintf(debug_buff, sizeof(debug_buff), <%s\n",inputline); * *//Passes to debug_print a.k.a printf* *debug_print(debug_buff)* Our analysis flagged this behavior. However, we are not sure whether ayttm developers are aware of this behaviour. This might very well be a false positive. We just wanted to confirm our analysis. Any response in this regard will be appreciated. Thanks Regards, Kapil |
From: David B. <dc...@ho...> - 2013-05-07 11:41:53
|
Hello there, I just ran the static analyser "cppcheck" over the source code of ayttm. It said 1. [edit_list_window.c:342]: (error) Buffer is accessed out of bounds. The source code is sprintf(rdata, "rowdata%d", i); but char rdata[8]; rdata is one too small, because 9 > 8. Suggest increase size of rdata by at least one. 2. Some resource leaks on error handling paths. [action.c:173]: (error) Resource leak: output_fhtml [action.c:173]: (error) Resource leak: output_fplain [offline_queue_mgmt.c:128]: (error) Resource leak: queue [offline_queue_mgmt.c:267]: (error) Resource leak: queue Regards David Binderman |
From: Philip T. <phi...@gm...> - 2013-05-01 23:37:25
|
On 1 May 2013 19:04, Kapil Anand <kap...@gm...> wrote: > Hi, > > I work in information flow analysis of programs and my analysis gave a > possible warning with respect to format string vulnerability in ayttm. > > Thanks Kapil. |
From: Kapil A. <kap...@gm...> - 2013-05-01 23:04:32
|
Hi, I work in information flow analysis of programs and my analysis gave a possible warning with respect to format string vulnerability in ayttm. * Function "http_connect" populates "debug_buff" through "inputline". "inputline" is populated through an external "recv" command. "debugf" is passed directly to printf without a format string. * *Code: (in http_connect)* * * *//Populates inputine through recv call* *ay_recv_line(sockfd,&inputline)* * * *//Moves inputline to debug_buff* *snprintf(debug_buff, sizeof(debug_buff), <%s\n",inputline); * * * * * *//Passes to debug_print a.k.a printf* *debug_print(debug_buff)* Our analysis flagged this behavior. However, we are not sure whether ayttm developers are aware of this behaviour. This might very well be a false positive. We just wanted to confirm our analysis. Any response in this regard will be appreciated. Thanks Regards, Kapil |
From: SourceForge.net <no...@so...> - 2012-11-20 04:52:03
|
Bugs item #3588676, was opened at 2012-11-19 20:52 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3588676&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: IRC Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://me.yahoo.com/a/jZ.7PAU_ () Assigned to: Nobody/Anonymous (nobody) Summary: Ayttm process 13437 rec'd signall 11 Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.5 Features: enchant Operating system: Linux 2.6.32-smp (i686) C Library: GNU libc 2.10.1 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3588676&group_id=77614 |
From: SourceForge.net <no...@so...> - 2012-06-08 00:35:40
|
Bugs item #3533071, was opened at 2012-06-07 17:35 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3533071&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://me.yahoo.com/a/LmRxwpgo () Assigned to: Nobody/Anonymous (nobody) Summary: Ayttm crashed Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.8 Features: enchant Operating system: Linux 2.6.32.59 (i686) C Library: GNU libc 2.10.1 Signal: 11 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3533071&group_id=77614 |
From: SourceForge.net <no...@so...> - 2012-04-12 17:53:49
|
Bugs item #3517270, was opened at 2012-04-12 10:53 Message generated for change (Tracker Item Submitted) made by lrxianed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3517270&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: lrxianed (lrxianed) Assigned to: Nobody/Anonymous (nobody) Summary: find a bug Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.8 Features: enchant Operating system: Linux 3.0.25 (i686) C Library: GNU libc 2.10.1 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3517270&group_id=77614 |
From: SourceForge.net <no...@so...> - 2012-01-25 22:54:35
|
Bugs item #3479774, was opened at 2012-01-25 14:54 Message generated for change (Tracker Item Submitted) made by kohandlen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3479774&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Yahoo Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: karen (kohandlen) Assigned to: Nobody/Anonymous (nobody) Summary: attym has crashed Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.8 Features: enchant Operating system: Linux 2.6.32-uni (i686) C Library: GNU libc 2.10.1 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3479774&group_id=77614 |
From: Siddhesh P. <sid...@gm...> - 2011-12-15 02:54:48
|
On Wed, Dec 14, 2011 at 9:35 PM, Miguel Bouzada <mbo...@gm...> wrote: > I sent the translation into Galician (gl) and Spanish (es) updating through > this email account. > The mail was rejected by oversized > Thanks, I've committed and pushed your changes to git. -- Siddhesh Poyarekar http://siddhesh.in |
From: Miguel B. <mbo...@gm...> - 2011-12-14 16:06:13
|
I sent the translation into Galician (gl) and Spanish (es) updating through this email account. The mail was rejected by oversized Can be downloaded from: http://gruvi.galpon.org/minino/traducciones/ayttm/0.6.3/ -- Membro de «The Document Foundation projects» http://gl.libreoffice.org Membro de «Proxecto Trasno» http://trasno.net Membro do «Grupo de Amigos Linux de Pontevedra (GALPon)» http://galpon.org Co-coordinador do proxecto «GALPon MiniNo» http://minino.galpon.org |
From: SourceForge.net <no...@so...> - 2011-10-15 15:38:58
|
Bugs item #3424146, was opened at 2011-10-15 11:38 Message generated for change (Tracker Item Submitted) made by ancientdreamer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3424146&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: MSN Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: AncientDreamer87 (ancientdreamer) Assigned to: Colin Leroy (colinleroy) Summary: crash on login Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.6 Features: enchant Operating system: Linux 3.0.0-12-generic-pae (i686) C Library: GNU libc 2.13 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3424146&group_id=77614 |
From: SourceForge.net <no...@so...> - 2011-07-25 20:13:32
|
Bugs item #3377535, was opened at 2011-07-25 20:13 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3377535&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: glens () Assigned to: Nobody/Anonymous (nobody) Summary: Crash on ubuntu 11.04 Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.24.4 Features: enchant Operating system: Linux 2.6.38-8-generic (x86_64) C Library: GNU libc 2.13 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3377535&group_id=77614 |
From: SourceForge.net <no...@so...> - 2011-06-09 02:12:06
|
Bugs item #3314017, was opened at 2011-06-08 20:12 Message generated for change (Tracker Item Submitted) made by colormedisco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3314017&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: MSN Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tek (colormedisco) Assigned to: Colin Leroy (colinleroy) Summary: Ayttm has crashed Initial Comment: Ayttm version 0.6.3-1 GTK+ version 2.20.0 Features: enchant Operating system: Linux 2.6.33.2 (i686) C Library: GNU libc 2.11.1 Signal: 11 -- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3314017&group_id=77614 |
From: SourceForge.net <no...@so...> - 2011-05-13 04:48:18
|
Bugs item #3301377, was opened at 2011-05-13 11:48 Message generated for change (Tracker Item Submitted) made by sagarun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3301377&group_id=77614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Arun SAG (sagarun) Assigned to: Nobody/Anonymous (nobody) Summary: ayttm SRPM rebuilding from source: Buildrequires enchant-dev Initial Comment: Operation system: Fedora 14 Steps to reproduce the bug: 1. Download the latest srpm http://sourceforge.net/projects/ayttm/files/ayttm/0.6.3/ayttm-0.6.3-1.src.rpm/download 2. rpmbuild --rebuild ayttm-0.6.3-1.src.rpm Actual result: rebuild fails with checking for ENCHANT... no configure: error: Package requirements (enchant) were not met: No package 'enchant' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ENCHANT_CFLAGS and ENCHANT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. error: Bad exit status from /var/tmp/rpm-tmp.OtZcCo (%build) Expected result: src rpm rebuilds correctly Possible fix: Add enchant-devel to BuildRequires: misc: koji build log: http://koji.fedoraproject.org/koji/getfile?taskID=3069111&name=build.log scratch build url: http://koji.fedoraproject.org/koji/taskinfo?taskID=3069109 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=3301377&group_id=77614 |
From: Dropbox <no-...@dr...> - 2011-04-02 22:20:09
|
Ran Yakumo wants you to try Dropbox! Dropbox lets you bring all your photos, docs and videos with you anywhere and share them easily. Get started here: http://www.dropbox.com/link/20.Qa7KUM56cD/NjgxMzkyODg0Nw?src=referrals_bulk9 - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/3653f30941ae/ayttm-users%40lists.sourceforge.net |
From: Ashish J. <ten...@ya...> - 2011-02-14 14:56:20
|
You’ll be astonished when you try it! http://fotoceramika.btx.pl/2011.php?hot=1004 ... |