On Mon, Mar 05, 2018 at 09:29:51PM +0100, wwp wrote:
> Hello Fred,
>
>
> On Mon, 5 Mar 2018 13:53:16 -0500 Fred Smith
> wrote:
>
> > I've finally been reduced to having to install Skype on my Linux box.
> > I resisted for years, but now ended up trying it.
> >
Hello Fred,
On Mon, 5 Mar 2018 13:53:16 -0500 Fred Smith
wrote:
> I've finally been reduced to having to install Skype on my Linux box.
> I resisted for years, but now ended up trying it.
>
> and while the latest RPM installs just fine, it refuses to
Wouldn't filtering the DNS be more practical?
On 5 March 2018 at 18:57, Leon Fauster wrote:
>
> > Am 05.03.2018 um 15:34 schrieb Bill Gee :
> >
> >
> > On Monday, March 5, 2018 7:23:53 AM CST Leon Fauster wrote:
> >> Am 05.03.2018 um 13:04
On 2/28/2018 4:23 PM, Nicolas Kovacs wrote:
Hi,
I've been running Squid successfully on CentOS 7 (and before that on 6
and 5), and it's always been running nicely. I've been using it mostly
as a transparent proxy filter in school networks.
So far, I've only been able to filter HTTP.
Do any of
Hi all!
I've finally been reduced to having to install Skype on my Linux box.
I resisted for years, but now ended up trying it.
and while the latest RPM installs just fine, it refuses to acknowledge
that I have a microphone!
In fact I have two: 1 in the USB web cam (it finds the cam), the
> Am 05.03.2018 um 15:34 schrieb Bill Gee :
>
>
> On Monday, March 5, 2018 7:23:53 AM CST Leon Fauster wrote:
>> Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs :
>>> Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
So far, I've only been able to
On 03/05/18 10:21, Nicolas Kovacs wrote:
Le 05/03/2018 à 16:30, Valeri Galtsev a écrit :
Sorry, I missed the beginning of this thread. This sounds to me like
running one's own Certification Authority. I did that a while ago for
over a decade. However, these days one may consider
Le 05/03/2018 à 16:30, Valeri Galtsev a écrit :
> Sorry, I missed the beginning of this thread. This sounds to me like
> running one's own Certification Authority. I did that a while ago for
> over a decade. However, these days one may consider
>
> https://letsencrypt.org/
>
> - you will have to
On 03/05/18 08:34, Bill Gee wrote:
On Monday, March 5, 2018 7:23:53 AM CST Leon Fauster wrote:
Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs :
Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
So far, I've only been able to filter HTTP.
Do any of you do transparent HTTPS
On 03/05/18 07:23, Leon Fauster wrote:
Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs :
Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
So far, I've only been able to filter HTTP.
Do any of you do transparent HTTPS filtering ? Any suggestions,
advice, caveats, do's and
The certificate should have *CA:true* set for act a CA for dynamic signing
certificates by Squid.
Most probably, Let's Encrypt will ignore this constraint in CSR.
2018-03-05 12:33 GMT-03:00 Chris Adams :
> Once upon a time, Valeri Galtsev said:
> >
Once upon a time, Valeri Galtsev said:
> https://letsencrypt.org/
>
> - you will have to run web server to have certificate signed by
> them
Not necessarily - we do most of our Let's Encrypt validation with DNS
rather than HTTP.
--
Chris Adams
On 03/05/18 06:34, Nicolas Kovacs wrote:
Le 05/03/2018 à 13:30, Nux! a écrit :
You could probably just drop your CA cert in the filesystem and run a
couple of commands to get it imported, rather than having to import
the CA in the browsers individually. You could probably deliver it
via
Starting with version 3.5 of Squid, was introduced a new feature named
"*SslBump
Peek and Splice*".
With this functionality, Squid is able to intercept HTTPS traffic
transparently (with exceptions, of course).
This manner, Squid, with spike, is able to logging HTTPS traffic and apply
directives
On Monday, March 5, 2018 7:23:53 AM CST Leon Fauster wrote:
> Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs :
> > Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
> >> So far, I've only been able to filter HTTP.
> >>
> >> Do any of you do transparent HTTPS filtering ? Any
Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs :
>
> Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
>> So far, I've only been able to filter HTTP.
>>
>> Do any of you do transparent HTTPS filtering ? Any suggestions,
>> advice, caveats, do's and don'ts ?
>
> After a week of
Le 04/03/2018 à 02:45, Yves Bellefeuille a écrit :
> I finally decided to move from CentOS 6 to CentOS 7, but was surprised
> to see that kmail is no longer included: Red Hat deliberately decided
> to omit it.
Probably because it's too buggy. I've been using Kmail for a few years
under KDE 3.x,
Le 05/03/2018 à 13:30, Nux! a écrit :
> You could probably just drop your CA cert in the filesystem and run a
> couple of commands to get it imported, rather than having to import
> the CA in the browsers individually. You could probably deliver it
> via yum/rpm or better yet, ansible or even some
Nice, thanks for sharing.
You could probably just drop your CA cert in the filesystem and run a couple of
commands to get it imported, rather than having to import the CA in the
browsers individually.
You could probably deliver it via yum/rpm or better yet, ansible or even some
shell script.
Le 28/02/2018 à 22:23, Nicolas Kovacs a écrit :
> So far, I've only been able to filter HTTP.
>
> Do any of you do transparent HTTPS filtering ? Any suggestions,
> advice, caveats, do's and don'ts ?
After a week of trial and error, transparent HTTPS filtering works
perfectly. I wrote a detailed
20 matches
Mail list logo