3 ms·

(IPFS dev here) wow, that sucks. is this blocked in your corp firewall? Any chance of talking to the sysadmins? Blocking IPFS is like blocking HTTP :/ :/ :/ We

(IPFS dev here) wow, that sucks. is this blocked in your corp firewall? Any chance of talking to the sysadmins? Blocking IPFS is like blocking HTTP :/ :/ :/ We may have to move our gateway back off our main domain, and have a "recommended blocker", so that people don't jump on this. Anyway, one piece of good news: despite everyone's belief about UDP transports never going through corp firewalls, QUIC now handles MOST (>60%, close to 80% i believe) of "Google Chrome<-->Google sites" traffic across the world. So, temp setbacks may be annoying, but in the end, once users install IPFS -- and once we have browser implementations, we can make all the traffic look like HTTP TLS flows, so blocking it will be very hard without also blocking regular HTTP TLS traffic.

dingaling 11y ago
> so blocking it will be very hard without also blocking regular HTTP TLS traffic. Many large or data-sensitive companies do SSL MiTM at their firewall so unfortunately that's not hard at all.
- _prometheus 11y ago
  true, but then you're not in a {censorship, attacker} free environment at all -- MITMing TLS _is_ violating the security expectations of today's websites. I wouldn't even check my non-work email. i.e. all bets are off. there will always be pockets. but over time we could win even there, as the perf improvement will matter.
- fulafel 11y ago
  This is a minority though and the users on such nets have pretty diminished expectations on the level of net access they have. (It's also illegal BTW in civilized countries! At least on networks with employees doing web browsing, as that's personal communications of the employee and and part of fundamental rights)
firebones 11y ago
I talked to them and explained the futility of blocking the informational site when the source is freely available on Github. Ironically, I could probably run the software, I just can't hit the ipfs.io site from my browser because the company we use for classifying sites (WebSense, I believe) has deemed ipfs.io "peer-to-peer", a category which is blocked by policy. You should take a survey of F500 companies to see how many can actually hit the site. Or check your logs.

dingaling 11y ago

> so blocking it will be very hard without also blocking regular HTTP TLS traffic. Many large or data-sensitive companies do SSL MiTM at their firewall so unfortunately that's not hard at all.

_prometheus 11y ago
true, but then you're not in a {censorship, attacker} free environment at all -- MITMing TLS _is_ violating the security expectations of today's websites. I wouldn't even check my non-work email. i.e. all bets are off. there will always be pockets. but over time we could win even there, as the perf improvement will matter.
fulafel 11y ago
This is a minority though and the users on such nets have pretty diminished expectations on the level of net access they have. (It's also illegal BTW in civilized countries! At least on networks with employees doing web browsing, as that's personal communications of the employee and and part of fundamental rights)

firebones 11y ago

I talked to them and explained the futility of blocking the informational site when the source is freely available on Github. Ironically, I could probably run the software, I just can't hit the ipfs.io site from my browser because the company we use for classifying sites (WebSense, I believe) has deemed ipfs.io "peer-to-peer", a category which is blocked by policy. You should take a survey of F500 companies to see how many can actually hit the site. Or check your logs.