> Il 30/01/19 16:49, Simon Matter ha scritto:
>>> On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
> Alessandro Baggi wrote:
>> Il 29/01/19 18:47, mark ha scritto:
>>> Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha scritto:
> Hi, again, folks,
>
>I'm trying to convert a number of iptables rules to firewalld rich
> rules. I need to do this, because this is, in fact, a firewall, to
> protect access to servers with sensitive data. It will limit access to
> the servers behind it to a specific network, and nobody
Hello Ed,
I tried that, for 2-3 newer kernels, didn't work (I actually posted that
link here yesterday or so).
btw: I haave the same problem with Centos/RHEL 7 kernels (as well as 6
ones).
You'd think there must be some kernel option to dodge the problem, so
far no luck.)
Ron
On
> On Tuesday, January 29, 2019, 8:08:39 PM EST, RC wrote:
> Hello,
>
> I run CentOS release 6.10 (Final) on a Dell Inspiron M6700.
>
> 2.6.32-754.el6.x86_64 boots, and is whaat I am running now
> none of these, updated ones, won't boot:
>
> 2.6.32-754.3.5.el6.x86_64
>
On 1/30/19 7:57 AM, Nicolas Kovacs wrote:
The tl;dr version of my last post is : Apache is not supposed to show
static web pages with a user_tmp_t SELinux context. So why does it show
them anyway ?
Policy allows that, currently:
# sesearch -A -s httpd_t -t user_tmp_t
Found 15 semantic av
On 1/30/19 12:40 PM, mark wrote:
What I've been trying to find is a script/program that converts the
output of iptables-save to something I can feed to firewall-cmd.
Anyone have a link to such?
None that I know of. It might be easier for you to convert existing
rules to "direct" rules
Buenas Tardes
un favor tengo un problema un equipo tenia virus el cual ya lo elimine de hecho
di de baja del servidor la cuenta del emial pero me siguen llegando pura
basura de esta cuenta y elimine las carpetas del usuarios , tuve que poner la
cuenta para que se rechace loe mail que están
Hi, again, folks,
I'm trying to convert a number of iptables rules to firewalld rich
rules. I need to do this, because this is, in fact, a firewall, to
protect access to servers with sensitive data. It will limit access to
the servers behind it to a specific network, and nobody else, and allow
Alessandro Baggi wrote:
> Il 30/01/19 16:49, Simon Matter ha scritto:
>>> On 01/30/19 03:45, Alessandro Baggi wrote:
>> I also don't have much experience with spare handling as I also don't
>> do it in my scenarios.
>>
>> However in general, I think the problem today is this:
>> We have very
Il 30/01/19 16:49, Simon Matter ha scritto:
On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha scritto:
I've no idea what happened, but the box I was
Il 30/01/19 18:49, mark ha scritto:
Alessandro Baggi wrote:
Il 30/01/19 16:33, mark ha scritto:
Alessandro Baggi wrote:
Il 30/01/19 14:02, mark ha scritto:
On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark
Robert Moskowitz wrote:
> I have a series of static routes in route-eth0
>
> Recently I had to made changes and could not find an effective way to
> get the old routes out and the new routes in.
>
> ifdown-route seems to apply the content of route-eth0 to take down the
> routes listed and
Alessandro Baggi wrote:
> Il 30/01/19 16:33, mark ha scritto:
>
>> Alessandro Baggi wrote:
>>
>>> Il 30/01/19 14:02, mark ha scritto:
>>>
On 01/30/19 03:45, Alessandro Baggi wrote:
> Il 29/01/19 20:42, mark ha scritto:
>
>> Alessandro Baggi wrote:
>>
>>> Il 29/01/19
Alessandro Baggi wrote:
> Il 30/01/19 14:02, mark ha scritto:
>> On 01/30/19 03:45, Alessandro Baggi wrote:
>>> Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
> Il 29/01/19 18:47, mark ha scritto:
>> Alessandro Baggi wrote:
>>> Il 29/01/19 15:03, mark ha scritto:
On Wed, 30 Jan 2019 at 09:45, SternData
wrote:
> On 1/30/19 5:57 AM, Stephen John Smoogen wrote:
> > On Wed, 30 Jan 2019 at 00:25, SternData
> > wrote:
> >
> >> This keeps logging:
> >>
> >> Could not get metalink
> >> https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64
> error
> >>
On Wed, 30 Jan 2019 at 09:21, Kenneth Porter wrote:
> --On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen
> wrote:
>
> > Can you run the code from: https://github.com/puiterwijk/check_metalink
> to
> > see if we can pin down the proxy which is the problem (there are 14 and
> >
Le 30/01/2019 à 16:22, Nicolas Kovacs a écrit :
> Some time ago I wrote an introductory article about SELinux on my blog.
> I'm currently updating it for my new blog, and I found a curious change
> in SELinux policy. Here goes.
>
> For demonstration purposes, I'm using some static webpages, more
Il 30/01/19 16:33, mark ha scritto:
Alessandro Baggi wrote:
Il 30/01/19 14:02, mark ha scritto:
On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha
> On 01/30/19 03:45, Alessandro Baggi wrote:
>> Il 29/01/19 20:42, mark ha scritto:
>>> Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
> Alessandro Baggi wrote:
>> Il 29/01/19 15:03, mark ha scritto:
>>
>>> I've no idea what happened, but the box I was working on
I have a series of static routes in route-eth0
Recently I had to made changes and could not find an effective way to
get the old routes out and the new routes in.
ifdown-route seems to apply the content of route-eth0 to take down the
routes listed and ifup-route brings up routes based on
Hi,
Some time ago I wrote an introductory article about SELinux on my blog.
I'm currently updating it for my new blog, and I found a curious change
in SELinux policy. Here goes.
For demonstration purposes, I'm using some static webpages, more exactly
the default pages found in
On 30.01.19 14:40, Jerry Geis wrote:
>> Please show us 'pip freeze'.
>> I assume that you have onvif sucessfully installed.
>
> your correct 'pip freeze' did show onvif.
> onvif==0.2.0
>
> I was then expecting to run python-onvif but that is not found.
I think, nobody has packaged this python
On 1/30/19 5:57 AM, Stephen John Smoogen wrote:
> On Wed, 30 Jan 2019 at 00:25, SternData
> wrote:
>
>> This keeps logging:
>>
>> Could not get metalink
>> https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64 error
>> was
>> 14: HTTPS Error 503 - Service Unavailable
>>
>> I've removed
--On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen
wrote:
Can you run the code from: https://github.com/puiterwijk/check_metalink to
see if we can pin down the proxy which is the problem (there are 14 and
our checks are showing they are ok so I need to pin this down
>Please show us 'pip freeze'.
>I assume that you have onvif sucessfully installed.
your correct 'pip freeze' did show onvif.
onvif==0.2.0
I was then expecting to run python-onvif but that is not found.
Jerry
___
CentOS mailing list
CentOS@centos.org
Il 30/01/19 14:02, mark ha scritto:
On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha scritto:
I've no idea what happened, but the box I was working
On Wed, Jan 30, 2019 at 08:17:37AM -0500, Jerry Geis wrote:
> I am trying to install the python-onvif package on C7.
>
> I did:
> pip install onvif
> Requirement already satisfied (use --upgrade to upgrade): onvif in
> /usr/lib/python2.7/site-packages
> Requirement already satisfied (use
I am trying to install the python-onvif package on C7.
I did:
pip install onvif
Requirement already satisfied (use --upgrade to upgrade): onvif in
/usr/lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): suds>=0.4 in
/usr/lib/python2.7/site-packages (from onvif)
On 01/30/19 03:45, Alessandro Baggi wrote:
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha scritto:
I've no idea what happened, but the box I was working on last week
has a *second* bad
On 30-01-19 03:49, Gregory P. Ennis wrote:
On Tue, 29 Jan 2019 20:00:03 -0600
Gregory P. Ennis wrote:
Thanks much for your help. I had tried the links you listed above and in
both cases the scripts do not identify the signature pad as been attached to
the system. I have tried this with both
On 2019-01-30, Ralf Prengel wrote:
>
> Zitat von Liam O'Toole :
>
>> On 2019-01-29, Ralf Prengel wrote:
>>> Hallo,
>>> thanks but this doesn t work here allthough most tips and hints are
>>> using this parameter.
>>> Any idea how to debug ?
>>>
>>> Thanks
>>> Ralf
>>>
>>> Von meinem iPad
On Wed, 30 Jan 2019 at 00:25, SternData
wrote:
> This keeps logging:
>
> Could not get metalink
> https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64 error
> was
> 14: HTTPS Error 503 - Service Unavailable
>
> I've removed the epel-release package, done a "yum clean all", then
>
Am Mittwoch, 30. Januar 2019, 06:24:46 CET schrieb SternData:
> This keeps logging:
>
> Could not get metalink
> https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64 error was
> 14: HTTPS Error 503 - Service Unavailable
>
> I've removed the epel-release package, done a "yum clean all",
Il 29/01/19 20:42, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 18:47, mark ha scritto:
Alessandro Baggi wrote:
Il 29/01/19 15:03, mark ha scritto:
I've no idea what happened, but the box I was working on last week
has a *second* bad drive. Actually, I'm starting to wonder about
34 matches
Mail list logo
