[CentOS-es] Revista Atix 27

[Esteban Saavedra L.]

Estimad@s, comunicarles que la Revista Atix, ha liberado su nuevo
numero, que puede ser descargado desde su sitio web.
http://revista.atixlibre.org

salu2

-- 
-- 
Esteban Saavedra López
CEO AtixLibre - Bolivia
esteban.saave...@atixlibre.org
estebansaave...@yahoo.com
estebansaave...@gmail.com
jesaave...@opentelematics.org
Bolivia
_
Te Invito a Visitarme y conocer mis Áreas de
Investigación
http://esteban.opentelematics.org
http://revista.atixlibre.org
http://www.atixlibre.org
GPG Key ID: 0x0E96FE54
65A1 CEA6 712D 355B F9DD 5B62 DE1B 7381 0E96 FE54
_
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

[Keith Keller]

On 2018-10-29, Frank Thommen  wrote:
>
> PostgreSQL is running in a docker container:
>
> $ docker ps
> CONTAINER IDIMAGE COMMAND 
>CREATED STATUS  PORTSNAMES
> 6f11fc41d2f0postgres  "docker-entrypoint..."   4 
> days ago  Up 4 days   0.0.0.0:5432->5432/tcp   postgres
> $
>
> The various docker interfaces and virtual bridges are not assigned to 
> any specific zone.
>
> Why is port 5432/tcp open?

It may be Docker manipulating the iptables rules.  If you don't want it
open at all, remove the port argument from the docker run command line
(or moral equivalent) and recreate the container (make sure you have
saved your data first, either with a volume mount or by dumping first).

If you need something more complex, here's some docs on how Docker
interacts with iptables, and how you can insert rules into its chains:

https://docs.docker.com/network/iptables/

--keith


-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CEBA-2018:3013 CentOS 7 tzdata BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2018:3013 

Upstream details at : https://access.redhat.com/errata/RHBA-2018:3013

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
59e12ef8382b5e1e893053e6b6b8ae9408df040bfe114a5a01e83dbfd53f6287  
tzdata-2018f-2.el7.noarch.rpm
789b5f573116c54397536cc178fb76eec58bc6b06cc811c0c3372f0505bfd251  
tzdata-java-2018f-2.el7.noarch.rpm

Source:
4c179f9fa6c98c75a94ab9f4fec7435abab6fa6484494f25059412a71669ccea  
tzdata-2018f-2.el7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CEBA-2018:3013 CentOS 6 tzdata BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2018:3013 

Upstream details at : https://access.redhat.com/errata/RHBA-2018:3013

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0e3a88856581aea77fe93130ea5a87c8db4645ef9e8a542dba9ea503293379e0  
tzdata-2018f-1.el6.noarch.rpm
f798c34e5a2e851ae952333ed2230c575199aa04159836012f65b89dfe3fb907  
tzdata-java-2018f-1.el6.noarch.rpm

x86_64:
0e3a88856581aea77fe93130ea5a87c8db4645ef9e8a542dba9ea503293379e0  
tzdata-2018f-1.el6.noarch.rpm
f798c34e5a2e851ae952333ed2230c575199aa04159836012f65b89dfe3fb907  
tzdata-java-2018f-1.el6.noarch.rpm

Source:
c6aac1e140d20ead4a4418c4357569cd6bace1a980a6f1bd0a3b1cf506f3da92  
tzdata-2018f-1.el6.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] IBM buying RedHat

[Brendan Conoboy]

On 10/29/18 1:55 AM, Simon Matter wrote:

