Re: [GTALUG] TekSavvy or Rogers blocking apt user agent

2019-11-05 Thread David Thornton via talk
I've seen this before on a fortigate firewall.

The FW will detect "apt" as app:XMLRPC rather than app:HTTP for the
purposes of "Application Detection" and if the "allow port 80 rules" is
infact an "Allow only app:HTTP on port 80" rule , then XMLRPC over port 80
is disallowed.

David

On Mon, Nov 4, 2019 at 4:13 PM Jamon Camisso via talk 
wrote:

> Well this is a new low:
>
>
> https://askubuntu.com/questions/1185612/apt-get-stuck-on-waiting-for-headers/1185713
>
> Mind-boggling that it is/was even an issue at an ISP & HTTP level.
>
> Either they have a giant whitelist of browser agents to maintain, or a
> blacklist to update and added apt to it.
>
> In either case, they're looking at HTTP traffic and acting on it directly.
>
> Still an issue for anyone?
>
> Jamon
> ---
> Post to this mailing list talk@gtalug.org
> Unsubscribe from this mailing list
> https://gtalug.org/mailman/listinfo/talk
>


-- 
David Thornton
https://wiki.quadratic.net
https://github.com/drthornt/
https://twitter.com/northdot9/
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] TekSavvy or Rogers blocking apt user agent

2019-11-05 Thread Giles Orr via talk
On Mon, 4 Nov 2019 at 21:27, Jamon Camisso via talk  wrote:

> On 04/11/2019 21:24, D. Hugh Redelmeier via talk wrote:
> > Is this happening to you?  I will assume so.
> >
> > - my main internet connection is directly through Rogers.
> >
> > - I use Ubuntu infrequently.
> >
> > - when I do update it, I have had no issue.  Most recently: a couple
> >   of days ago.
> >
> > The ip address in the wireshark log is 91.189.91.23 (AKA
> > economy.canonical.com).  When I point (Fedora) firefox at it, it claims
> > that it cannot connect to a web server there.  Of course that's with
> > Firefox's User Agent String.  ping does get responses.
>
> Teksavvy have done something on their end:
>
> https://twitter.com/TekSavvyCSR/status/1191486635764068355
>

Wouldn't it be great if they said WHAT had caused it rather than just "we
fixed it?"  If you told us the how, we might have more faith that you
wouldn't do it again.  But more and more, technical support departments are
hiding these outcomes - either to disguise what they think could be
regarded as incompetence or because they're afraid it might reveal secrets
about their processes or infrastructure.  Both have some validity.  Having
been in the position myself [1], I get that it's not appealing to reveal
the process and problems discovered, but I'm still a believer in
transparency.

[1] I'm in "Operations," here's just one example.  We upgraded Debian on a
back end server which in turn broke Chrome 49 - but it took over a week to
figure out that HAProxy was the reason for the Chrome 49 breakage.  We then
upgraded HAProxy again (to Debian backports) which fixed Chrome 49.  Yes,
we still have to support that.  And this has led to a big dispute at work
about whether we should be notifying people and on what level of upgrade
...  You get the idea.

-- 
Giles
https://www.gilesorr.com/
giles...@gmail.com
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Hardcore sed foo

2019-11-05 Thread Giles Orr via talk
On Tue, 5 Nov 2019 at 06:42, Giles Orr  wrote:

> On Tue, 5 Nov 2019 at 01:47, William Park via talk 
> wrote:
>
>> 0 or 1 match is ?
>> Eg.  echo /aaa/.bbb//ccc/123 | sed 's,\(/\.\?[^/]\)[^/]*,\1,g'
>> --William
>>
>
> Nice - that works too.
>
> Jeez regex is a pain - it took three minutes of staring at that just to
> figure it out, even though I knew what we were both trying to achieve.
>

PS.  Yours works better: mine fails on the double slash '//' because it
insists on looking for a non-slash item right after it and so produces
'/a/.b///1' when it should have given me '/a/.b//c/1' as yours did.  It's
somewhat academic as in processing prompts the regex should never encounter
two slashes with nothing between them, but ... I prefer the more correct
answer.  Thanks.

-- 
Giles
https://www.gilesorr.com/
giles...@gmail.com
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Hardcore sed foo

2019-11-05 Thread Giles Orr via talk
On Tue, 5 Nov 2019 at 01:47, William Park via talk  wrote:

> 0 or 1 match is ?
> Eg.  echo /aaa/.bbb//ccc/123 | sed 's,\(/\.\?[^/]\)[^/]*,\1,g'
> --William
>

Nice - that works too.

Jeez regex is a pain - it took three minutes of staring at that just to
figure it out, even though I knew what we were both trying to achieve.

-- 
Giles
https://www.gilesorr.com/
giles...@gmail.com
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk