Messages

721

HFS ~ HTTP File Server / Re: For testing purpose (HFS including SSl tools)

« on: March 16, 2015, 08:12:16 AM »

look for disabled... Silent Plz has already done this...:
; Disable support for insecure SSLv2 protocol.
options = NO_SSLv2
; Disable support for insecure SSLv3 protocol.
options = NO_SSLv3

Nice find!, I didn't notice it.

722

Everything else / Re: Google code shutting down

« on: March 14, 2015, 07:50:00 AM »

This is not a surprise for me at all! They did the same with Google Wave, and they killed Gizmo5. And with GrandCentral was merged with Google Voice. And the same was with Google Reader (RSS). So, I'm tired of see big companies shitting shutting down services. If were for them, they would discontinue GMail too (and all just to promote Google+). Just for now, Google Search and GMail are safe...

If you are curious, the list of discontinued Google services, continues here...
http://en.wikipedia.org/wiki/Category:Discontinued_Google_services

About Google Code, is not a big loss. We still have GitHub, Bitbucket, SourceForge, etc.

723

HFS ~ HTTP File Server / Re: For testing purpose (HFS including SSl tools)

« on: March 14, 2015, 07:14:12 AM »

Talking about security and vulnerabilities, how about this?:

POODLE - An SSL 3.0 Vulnerability (CVE-2014-3566)

Code: [Select]

http://en.wikipedia.org/wiki/POODLE
https://www.us-cert.gov/ncas/alerts/TA14-290A
https://securityblog.redhat.com/2014/10/15/poodle-a-ssl3-vulnerability-cve-2014-3566/
https://community.qualys.com/blogs/securitylabs/2014/10/15/ssl-3-is-dead-killed-by-the-poodle-attack
I'm not on technical details about this (I'm not an expert at all about this!), but I was wondering if "HFS 2.3d SSL 292f" is using SSL v3.0 (which is vulnerable) or TLS (which is not vulnerable) by default?...

According to this vulnerability, we should disable (not necessarily remove) SSL, and use TLS by default. Is that possible?...

724

HTML & templates / Re: mp3 streamer

« on: March 07, 2015, 05:43:15 AM »

...i know its old...:

725

Pусский / Re: HFS + P2P?

« on: March 01, 2015, 09:33:07 PM »

rosner: Try to run HFS on port 443 or 80 (not 8080!). The problem is that your ISP is giving you a private IP, and not a public IP. Generally, a private IP comes with closed ports (firewalled). You may try pagekite.net, which is something perfect for this problem.

726

router & port problems / Re: Is there any way to protect repeated login attempts

« on: January 10, 2015, 08:45:49 AM »

I don't think a captcha could be of any help here, so, I think this must be implemented internally on HFS (if it was not implemented already). I don't see another option.

727

HFS ~ HTTP File Server / Re: favicon HFS ?

« on: January 10, 2015, 08:38:16 AM »

Alguem pode me ajudar a alterar o favicon?

Use a favicon editor, or any icon editor, like these:
http://favicon-generator.org/editor/
http://www.degraeve.com/favicon/

728

Español / Re: Guardar las cuentas de Usuario

« on: January 05, 2015, 02:17:30 PM »

Are you having fun?... LOL!
Skal du ha det gøy?

729

HFS ~ HTTP File Server / Re: [Feature Request] an option to show MB/s instead of KB/s

« on: January 05, 2015, 02:01:10 PM »

Yeah, that's great for fast connections...
But, if speed is (slow), and less than 1.00 MB/s, I think it's still great to have it displayed on KB/s, isn't it?... (Or at least have an option to use MB/s or KB/s).

730

HFS ~ HTTP File Server / Re: Out of no where, HFS speeds drastically decreased.

« on: January 05, 2015, 01:54:10 PM »

Hi and welcome...
It sounds your ISP touched something...
Are you running HFS on traditional ports? (like 80 or 443). Perhaps if you run it on some strange port (like 33907, 5600, 9080, etc), your ISP may be throttling your speed on non-traditional ports. It happened to me.
Try using port 80.

731

Pусский / Re: HFS + P2P?

« on: December 29, 2014, 08:48:31 AM »

The problem is that HFS does not break through NAT. (We need to think how to do it.

So, the problem is your ISP gives you a private IP, and not a public IP. In that case, instead of implementing the "torrent protocol", we may need to implement a "NAT Traversal" feature to HFS (I don't know if that is possible).

More info about "NAT Traversal", here:

http://www.tml.tkk.fi/Studies/T-110.551/2005/papers/hu.pdf
http://en.wikipedia.org/wiki/TCP_hole_punching
http://en.wikipedia.org/wiki/STUN

732

HTML & templates / Re: register end after to see the file in our server

« on: December 23, 2014, 07:23:39 AM »

So, you want to someone who visit your HFS server, be able to register, and then be able to view your files?, right?. In that case, I think it's not possible, since user registrations must be handled directly from HFS program, and not through the web interface. So, you need to create a username and password in the HFS program first. Someone correct me if I'm wrong.

733

HTML & templates / Re: filelist.tpl ignored?

« on: December 23, 2014, 07:19:09 AM »

(Can someone with wiki credentials add hfs. to the doc page at http://www.rejetto.com/wiki/index.php?title=HFS:_Hidden_things  ?)

OK, I'll do that when my wiki account is approved.

734

HFS ~ HTTP File Server / Re: How to use domain name instead of static IP?

« on: December 19, 2014, 05:15:49 AM »

This is an interesting topic.

By guessing your domain registrar doesn't give you a DDNS service, what you can actually do is create a CNAME record for www (or any other subdomain) to point to example.dyndns.com (in case your are using DynDNS as your DDNS provider).

What you can't do is point an A record to example.dyndns.com, because an A record needs to be pointed to an IP, not a domain. Using only a CNAME, the problem is your website will not be reacheable by using example.com (which needs an A record), so your website will only work using a subdomain, like www.example.com, or private.example.com. I you don't understand what I'm saying, just ask.

If I'm wrong on something, or anybody has a better idea of how get this done, just leave a comment here. Thanks.....

735

HFS ~ HTTP File Server / Re: How to use domain name instead of static IP?

« on: December 18, 2014, 12:29:42 PM »

I already point my domain to the static on the domain provider's DNS management site. (I set A record example.com to IP xxx.xxx.xxx.xxx)

Setting up an "A Record" on your domain registrar, doesn't have any to do with HFS's features. HFS makes use of a DDNS service. As far I know, your domain provider needs to support/offer a DDNS service, like DynDNS does. So, you can't update an "A Record" directly with HFS, unless your domain registrar offers you a DDNS service with their service.

So, here a few questions:
A) What domain registrar are you using?...
B) Do you have a fixed static IP or a dynamic one? (I guess you have a dynamic one)