On Tue, Mar 08, 2016 at 09:00:44AM -0500, mechy2k2000 wrote:
> I think nearly all the fedora images are live CDs now. They should have an
> option to install fedora when you boot the cd. Usually when you boot the
> cd. A window appears asking to either install the os or try it out. If you
> are using a non gnome cd,you may have to search the application menu for
> the installer
At one point, at least the LiveCD had a bunch of limitations, possibly on
partitioning, and also on package selection. I don't know if that's still
true.
However, there are also the server and workstation spins. If you are
looking for the usual Gnome desktop, you probably want workstation. I usue
server, choose minimal install and add things afterwards.
The Fedora site itself has the live one by default. Their logic is that
the newcomer will have the best chance of success with that one, and the
more experienced will go elsewhere. Their site,
https://getfedora.org/, shows server and workstation images for download.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
On Tue, Mar 8, 2016 at 9:28 AM, Scott Robbins <scottro11(a)gmail.com> wrote:
> On Tue, Mar 08, 2016 at 09:00:44AM -0500, mechy2k2000 wrote:
> > I think nearly all the fedora images are live CDs now. They should have
> an
> > option to install fedora when you boot the cd. Usually when you boot the
> > cd. A window appears asking to either install the os or try it out. If
> you
> > are using a non gnome cd,you may have to search the application menu for
> > the installer
>
> At one point, at least the LiveCD had a bunch of limitations, possibly on
> partitioning, and also on package selection. I don't know if that's still
> true.
>
Still true.
Anaconda doesn't handle LVM on Software RAID properly. Maybe it will be
fixed when F24 releases this summer.
https://bugzilla.redhat.com/show_bug.cgi?id=1225184
There may be other limitations as well.
The work around is to use the netinstall image.
The server images are a different set of packages apparently and is said to
require a bunch of work to make a server install a workstation install in
the end. So I'd advise against that and instead netinstall (worked for me).
>
> However, there are also the server and workstation spins. If you are
> looking for the usual Gnome desktop, you probably want workstation. I usue
> server, choose minimal install and add things afterwards.
>
> The Fedora site itself has the live one by default. Their logic is that
> the newcomer will have the best chance of success with that one, and the
> more experienced will go elsewhere. Their site,
> https://getfedora.org/, shows server and workstation images for download.
--
---~~.~~---
Mike
// SilverTip257 //
Hi Rafal,
On Thu, Oct 6, 2016 at 5:57 PM, Rafal Skolasinski <r.j.skolasinski(a)gmail.com
> wrote:
> Thanks for detailed information! I am using playbooks to create vms on a
> remote host and then I want to run another playbook to configure them.
>
For me, the most amazing feature of Vagrant was to be able to use just one
Vagrantfile to control both local development VMs, to production servers,
and to change from one to the other with just one command. There are
Vagrant plugins for pretty much every provider with an API: big "cloud"
providers like AWS, Google Cloud or Azure, VPS hosters like Digital Ocean,
Vultr or Linode, and also other cloud solutions like OpenShift, OpenStack
and CloudStack. You can also use the libvirt plugin with both local and
remote servers, it comes with plugins for most virtualization providers and
Docker, and there's even a plugin for dedicated servers (when there's no
API for controlling their creation and destruction). Being able to do:
vagrant up --provider virtualbox
vagrant up --provider aws
vagrant up --provider digitalocean
and move seamlessly between providers, provisioning everything with
Ansible, is just priceless. I wouldn't go back to plain Ansible and writing
dynamic inventory scripts.
> I want to enable password authentication only for a moment of initial
> configuration and then disable it again - I believe this should[n't] cause
> any security risk.
>
The risk is small, but not zero. If someone's script hits your server in a
critical moment, your server becomes his. This is not just theoretical:
during Blaster (a Windows worm), a former colleague had installed Windows
2000 more than 12 times, and went directly to download the hotfix from
Microsoft, which took less than a minute - and got infected every single
time. And I've heard people complaining about getting hacked in the first 5
minutes after imaging a new Linux VPS, before they had the time to disable
password logins (they had chosen their own passwords - apparently not that
unique). But that's for you to decide - good luck! :)
Best regards,
Laurențiu
Thanks!
BTW. I just noticed that every user on vms created with Vagrant is in fact
admin... one can always
```
su - vagrant
```
On 6 October 2016 at 20:30, Laurențiu Păncescu <lpancescu(a)gmail.com> wrote:
> Hi Rafal,
>
> On Thu, Oct 6, 2016 at 5:57 PM, Rafal Skolasinski <
> r.j.skolasinski(a)gmail.com> wrote:
>
>> Thanks for detailed information! I am using playbooks to create vms on a
>> remote host and then I want to run another playbook to configure them.
>>
>
> For me, the most amazing feature of Vagrant was to be able to use just one
> Vagrantfile to control both local development VMs, to production servers,
> and to change from one to the other with just one command. There are
> Vagrant plugins for pretty much every provider with an API: big "cloud"
> providers like AWS, Google Cloud or Azure, VPS hosters like Digital Ocean,
> Vultr or Linode, and also other cloud solutions like OpenShift, OpenStack
> and CloudStack. You can also use the libvirt plugin with both local and
> remote servers, it comes with plugins for most virtualization providers and
> Docker, and there's even a plugin for dedicated servers (when there's no
> API for controlling their creation and destruction). Being able to do:
>
> vagrant up --provider virtualbox
> vagrant up --provider aws
> vagrant up --provider digitalocean
>
> and move seamlessly between providers, provisioning everything with
> Ansible, is just priceless. I wouldn't go back to plain Ansible and writing
> dynamic inventory scripts.
>
>
>> I want to enable password authentication only for a moment of initial
>> configuration and then disable it again - I believe this should[n't] cause
>> any security risk.
>>
>
> The risk is small, but not zero. If someone's script hits your server in a
> critical moment, your server becomes his. This is not just theoretical:
> during Blaster (a Windows worm), a former colleague had installed Windows
> 2000 more than 12 times, and went directly to download the hotfix from
> Microsoft, which took less than a minute - and got infected every single
> time. And I've heard people complaining about getting hacked in the first 5
> minutes after imaging a new Linux VPS, before they had the time to disable
> password logins (they had chosen their own passwords - apparently not that
> unique). But that's for you to decide - good luck! :)
>
> Best regards,
> Laurențiu
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
>
On Jun 28, 2016, at 11:17 AM, Peter Q. <btoven66(a)gmail.com> wrote:
>
> What will happen with Centos and .NET?
I’d expect it to show up in SCL at some point:
https://wiki.centos.org/AdditionalResources/Repositories/SCL
Until then, the CentOS build instructions on Microsoft’s official download page work just fine, at least on EL7:
https://www.microsoft.com/net/core#centos
RC3 apparently just shipped, which has caused some version incompatibilities in the .NET package repositories. I was able to get the default C# “hello, world” project to build and run:
$ mkdir test
$ cd test
$ dotnet new --lang c#
$ dotnet restore
$ dotnet build
$ dotnet run
Hello World!
...but the F# project (--lang f#) chokes due to a version incompatibility. This should shake out soon.
Beware that .NET Core is not the same thing as .NET. It is very much stripped down compared to the Windows .NET platform. It is mainly intended for headless server-side applications, like serving ASP.NET sites.
> In the side of security and stability.
I’m guessing you’re asking if .NET Core will be secure. I assume it will be as secure as any VM type interpreter, such as Java or Flash. That is to say, theoretically quite secure, but in practice only as secure the platform’s maintainers put in the effort to make it secure. My advice: wrap it in SELinux, VMs, chroots, etc., just as you would any other executable code you want walled off from the rest of your infrastructure.
As for stability, it’s still pre-1.0. Don’t bet your business on it today. If you need a stable .NET implementation for Linux today, use Mono.
Hi for some reason I am still getting an error:
[root@centos-mirrors ~]# ./rsync-verbose.sh
msync.CentOS.org rsync service (centosz7)
---------------------------------------
This service is intended for the sole use of the CentOS worldwide mirror network
to synchronize mirrors.
Unless you are running or intending to run a listed public CentOS mirror
use a mirror listed at http://centos.org/download/mirrors
If you intend to populate a mirror for public use please read the
notes at http://wiki.centos.org/HowTos/CreatePublicMirrors
If you do use this service then it is implied that you are providing a
mirror for public use and giving us authority to publicise such mirror.
@ERROR: Unknown module 'CentOS'
rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]
here's my command:
rsync -vazH --delete msync.centos.org::CentOS /srv
On 10/03/2016 01:55 AM, Fabian Arrotin wrote:
[cid:FTN_BSI_4044b8d1-d867-4aee-a026-4bf5a385f7a6.jpg]
[cid:Facebook_e6944a85-19e9-4b56-ab43-2e59071f60c7.png]<https://www.facebook.com/FORETHOUGHT.net>[cid:Google+_36fad311-d99c-436d-a0cd-dae57ea35b35.png]<https://plus.google.com/+FORETHOUGHTnetDenver>[cid:LinkedIn_8002c88d-8375-454f-9e8e-69c9388d702a.png]<https://www.linkedin.com/company/forethought.net>[cid:Twitter_4f042d7a-eca9-43f6-8e69-d4a5eb2d70ab.png]<https://twitter.com/forethoughtnet>
“Forethought.net has been a definite improvement over our
previous “big name” provider and they promptly resolve any small concerns that
may come up.” - Sarah B, Lifetime Windows and
SidingOn 01/10/16 21:10, Jawaid Bazyar wrote:
Please add IP 206.124.13.171 for mirror repos.forethought.net.
We will change IP once we can rsync from the new IP.
Updated, and older ip address removed (so replaced by the new one)
Cheers,
_______________________________________________
CentOS-mirror mailing list
CentOS-mirror(a)centos.org<mailto:CentOS-mirror@centos.org>
https://lists.centos.org/mailman/listinfo/centos-mirror
On 4/7/2016 12:04 AM, Chandran Manikandan wrote:
> Still no luck .
> I have tried your commands in root folder.
> It's showing max size 384 only in home directory.
>
> But if i try df -h shown 579.
>
> Is there any way to find out recycle bin folder
Linux shell has no such thing as a recycle bin, thats a windows thing
(some linux graphical desktops might create one in for a user's files,
it would be in his /home/username somewhere).
df -h shows a lot of info, for instance on one of my servers, I see...
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_free-lv_root
50G 7.7G 39G 17% /
tmpfs 12G 0 12G 0% /dev/shm
/dev/sda1 477M 146M 306M 33% /boot
/dev/mapper/vg_free-lv_home
30G 7.1G 23G 25% /home
/dev/mapper/vg_free-lvpgsql
30G 671M 30G 3% /var/lib/pgsql
/dev/mapper/vg_free-lvimages
150G 61G 90G 41% /var/lib/libvirt/images
/dev/mapper/vgdata-lvhome2
1.8T 470G 1.4T 26% /home2
# du -hs /home/*
398M /home/downloads
16K /home/ipsloth
16K /home/junk
4.1G /home/observers
32M /home/pierce
2.5G /home/scac
2.5GB + 4.1 GB + the odds and ends there adds up to pretty close to the
7.1GB 'used' in the /home file system.
--
john r pierce, recycling bits in santa cruz
Sent from BlackBerry Passport
Original Message
From: centos-request(a)centos.org
Sent: Saturday, March 12, 2016 5:30 PM
To: centos(a)centos.org
Reply To: centos(a)centos.org
Subject: CentOS Digest, Vol 134, Issue 12
Send CentOS mailing list submissions to
centos(a)centos.or',g
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos
or, via email, send a message with subject or body 'help' to
centos-request(a)centos.org
You can reach the person managing the list at
centos-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS digest..."
Today's Topics:
1. CentOS-announce Digest, Vol 133, Issue 5
(centos-announce-request(a)centos.org)
2. Re: Openshot 2.x (beta) on C7?? (Chris Beattie)
3. Re: Openshot 2.x (beta) on C7?? (Nux!)
4. CentOS 7 and display managers (m.roth(a)5-cent.us)
5. Re: CentOS 7 and display managers (Richard)
6. Re: CentOS 7 and display managers (m.roth(a)5-cent.us)
7. Re: CentOS 7 and display managers (Valeri Galtsev)
8. Re: CentOS 7 and display managers (m.roth(a)5-cent.us)
9. Re: CentOS 7 and display managers (Frank Cox)
10. Re: CentOS 7 and display managers (Scot P. Floess)
11. Centos and automatic update on server (Alessandro Baggi)
12. Re: Centos and automatic update on server (Alice Wonder)
13. Re: Centos and automatic update on server (m.roth(a)5-cent.us)
14. Re: Centos and automatic update on server (m.roth(a)5-cent.us)
15. Re: Centos and automatic update on server (David Nelson)
----------------------------------------------------------------------
Message: 1
Date: Fri, 11 Mar 2016 12:00:02 +0000
From: centos-announce-request(a)centos.org
To: centos-announce(a)centos.org
Subject: [CentOS] CentOS-announce Digest, Vol 133, Issue 5
Message-ID: <mailman.5.1457697602.15401.centos-announce(a)centos.org>
Content-Type: text/plain; charset="us-ascii"
Send CentOS-announce mailing list submissions to
centos-announce(a)centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request(a)centos.org
You can reach the person managing the list at
centos-announce-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CESA-2016:0428 Moderate CentOS 6 libssh2 Security Update
(Johnny Hughes)
2. CESA-2016:0428 Moderate CentOS 7 libssh2 Security Update
(Johnny Hughes)
3. CESA-2016:C001 ipa and glusterfs Update (Johnny Hughes)
4. CESA-2016:0430 Important CentOS 7 xerces-c Security Update
(Johnny Hughes)
----------------------------------------------------------------------
Message: 1
Date: Thu, 10 Mar 2016 12:05:04 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CESA-2016:0428 Moderate CentOS 6 libssh2
Security Update
Message-ID: <20160310120504.GA20915(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:0428 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0428.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
3dd5f11872a5254b65711f88a89b4400c87329ed185af7d69d1d705f94abe13d libssh2-1.4.2-2.el6_7.1.i686.rpm
c00dbe2421aada7e7eb2bc87e5160014aae7673e684011783dc34cfa9dd1fcae libssh2-devel-1.4.2-2.el6_7.1.i686.rpm
4be2256b4afe177140a3e87fdc0061d76b3f142ef7264aeb0f9d7a8b5b8fe3b7 libssh2-docs-1.4.2-2.el6_7.1.i686.rpm
x86_64:
3dd5f11872a5254b65711f88a89b4400c87329ed185af7d69d1d705f94abe13d libssh2-1.4.2-2.el6_7.1.i686.rpm
729dc417c94e9efbe67f10fe848ce3571945f054bd87fec428179b58dd09bef6 libssh2-1.4.2-2.el6_7.1.x86_64.rpm
c00dbe2421aada7e7eb2bc87e5160014aae7673e684011783dc34cfa9dd1fcae libssh2-devel-1.4.2-2.el6_7.1.i686.rpm
2004db099a3302057dbf799c09012d8d9bc1360ddf043ecef2e485f0b3b7fc86 libssh2-devel-1.4.2-2.el6_7.1.x86_64.rpm
d2faf5949f869b6b295c3241707e3f40a74f7c1862da57daaaca77aabce535aa libssh2-docs-1.4.2-2.el6_7.1.x86_64.rpm
Source:
042b1f294e214d514f5b16332956e168cc168c90a416bcfe4bbc1625636581fc libssh2-1.4.2-2.el6_7.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
Twitter: @JohnnyCentOS
------------------------------
Message: 2
Date: Thu, 10 Mar 2016 12:53:35 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CESA-2016:0428 Moderate CentOS 7 libssh2
Security Update
Message-ID: <20160310125335.GA39205(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:0428 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0428.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
3a25e00b04b27ba59fa17adb97791702dcccb56e130eb5f51651d6fe4fe42f89 libssh2-1.4.3-10.el7_2.1.i686.rpm
1e1f93e449e678597bfdd99bed306c9bb8d5b513ffcaea13d32f5b7434900300 libssh2-1.4.3-10.el7_2.1.x86_64.rpm
e76bdc2e93bbb6c4ac8705d50eef1f114ee8b8674e8436063359ac5518b10191 libssh2-devel-1.4.3-10.el7_2.1.i686.rpm
b176ee6feaf699eb9ed7466309ab9a9e8d6a7cccaf2e38a15093c484dbd22548 libssh2-devel-1.4.3-10.el7_2.1.x86_64.rpm
f76b77eed1cc006c0947abd138084a5808d97b311ebf0e13fbf3504248698f4e libssh2-docs-1.4.3-10.el7_2.1.noarch.rpm
Source:
2181b44f7d4636eb0920582a519d1adabae94f34cb49c531a5a2b31e2ad4cf57 libssh2-1.4.3-10.el7_2.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
Twitter: @JohnnyCentOS
------------------------------
Message: 3
Date: Thu, 10 Mar 2016 17:33:15 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CESA-2016:C001 ipa and glusterfs Update
Message-ID: <20160310173315.GA44278(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and BugFix Advisory 2016:C001
Upstream details at : https://bugs.centos.org/view.php?id=10538
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
96963d839797a7601ef6a4922c94e7ef82b42fcb70533f9a31c43adceee2fb19 glusterfs-3.7.1-16.0.1.el7.centos.x86_64.rpm
0edd9669023af5881cd554a25f11af30c4ad1cec2ac515355a55541ca5afd444 glusterfs-api-3.7.1-16.0.1.el7.centos.x86_64.rpm
1ff4ab3dee2755555db663d522929c45949544d023f0af862e595234eb206b1e glusterfs-api-devel-3.7.1-16.0.1.el7.centos.x86_64.rpm
310cdbc4645b1dff02f7fd1ab15ca11f3d2b65a49e684a3015de264cc9055d2d glusterfs-cli-3.7.1-16.0.1.el7.centos.x86_64.rpm
7ebb8186125e4246b0ba612961872e3a6229351d15c6849c9b4d3d57587005f0 glusterfs-client-xlators-3.7.1-16.0.1.el7.centos.x86_64.rpm
fb6f197ac33e79768892ec98548521cba9dbabbaf6dd577a1b9d09c461c344bc glusterfs-devel-3.7.1-16.0.1.el7.centos.x86_64.rpm
c50c59c56d305efd2caaf49f9a03a934f60d6d60b9ede5fa6f9c7c41d4d0af3e glusterfs-fuse-3.7.1-16.0.1.el7.centos.x86_64.rpm
8eb112d7a006b9edcf0a6dce79abb6018909c8d9b6baa645f623f5cc4a38a837 glusterfs-libs-3.7.1-16.0.1.el7.centos.x86_64.rpm
959d24d812bb0679000f78d9e17b13476e424bb811b159eea8632d98dd2b46a3 glusterfs-rdma-3.7.1-16.0.1.el7.centos.x86_64.rpm
be195e50fcbd3c190e90ecbe5690a664e01bf953ae29be709a4a6aba662736bb ipa-admintools-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
46df2769ffc4e7439ddd6a8a140b0afcb4f45204aa717dbe4fc027dd4c5dda71 ipa-client-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
c64d59f138beb4fb8a8a3a200c7696213eebf5c07ac50bb43a7faaadd1b5b9c0 ipa-python-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
c20a31a1e4ac386e50c55839ef25b4ad1b3c261d60981da35d7c0d6a7d773ee9 ipa-server-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
9accd7c6001f0f0c02b37eae8538e3045eaaf0f04008d5202fd4007368ba0a64 ipa-server-dns-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
5a5a91ff922ba863eef85723f589d3c940d2e8e529683ca811016688f7bcc95a ipa-server-trust-ad-4.2.0-15.0.1.el7.centos.6.x86_64.rpm
2bc01ee09379a075724d311ff883fac2564ac27826a5b4ee0d4c7c09492a75c4 python-gluster-3.7.1-16.0.1.el7.centos.x86_64.rpm
Source:
e2ca01712e5f0c52b16a9397597ca15597bccf692881404f695f6cec8f97d925 glusterfs-3.7.1-16.0.1.el7.centos.src.rpm
febdf5cf5065c93fb4ba44c02f3ac44bfe1a02b2ff5c489e3a4ec8556c99762f ipa-4.2.0-15.0.1.el7.centos.6.src.rpm
NOTE: This rebuild was done to all the packages to have a DIST tag of .el7.centos.
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos at irc.freenode.net
------------------------------
Message: 4
Date: Thu, 10 Mar 2016 17:35:16 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CESA-2016:0430 Important CentOS 7 xerces-c
Security Update
Message-ID: <20160310173516.GA44370(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:0430 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0430.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
0102baca3c47fdb3a16d421d42be3c2e1944ef95cf0bad1b42d01e8fda4d5f83 xerces-c-3.1.1-8.el7_2.i686.rpm
06c92060b15956706630e2d2fd84d72ad71db65151b4435828980d869a7d4f11 xerces-c-3.1.1-8.el7_2.x86_64.rpm
9009f3e814779b14a0e0d6a75fbe555804f2a031e70b15309fe6734205c1c4d2 xerces-c-devel-3.1.1-8.el7_2.i686.rpm
dad423ae642a29be177bb4825f71ad3fa5d8db98c4ee658f12094e30c3a88d04 xerces-c-devel-3.1.1-8.el7_2.x86_64.rpm
7fbb6adaf2adb7f3dbf34bf3f2c9e9ea4da1bd61660d84856189583511eec395 xerces-c-doc-3.1.1-8.el7_2.noarch.rpm
Source:
95181791907cd7b8bc12c5814cf8e8182aec7dd51faa88224c6f1ec3f4a2336c xerces-c-3.1.1-8.el7_2.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
Twitter: @JohnnyCentOS
------------------------------
_______________________________________________
CentOS-announce mailing list
CentOS-announce(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 133, Issue 5
***********************************************
------------------------------
Message: 2
Date: Fri, 11 Mar 2016 15:53:29 +0000
From: Chris Beattie <cbeattie(a)geninfo.com>
To: 'CentOS mailing list' <centos(a)centos.org>
Subject: Re: [CentOS] Openshot 2.x (beta) on C7??
Message-ID:
<C56CB550F3B0CC428EFC662940A0C2E6A70634F8(a)EX10MS2.geninfo.com>
Content-Type: text/plain; charset="us-ascii"
On 3/11/2016 2:02 AM, Sorin Srbu wrote:
>>> Looks like installing openshot 2.x on C7 isn't as trivial
>>
>> It is not trivial at all. The best way to handle this will be to find the
>> required packages in Fedora and rebuild them.
>
> So what's the easy way?
>
> Switch to Ubuntu or something? 8-O
Maybe Fedora, maybe Ubuntu? It's more time-consuming than hard to build a virtual machine these days, and it's not even that time-consuming. Is there a distro that already has what you want all packaged up? Run it in a VM. Take a snapshot first if you want to try something potentially system-breaking or that's going to spew files everywhere. On a single-user machine, the performance should be within a few percent of running on the bare metal. So, if you test drive some beta software and it doesn't perform well on a VM, it's probably not going to be much better running on a same-spec physical machine.
NB: I administer several hundred virtual desktops, so I chugged rather than sipped the virtualization Kool-Aid. :-)
--
-Chris
------------------------------
Message: 3
Date: Fri, 11 Mar 2016 16:07:24 +0000 (GMT)
From: Nux! <nux(a)li.nux.ro>
To: CentOS mailing list <centos(a)centos.org>
Subject: Re: [CentOS] Openshot 2.x (beta) on C7??
Message-ID: <1470053539.78961.1457712444140.JavaMail.zimbra(a)li.nux.ro>
Content-Type: text/plain; charset=utf-8
Ubuntu in a docker?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Chris Beattie" <cbeattie(a)geninfo.com>
> To: "CentOS mailing list" <centos(a)centos.org>
> Sent: Friday, 11 March, 2016 15:53:29
> Subject: Re: [CentOS] Openshot 2.x (beta) on C7??
> On 3/11/2016 2:02 AM, Sorin Srbu wrote:
>>>> Looks like installing openshot 2.x on C7 isn't as trivial
>>>
>>> It is not trivial at all. The best way to handle this will be to find the
>>> required packages in Fedora and rebuild them.
>>
>> So what's the easy way?
>>
>> Switch to Ubuntu or something? 8-O
>
> Maybe Fedora, maybe Ubuntu? It's more time-consuming than hard to build a
> virtual machine these days, and it's not even that time-consuming. Is there a
> distro that already has what you want all packaged up? Run it in a VM. Take a
> snapshot first if you want to try something potentially system-breaking or
> that's going to spew files everywhere. On a single-user machine, the
> performance should be within a few percent of running on the bare metal. So,
> if you test drive some beta software and it doesn't perform well on a VM, it's
> probably not going to be much better running on a same-spec physical machine.
>
> NB: I administer several hundred virtual desktops, so I chugged rather than
> sipped the virtualization Kool-Aid. :-)
>
> --
> -Chris
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos
------------------------------
Message: 4
Date: Fri, 11 Mar 2016 11:33:57 -0500
From: m.roth(a)5-cent.us
To: "CentOS" <centos(a)centos.org>
Subject: [CentOS] CentOS 7 and display managers
Message-ID:
<19814dd6ca3be28d95ab776fd52cbb58.squirrel(a)host290.hostmonster.com>
Content-Type: text/plain;charset=utf-8
<rant>
Dear gnome developers - could you *possibly* be more anti-Unix? I mean,
thanks *so* much for trying to turn Linux into Windows or Macs....
</rant>
So, now that I've gotten that out, the KDE display manager, on the login
screen, easily lets you choose window managers. Gnome utterly refuses to
consider such an idea.
I've just yum groupinstall "KDE Plasma Workspaces" on one of my user's new
system... and I cannot figure out, not in googling, and there's nothing
vaguely obvious anywhere, how to change to KDE from gnome.
Anyone got a pointer?
mark, frustrated
------------------------------
Message: 5
Date: Fri, 11 Mar 2016 16:42:34 +0000
From: Richard <lists-centos(a)listmail.innovate.net>
To: CentOS mailing list <centos(a)centos.org>
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID: <D655042E52FAB736EED4FCD8(a)ritz.innovate.net>
Content-Type: text/plain; charset=us-ascii
> Date: Friday, March 11, 2016 11:33:57 -0500
> From: m.roth(a)5-cent.us
>
> So, now that I've gotten that out, the KDE display manager, on the
> login screen, easily lets you choose window managers. Gnome utterly
> refuses to consider such an idea.
>
> I've just yum groupinstall "KDE Plasma Workspaces" on one of my
> user's new system... and I cannot figure out, not in googling, and
> there's nothing vaguely obvious anywhere, how to change to KDE from
> gnome.
>
With gnome there is a "gear wheel" on the password entry page -- on
the right below the password box, next to the "sign in" label. If I
select it I can switch between gnome and mate. Does KDE show there as
an option?
------------------------------
Message: 6
Date: Fri, 11 Mar 2016 11:46:20 -0500
From: m.roth(a)5-cent.us
To: "CentOS mailing list" <centos(a)centos.org>
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID:
<8f02f00958f1b8f56d9235b4bf7a0564.squirrel(a)host290.hostmonster.com>
Content-Type: text/plain;charset=utf-8
Richard wrote:
>
>
>> Date: Friday, March 11, 2016 11:33:57 -0500
>> From: m.roth(a)5-cent.us
>>
>> So, now that I've gotten that out, the KDE display manager, on the
>> login screen, easily lets you choose window managers. Gnome utterly
>> refuses to consider such an idea.
>>
>> I've just yum groupinstall "KDE Plasma Workspaces" on one of my
>> user's new system... and I cannot figure out, not in googling, and
>> there's nothing vaguely obvious anywhere, how to change to KDE from
>> gnome.
>
> With gnome there is a "gear wheel" on the password entry page -- on
> the right below the password box, next to the "sign in" label. If I
> select it I can switch between gnome and mate. Does KDE show there as
> an option?
Fascinating. Not in ours. It displays our issue, and in the upper left,
some icons that let you deal with sound, I think, connection, maybe, and I
forget what else.
mark
------------------------------
Message: 7
Date: Fri, 11 Mar 2016 10:52:12 -0600 (CST)
From: "Valeri Galtsev" <galtsev(a)kicp.uchicago.edu>
To: "CentOS mailing list" <centos(a)centos.org>
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID:
<13369.128.135.52.6.1457715132.squirrel(a)cosmo.uchicago.edu>
Content-Type: text/plain;charset=iso-8859-1
On Fri, March 11, 2016 10:46 am, m.roth(a)5-cent.us wrote:
> Richard wrote:
>>
>>
>>> Date: Friday, March 11, 2016 11:33:57 -0500
>>> From: m.roth(a)5-cent.us
>>>
>>> So, now that I've gotten that out, the KDE display manager, on the
>>> login screen, easily lets you choose window managers. Gnome utterly
>>> refuses to consider such an idea.
>>>
>>> I've just yum groupinstall "KDE Plasma Workspaces" on one of my
>>> user's new system... and I cannot figure out, not in googling, and
>>> there's nothing vaguely obvious anywhere, how to change to KDE from
>>> gnome.
>>
>> With gnome there is a "gear wheel" on the password entry page -- on
>> the right below the password box, next to the "sign in" label. If I
>> select it I can switch between gnome and mate. Does KDE show there as
>> an option?
>
> Fascinating. Not in ours. It displays our issue, and in the upper left,
> some icons that let you deal with sound, I think, connection, maybe, and I
> forget what else.
In my case the gear which when clicked of gives you drop down choices of
Desktop Environments (DE) installed appears only after I click on
particular user. In other words, when user has password field, he also has
a gear to click on to choose DE.
I hope, this helps.
Valeri
>
> mark
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++
------------------------------
Message: 8
Date: Fri, 11 Mar 2016 12:05:49 -0500
From: m.roth(a)5-cent.us
To: "CentOS mailing list" <centos(a)centos.org>
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID:
<3ddbfe316694094045c2b88aa5c3f7d9.squirrel(a)host290.hostmonster.com>
Content-Type: text/plain;charset=utf-8
Valeri Galtsev wrote:
> On Fri, March 11, 2016 10:46 am, m.roth(a)5-cent.us wrote:
>> Richard wrote:
>>>> Date: Friday, March 11, 2016 11:33:57 -0500
>>>> From: m.roth(a)5-cent.us
>>>>
>>>> So, now that I've gotten that out, the KDE display manager, on the
>>>> login screen, easily lets you choose window managers. Gnome utterly
>>>> refuses to consider such an idea.
>>>>
>>>> I've just yum groupinstall "KDE Plasma Workspaces" on one of my
>>>> user's new system... and I cannot figure out, not in googling, and
>>>> there's nothing vaguely obvious anywhere, how to change to KDE from
>>>> gnome.
>>>
>>> With gnome there is a "gear wheel" on the password entry page -- on
>>> the right below the password box, next to the "sign in" label. If I
>>> select it I can switch between gnome and mate. Does KDE show there as
>>> an option?
>>
>> Fascinating. Not in ours. It displays our issue, and in the upper left,
>> some icons that let you deal with sound, I think, connection, maybe, and
>> I forget what else.
>
> In my case the gear which when clicked of gives you drop down choices of
> Desktop Environments (DE) installed appears only after I click on
> particular user. In other words, when user has password field, he also has
> a gear to click on to choose DE.
>
> I hope, this helps.
Ah, that was it, it's not on the screen where you put in your username,
it's on the password screen. On the other hand, the easier solution was to
just create /etc/sysconfig/desktop, which did not exist, and add the two
lines to it.
Thanks, folks.
mark
------------------------------
Message: 9
Date: Fri, 11 Mar 2016 11:16:38 -0600
From: Frank Cox <theatre(a)melvilletheatre.com>
To: centos(a)centos.org
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID:
<20160311111638.bc745cc6c6aa1e38a7d26885(a)melvilletheatre.com>
Content-Type: text/plain; charset=US-ASCII
On Fri, 11 Mar 2016 10:52:12 -0600 (CST)
Valeri Galtsev wrote:
> > Fascinating. Not in ours. It displays our issue, and in the upper left,
> > some icons that let you deal with sound, I think, connection, maybe, and I
> > forget what else.
>
> In my case the gear which when clicked of gives you drop down choices of
> Desktop Environments (DE) installed appears only after I click on
> particular user. In other words, when user has password field, he also has
> a gear to click on to choose DE.
With gdm the gear only shows up if you have more than one whatever.session file in /usr/share/xsessions. gnome-classic-session and gnome-session-xsession provides this file for gnome sessions, mate-session-manager provides it for mate, and I don't know what provides it for kde.
lightdm is a lot more configurable than gdm, and it's easy to use that instead:
systemctl disable gdm
systemctl enable lightdm
systemctl isolate graphical.target
Then you can easily configure /etc/lightdm/lightdm-gtk-greeter.conf to do pretty much what you want it to do. I haven't yet figured out how to get rid of the blank photo man beside the password prompt, though.
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
------------------------------
Message: 10
Date: Fri, 11 Mar 2016 18:07:29 -0500 (EST)
From: "Scot P. Floess" <sfloess(a)nc.rr.com>
To: CentOS mailing list <centos(a)centos.org>
Subject: Re: [CentOS] CentOS 7 and display managers
Message-ID: <alpine.LRH.2.20.1603111805520.2021(a)admin.flossware.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
I think its in /usr/share/desktop
DISPLAYMANAGER=KDE
or something like that
On Fri, 11 Mar 2016, m.roth(a)5-cent.us wrote:
> <rant>
> Dear gnome developers - could you *possibly* be more anti-Unix? I mean,
> thanks *so* much for trying to turn Linux into Windows or Macs....
> </rant>
>
> So, now that I've gotten that out, the KDE display manager, on the login
> screen, easily lets you choose window managers. Gnome utterly refuses to
> consider such an idea.
>
> I've just yum groupinstall "KDE Plasma Workspaces" on one of my user's new
> system... and I cannot figure out, not in googling, and there's nothing
> vaguely obvious anywhere, how to change to KDE from gnome.
>
> Anyone got a pointer?
>
> mark, frustrated
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
Scot P. Floess RHCT (Certificate Number 605010084735240)
Chief Architect FlossWare http://sourceforge.net/projects/flosswarehttp://flossware.sourceforge.nethttps://github.com/organizations/FlossWare
------------------------------
Message: 11
Date: Fri, 11 Mar 2016 19:41:54 +0100
From: Alessandro Baggi <alessandro.baggi(a)gmail.com>
To: CentOS mailing list <centos(a)centos.org>
Subject: [CentOS] Centos and automatic update on server
Message-ID:
<CA+1R4jQzwzFomCO-sfWeFTsjXA3XNzq3cTKZYET0UY9q8Hjn7Q(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi list, I know that there are automatic update with yum-cron but never
tried.
In my experiences I never did automatic backup because if update was broken
my installation will be broken and I wait some time before apply update.
Today seems to be that automatic update are used more than before.
What do you think about automatic update? It is a good practice on a
server? What is your experiences?
Thanks in advance.
Alessandro
------------------------------
Message: 12
Date: Fri, 11 Mar 2016 10:47:26 -0800
From: Alice Wonder <alice(a)domblogger.net>
To: centos(a)centos.org
Subject: Re: [CentOS] Centos and automatic update on server
Message-ID: <56E312BE.40606(a)domblogger.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 03/11/2016 10:41 AM, Alessandro Baggi wrote:
> Hi list, I know that there are automatic update with yum-cron but never
> tried.
> In my experiences I never did automatic backup because if update was broken
> my installation will be broken and I wait some time before apply update.
> Today seems to be that automatic update are used more than before.
> What do you think about automatic update? It is a good practice on a
> server? What is your experiences?
>
> Thanks in advance.
>
> Alessandro
For me, yum-cron only downloads the updates and e-mails me to let me
know they are ready. It does not actually apply them.
To apply them, I ssh in and run the command "yum update" and they
install fast w/o me needing to wait for the download.
That lets me test everything that is critical and make sure it works
after the update.
------------------------------
Message: 13
Date: Fri, 11 Mar 2016 13:55:12 -0500
From: m.roth(a)5-cent.us
To: "CentOS mailing list" <centos(a)centos.org>
Subject: Re: [CentOS] Centos and automatic update on server
Message-ID:
<f37b628d428c3e57349bbd146e31c2f9.squirrel(a)host290.hostmonster.com>
Content-Type: text/plain;charset=utf-8
Alessandro Baggi wrote:
> Hi list, I know that there are automatic update with yum-cron but never
> tried.
> In my experiences I never did automatic backup because if update was
> broken
> my installation will be broken and I wait some time before apply update.
> Today seems to be that automatic update are used more than before.
> What do you think about automatic update? It is a good practice on a
> server? What is your experiences?
>
1. Under *NO* *CIRCUMSTANCES* would I *ever* have that running on
a production machine. That's what test boxes are for.
2. If it was my own machine at home, thanks, but I want to wake up,
or come home, to a guaranteed working system. I'll update, so
I can always undo.
------------------------------
Message: 14
Date: Fri, 11 Mar 2016 13:58:32 -0500
From: m.roth(a)5-cent.us
To: "CentOS mailing list" <centos(a)centos.org>
Subject: Re: [CentOS] Centos and automatic update on server
Message-ID:
<4a4e118ea85aafda74981ea49ac92734.squirrel(a)host290.hostmonster.com>
Content-Type: text/plain;charset=utf-8
Sorry, <enter> accidentally got hit before I finished.
m.roth(a)5-cent.us wrote:
> Alessandro Baggi wrote:
>> Hi list, I know that there are automatic update with yum-cron but never
>> tried.
>> In my experiences I never did automatic backup because if update was
>> broken
>> my installation will be broken and I wait some time before apply update.
>> Today seems to be that automatic update are used more than before.
>> What do you think about automatic update? It is a good practice on a
>> server? What is your experiences?
>
> 1. Under *NO* *CIRCUMSTANCES* would I *ever* have that running on
> a production machine. That's what test boxes are for.
> 2. If it was my own machine at home, thanks, but I want to wake up,
> or come home, to a guaranteed working system. I'll update, so
> I can always undo.
3. Systems like backup servers, etc, sure. They're not critical.
4. We don't do it on users' systems unless we're *sure* that
it won't break something.
Finally, on systems where there is a concern that something might break,
like video drivers, we put excludes in /etc/yum.conf, and disable them
under controlled conditions (i.e., one of us is sitting there doing it.)
mark
------------------------------
Message: 15
Date: Fri, 11 Mar 2016 11:22:17 -0800
From: David Nelson <david(a)davidnelson.net>
To: CentOS mailing list <centos(a)centos.org>
Subject: Re: [CentOS] Centos and automatic update on server
Message-ID: <ED7CF038-5FCC-4F1A-A956-1510729C28EC(a)davidnelson.net>
Content-Type: text/plain; charset=us-ascii
Personally I enable yum-cron on relatively simple configs without much that could break, for example a LAMP server. Especially when they are public-facing and thus have greater exposure to security threats.
But I don't as often on things that are internal-only and/or have a more complex setup such as running software I had to compile from source.
> On Mar 11, 2016, at 10:41, Alessandro Baggi <alessandro.baggi(a)gmail.com> wrote:
>
> Hi list, I know that there are automatic update with yum-cron but never
> tried.
> In my experiences I never did automatic backup because if update was broken
> my installation will be broken and I wait some time before apply update.
> Today seems to be that automatic update are used more than before.
> What do you think about automatic update? It is a good practice on a
> server? What is your experiences?
>
> Thanks in advance.
>
> Alessandro
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos
------------------------------
_______________________________________________
CentOS mailing list
CentOS(a)centos.org
https://lists.centos.org/mailman/listinfo/centos
End of CentOS Digest, Vol 134, Issue 12
***************************************
On Jun 15, 2016, at 9:02 AM, Valeri Galtsev <galtsev(a)kicp.uchicago.edu> wrote:
>
> I do see WoSign there (though I'd prefer to avoid my US located servers
> have certificates signed by authority located in China, hence located sort
> of behind "the great firewall of China" - call me superstitious).
That’s a perfectly valid concern. The last I heard, modern browsers trust 1,100 CAs! Surely some of those CAs have interests that do not align with my interests.
> I do not see neither starttls.com nor letsencrypt.org between Authorities
> certificates.
That’s because they are not top-tier CAs.
> This means (correct me if I'm wrong) that client has to
> import one of these Certification Authorities certificates
You must be unaware of certificate chaining:
https://en.wikipedia.org/wiki/Intermediate_certificate_authorities
Even top-tier CAs use certificate chaining. The proper way to run a CA is to keep your private root signing key off-line, using it only to sign some number of intermediate CA signing certs, which are the ones used to generate the certs publicly distributed by that CA.
Doing so lets a CA abandon an escaped private key by issuing a CRL for an escaped private key. The CA then just generates a new signing key and continues on with that; it doesn’t have to get its new signing key into all the TLS clients’s trusted signing key stores because the new key’s trust chain goes back to the still-private offline root key.
Without that layer of protection, if their private signing key somehow escapes, the CA is basically out of business until they convince all the major browsers to distribute their replacement public key.
> - but other clients, like laptops had to download, install and
> trus my CA certificate).
If those laptops are Windows laptops on an AD domain, there is a way to push CA public keys out to them automatically. (Don’t ask me how, I’m not a Windows admin. I’m just aware that it can be done.)
> Also: with CA signing server certificate there is a part that is
> "verification of identity" of domain or server owner. Namely, that whoever
> requested certificate indeed exists as physical entity (person,
> organization or company) accessible at some physical address etc. This is
> costly process, and as I remember, free automatically signed certificates
> were only available from Certification Authority whose CA certificated had
> no chance to be included into CA bundles shipped with browsers, systems
> etc. For that exact reason: there is "no identity verification". The last
> apparently is costly process.
I’m not exactly sure what you’re asking here. If you are simply pointing out that the free certificate providers — including Let’s Encrypt — do not do public records background checks, D&B checks, phone calls to phone numbers on your web page and DNS records, etc. to prove that you are who you say you are, that is true.
Let’s Encrypt is not in competition with EV certificates, for example:
https://en.wikipedia.org/wiki/Extended_Validation_Certificate
The term of art for what Let’s Encrypt provides is a domain validation certificate. That is, it only proves that the holder was in control of the domain name at the time the cert was generated.
> So, someone, please, set all of us straight: what is the state of the art
> today?
The answer could fill books. In a forum like this, you can only expect answers to specific questions for such broad topics.
On Thu, Dec 24, 2020 at 12:23 AM Richard <lists-centos(a)listmail.innovate.net>
wrote:
>
> > Date: Wednesday, December 23, 2020 23:24:49 +0530
> > From: Kaushal Shriyan <kaushalshriyan(a)gmail.com>
> >
> > Are there any repos to download keepass password manager for CentOS
> > Linux release 7.9.2009 (Core)? I am getting Service Unavailable
> > when I hit https://apps.fedoraproject.org/packages/keepass as per
> > https://keepass.info/download.html
> >
>
> You can get this for CentOS-7 from the EPEL repo.
>
>
Thanks Richard for the response. I have installed it on CentOS Linux
release 7.9.2009 (Core) server. Is there a GUI for it to access it from a
network similar to bitwarden (https://bitwarden.com/)? For example
http://keepass.example.com. I am going through
https://keepass.info/download.html
rpm -qil keepassx2-2.0.3-2.el7.x86_64
Name : keepassx2
Version : 2.0.3
Release : 2.el7
Architecture: x86_64
Install Date: Thu 24 Dec 2020 05:26:30 AM IST
Group : User Interface/Desktops
Size : 1892119
License : GPLv2+
Signature : RSA/SHA256, Wed 30 Nov 2016 04:33:42 AM IST, Key ID
6a2faea2352c64e5
Source RPM : keepassx2-2.0.3-2.el7.src.rpm
Build Date : Wed 30 Nov 2016 03:25:42 AM IST
Build Host : buildhw-09.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.keepassx.org/
Summary : Cross-platform password manager
Description :
KeePassX is an application for people with extremly high demands on secure
personal data management.
KeePassX saves many different information e.g. user names, passwords, urls,
attachemts and comments in one single database. For a better management
user-defined titles and icons can be specified for each single entry.
Furthermore the entries are sorted in groups, which are customizable as
well.
The integrated search function allows to search in a single group or the
complete database.
KeePassX offers a little utility for secure password generation. The
password
generator is very customizable, fast and easy to use. Especially someone who
generates passwords frequently will appreciate this feature.
The complete database is always encrypted either with AES (alias Rijndael)
or
Twofish encryption algorithm using a 256 bit key. Therefore the saved
information can be considered as quite safe. KeePassX uses a database format
that is compatible with KeePass Password Safe for MS Windows.
/usr/bin/keepassx2
/usr/lib64/keepassx2/libkeepassx-autotype-x11.so
/usr/share/applications/keepassx2.desktop
/usr/share/doc/keepassx2-2.0.3
/usr/share/doc/keepassx2-2.0.3/CHANGELOG
/usr/share/doc/keepassx2-2.0.3/README.md
/usr/share/icons/hicolor/128x128
/usr/share/icons/hicolor/128x128/apps
/usr/share/icons/hicolor/128x128/apps/keepassx.png
/usr/share/icons/hicolor/128x128/mimetypes
/usr/share/icons/hicolor/128x128/mimetypes/application-x-keepassx.png
/usr/share/icons/hicolor/16x16
Best Regards,
Kaushal