To me it seems like, if they are smart, they will try to push IBM POWER
and RedHat Linux together to establish real competition in the hardware
market again (and of course don't forget to keep Fedora/CentOS alive)!


Er, RHEL has been running on Power for a very long time.  The fastest 
supercomputer in the world is Power9 + RHEL.


--
Brendan Conoboy / RHEL Development Coordinator / Red Hat, Inc.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

[Alexander Dalloz]

Am 29.10.2018 um 20:03 schrieb Frank Thommen:

PostgreSQL is running in a docker container:

$ docker ps
CONTAINER ID    IMAGE COMMAND   
CREATED STATUS  PORTS    NAMES
6f11fc41d2f0    postgres  "docker-entrypoint..."   4 
days ago  Up 4 days   0.0.0.0:5432->5432/tcp   postgres

$


The various docker interfaces and virtual bridges are not assigned to 
any specific zone.



Why is port 5432/tcp open?


You will see it if you check the netfilter rules with:

iptables -L -n -v --line -t filter
iptables -L -n -v --line -t nat


frank


Alexander
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] PostgreSQL port accessible even though it should be blocked by firewall

[Frank Thommen]

Hi,

this puzzles me: On one of our developer workstations, all ports with 
the exception of SSH are closed:


$ firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eno1
  sources:
  services: ssh dhcpv6-client
  ports: 22/tcp
  protocols:
  masquerade: no
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

$

but still port 5432/tcp (PostgreSQL) is open:

$ nmap -P0 devel-host

Starting Nmap 6.40 ( http://nmap.org ) at 2018-10-29 19:46 CET
Nmap scan report for devel-host (xxx.xxx.xxx.xxx)
Host is up (0.94s latency).
rDNS record for xxx.xxx.xxx.xxx: devel-host.our.domain
Not shown: 998 filtered ports
PORT STATE SERVICE
22/tcp   open  ssh
5432/tcp open  postgresql

Nmap done: 1 IP address (1 host up) scanned in 57.26 seconds
$


PostgreSQL is running in a docker container:

$ docker ps
CONTAINER IDIMAGE COMMAND 
  CREATED STATUS  PORTSNAMES
6f11fc41d2f0postgres  "docker-entrypoint..."   4 
days ago  Up 4 days   0.0.0.0:5432->5432/tcp   postgres

$


The various docker interfaces and virtual bridges are not assigned to 
any specific zone.



Why is port 5432/tcp open?

frank


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [Marketing Mail] Re: Cups freeze when remote server is unavailable

[Patrick Bégou]

Hi Lange,

thanks for these links. Following John reply I goes back and deeper in
looking for documentation. Using the web interface is not an option as I
have many laptops to set up and they are all automatically
(re)installable from a PXE boot + kickstart in case of trouble. So all
must be setup automatically (using command lines in the kickstart file)
and user must be allowed to add their own home printer.

I understand some things this afternoon, discover cups-browsed that was
not available in 1.4 version (CentOS6), understand why it was not
working (the laboratory cups version was 1.4 on a debian server and
CentOS7 has 1.6.x now) discover also that ppd files are deprecated in
newer cups version (> 2.x ?)

Time is to go deeper in all these documentations and build a scenario to
set up cups in these automatic installations process. I agree, it was
not a bug, just misunderstanding new cups software behaviour.

Patrick

Le 29/10/2018 à 17:15, Lange, Markus a écrit :
> Hi,
>
> John tries to tell you:
> Revert your configuration changes to the config file and use the local
> web interface / lp* / GUI Print Server Configuration tool to setup all
> printers at work and / or at home using these tools.
>
> This method needs a local cups instance that works if your OS is
> running (if a printer is not reachable for printing cups can still keep
> the job in it's queue until the printer is reachable).
> You can find an linux.com article on Printer Setups in [1] (mainly
> selected for its screenshots of cups web interface and not for its
> actuality) which should give you all information's to get it work.
>
> At least for desktop setups cups should be running by default, see
> "systemctl status cups" to check if it's running.
>
> For a more in-depth view on cups I can recommend reading the archwiki
> [2].
>
> best regards
> Markus
>
> [1] https://www.linux.com/learn/linux-101-printing
> [2] https://wiki.archlinux.org/index.php/CUPS
>
>
> On Mon, 2018-10-29 at 15:35 +0100, Patrick Bégou wrote:
>> Hi John
>>
>> thanks for your quick reply. If it is not a bug, as I was reading on
>> the
>> web, it is some misunderstanding from me.
>> Running cups 1.4.2 (CentOS6) I was using the "BrowsePoll" directive
>> in
>> cupsd.conf. So the printers were automatically known from the central
>> server of the lab. And home printers were working fine with this
>> setup too.
>> In CentOS7, with cups 1.6.3, this directive does not exist any more
>> and
>> reading the doc I had understood that it was replaced by the
>> client.conf
>> file. Reading your answer suggest it is not true.
>>
>> So could you tell me or suggest reading on the right manner to
>> reproduce
>> my previous centos6 setup ?
>>
>> Sorry for this newbie question, I'm not very familiar with cups
>> setup.
>>
>> Patrick
>>
>>
>> Le 29/10/2018 à 14:45, John Hodrien a écrit :
>>> On Mon, 29 Oct 2018, Patrick Bégou wrote:
>>>
 Any idea ?
>>> I don't see that this is a bug.
>>>
>>> In client.conf you're telling it which server to use, exclusively. 
>>> You're not
>>> adding remote printers, you're telling it which CUPS server to talk
>>> to
>>> everytime you use CUPS clients commands.  You don't even need to
>>> run a
>>> local
>>> CUPS server if you configure it like this.
>>>
>>> If you want a machine to work at both ends, I'd suggest you don't
>>> do
>>> this, and
>>> instead run a local CUPS server, and add remote printers to that
>>> local
>>> server.
>>>
>>> jh
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [Marketing Mail] Re: Cups freeze when remote server is unavailable

[Lange, Markus]

Hi,

John tries to tell you:
Revert your configuration changes to the config file and use the local
web interface / lp* / GUI Print Server Configuration tool to setup all
printers at work and / or at home using these tools.

This method needs a local cups instance that works if your OS is
running (if a printer is not reachable for printing cups can still keep
the job in it's queue until the printer is reachable).
You can find an linux.com article on Printer Setups in [1] (mainly
selected for its screenshots of cups web interface and not for its
actuality) which should give you all information's to get it work.

At least for desktop setups cups should be running by default, see
"systemctl status cups" to check if it's running.

For a more in-depth view on cups I can recommend reading the archwiki
[2].

best regards
Markus

[1] https://www.linux.com/learn/linux-101-printing
[2] https://wiki.archlinux.org/index.php/CUPS


On Mon, 2018-10-29 at 15:35 +0100, Patrick Bégou wrote:
> Hi John
> 
> thanks for your quick reply. If it is not a bug, as I was reading on
> the
> web, it is some misunderstanding from me.
> Running cups 1.4.2 (CentOS6) I was using the "BrowsePoll" directive
> in
> cupsd.conf. So the printers were automatically known from the central
> server of the lab. And home printers were working fine with this
> setup too.
> In CentOS7, with cups 1.6.3, this directive does not exist any more
> and
> reading the doc I had understood that it was replaced by the
> client.conf
> file. Reading your answer suggest it is not true.
> 
> So could you tell me or suggest reading on the right manner to
> reproduce
> my previous centos6 setup ?
> 
> Sorry for this newbie question, I'm not very familiar with cups
> setup.
> 
> Patrick
> 
> 
> Le 29/10/2018 à 14:45, John Hodrien a écrit :
> > On Mon, 29 Oct 2018, Patrick Bégou wrote:
> > 
> > > Any idea ?
> > 
> > I don't see that this is a bug.
> > 
> > In client.conf you're telling it which server to use, exclusively. 
> > You're not
> > adding remote printers, you're telling it which CUPS server to talk
> > to
> > everytime you use CUPS clients commands.  You don't even need to
> > run a
> > local
> > CUPS server if you configure it like this.
> > 
> > If you want a machine to work at both ends, I'd suggest you don't
> > do
> > this, and
> > instead run a local CUPS server, and add remote printers to that
> > local
> > server.
> > 
> > jh
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> > 
> 
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cups freeze when remote server is unavailable

[Patrick Bégou]

Hi John

thanks for your quick reply. If it is not a bug, as I was reading on the
web, it is some misunderstanding from me.
Running cups 1.4.2 (CentOS6) I was using the "BrowsePoll" directive in
cupsd.conf. So the printers were automatically known from the central
server of the lab. And home printers were working fine with this setup too.
In CentOS7, with cups 1.6.3, this directive does not exist any more and
reading the doc I had understood that it was replaced by the client.conf
file. Reading your answer suggest it is not true.

So could you tell me or suggest reading on the right manner to reproduce
my previous centos6 setup ?

Sorry for this newbie question, I'm not very familiar with cups setup.

Patrick


Le 29/10/2018 à 14:45, John Hodrien a écrit :
> On Mon, 29 Oct 2018, Patrick Bégou wrote:
>
>> Any idea ?
>
> I don't see that this is a bug.
>
> In client.conf you're telling it which server to use, exclusively. 
> You're not
> adding remote printers, you're telling it which CUPS server to talk to
> everytime you use CUPS clients commands.  You don't even need to run a
> local
> CUPS server if you configure it like this.
>
> If you want a machine to work at both ends, I'd suggest you don't do
> this, and
> instead run a local CUPS server, and add remote printers to that local
> server.
>
> jh
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cups freeze when remote server is unavailable

[John Hodrien]

On Mon, 29 Oct 2018, Patrick Bégou wrote:


Any idea ?


I don't see that this is a bug.

In client.conf you're telling it which server to use, exclusively.  You're not
adding remote printers, you're telling it which CUPS server to talk to
everytime you use CUPS clients commands.  You don't even need to run a local
CUPS server if you configure it like this.

If you want a machine to work at both ends, I'd suggest you don't do this, and
instead run a local CUPS server, and add remote printers to that local server.

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Cups freeze when remote server is unavailable

[Patrick Bégou]

Hi,

I have a setup problem with cups on my CentOS7 laptop.

In client.conf If have set the cups server FDQN used at work

ServerName servprint.lmy.lab.fr


But when I'm at home if I do not comment this line with:

# ServerName servprint.lmy.lab.fr


cups freeze as soon as I try to print something on my local home printer
as the remote server is unreachable.

This seams to be an old 2012 bug (see
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1050422) but I'm
unable to find any work around 6 years later!

My cups in CentOS7 is cups-1.6.3-35.el7.x86_64


Any idea ?



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IBM buying RedHat

[Hakan Koseoglu]

On Sun, 28 Oct 2018 at 23:23, Valeri Galtsev 
wrote:

>
> 2. Does anybody still remember OS/2 which lost userbase to MS Windows for
> workgroups, but IBM still supported it for quite long period of time. And
> OS/2 was much better IMHO.
>
>
As a long-time OS/2 user, I do remember, and damn what a miserable life
that was. As soon as I had wound my BBS down (which was running on Maximus
on OS/2), I had switched my home server around to Linux since I preferred
it way way more. Using any new hardware, or a decent graphics card was a
constant struggle and IBM wouldn't care much.

Support as in life support is as good as none.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IBM buying RedHat

[Simon Matter]

>
> On Sun, October 28, 2018 6:07 pm, mark wrote:
>> On 10/28/18 17:54, Zube wrote:
>>> On Sun Oct 28 10:20:31 PM, Alain péan wrote:
>>>
 Le 28/10/2018 à 22:10, Albert McCann a écrit :
> Damn, this is bad enough to make one weep.

 Red Hat would stay as a distinct entity inside IBM. IBM has also
 contributed to Free software, and especially Linux kernel.
 I don't know how bad it is and the implications for CentOS...
>>>
>>> That old war wound started aching again.
>>>
>>> IBM:Redhat :: Oracle:Sun
>>
>> Actually, it could have been *much8 worse: *Oracle* could have bought
>> RH.
>>
>> That *really* would have been an order of magnitude worse.
>>
>
> I like the fact that it was IBM who bought RedHat. I remember several good
> things about IBM:
>
> 1. Postfix. Vietse Venema wrote it at IBM Thomas J. Watson Research
> Center, and IBM was really happy to release MTA written with security in
> mind under IBM Public License 1.0 which is a free software license - for
> everybody to use.

That's one example but I think there is much more in the history of IBM
when looking back.

To me it seems like, if they are smart, they will try to push IBM POWER
and RedHat Linux together to establish real competition in the hardware
market again (and of course don't forget to keep Fedora/CentOS alive)!

Regards,
Simon

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Setting up sendmail to mail system messages on CentOS 6 and 7

[Sorin Srbu]

> -Original Message-
> From: CentOS  On Behalf Of Alexander Dalloz
> Sent: den 26 oktober 2018 16:05
> To: centos@centos.org
> Subject: Re: [CentOS] Setting up sendmail to mail system messages on
> CentOS 6 and 7
> 
> Am 26.10.2018 um 14:44 schrieb Sorin Srbu:
> > Here is a typical guide I've used for CentOS  6, and that I've used for
the
> > problem server above as well as for other CentOS 7-machines.
> >  centos>
> 
> That "guide" is not really useful nor clever. In a scenario like yours,
> you would setup Sendmail as a nullclient. That's documented in
> cf/README. Or even drop Sendmail and choose a software like msmtp or
> ssmtp which is dedicated for such purpose. You don't need the MTA
> functionality of Sendmail.

I'll look those up. The suggestions makes a lot of sense.


> > Is setting up sendmail different on CentOS 7 in any way, as compared to
> > CentOS 6??
> 
> Not really.

Thanks.


> > Anything else I should double-check?
> 
> Your logs will tell you what is happening and where to look at closer.
> If you like to get specific help from this list I feel you should
> provide your sendmail.mc and log content demonstrating your issue(s).

Gotcha'.

This morning I found a load of "This message hasn't been delivered
yet" mails in my inbox.
Turns out the central uni mail filter had intercepted all my test mails from
the very beginning.

Previous log messages stated the mails had been accepted for delivery from
the mail servers and I took their word for it.

What I missed was these messages that came in slightly later; "First-time
sender tempfailed as anti-spam measure; please try again in 720 minutes..."

I'll have a talk with the central support and see if they can't ease up on
this.

Thanks everybody for your assistance as well as suggestions!

--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Setting up sendmail to mail system messages on CentOS 6 and 7

[Sorin Srbu]

> -Original Message-
> From: CentOS  On Behalf Of Fred Smith
> Sent: den 29 oktober 2018 03:23
> To: centos@centos.org
> Subject: Re: [CentOS] Setting up sendmail to mail system messages on
> CentOS 6 and 7
> 
> On Mon, Oct 29, 2018 at 10:38:10AM +0900, マスターズ・イアン wrote:
> > On 2018/10/27 21:00, centos-requ...@centos.org wrote:
> > >I've previously configured sendmail to send system messages on selected
> > >servers running CentOS 6. Usually they just kinda' work out of the box. No
> > >problems to speak of.
> > >
> > >However most of my CentOS 7-servers are rather flakey when it comes to
> > >sendmail. Most of the time they just won't send mails for whatever
> reason.
> > >Further, most of the time I can get it working, it's usually about a
> > >firewall rule not set, the firewall not having been reloaded or some simple
> > >such.
> >
> > Another thing to try would be Postfix. I've always found that very easy to
> use and also requires almost no configuration:
> > https://www.server-world.info/en/note?os=CentOS_7=mail=1 (on
> the same site, a lot of very useful CentOS7 info)
> >
> > Usually for local servers, all I do is:
> > 1. Add root alias in /etc/aliases
> > 2. Run 'newaliases'
> > 3. Send test mail:
> > echo "test from `hostname`" | mail -s 'mail test' me@address
> >
> > That's all.
> >
> > ian
> 
> Probably not helpful, but I run a home mailserver, always used sendmail.
> Spent 15 years slowly accumulating a functioning sendmail.mc. When I
> bring up a new system I just carry over the sendmail.mc, compile it,
> restart sendmail and voila. EL7 was no different than EL6 in that regard.

Thanks, that actually helps for starters. No difference then.

--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos