*Qubes Is YOU a system “*out *the *box” smart to use, recommend to read
his documentation little by little by what can contribute to the hour to use
the system.
In my experience with the system would stand out:
From my scarce technical knowledge, this system covers appearances of
security that the conventional monolithic operating systems does not reach
them, that is to say, the purpose of *Qubes is YOU do more difficult this
hypothetical *game *over to the that a monolithic system finds constantly
exposed.
The metaphor perhaps could draw as if a system treated of an army, with what
sail, with the host, with the king? No, in *Qubes sail with a first line of
army (*AppVM) with which no only sail, but you also execute all your
programs, if this line falls or is engaged, don 't happen nothing, clone
another, created another.
Backwards of this first line where execute our programs, finds the second
line of our army (*Templates), these only serve to install, have denied the
access (by defect) to connect further of your repositories, can update them
with a pair of clicks and install also graphic or by commandos. But if it is
line fell or went committed, neither there would be *game *over, install or
clone others, reproduce the same without *despeinarte neither be
“defeated”.
And from further back in the army, finds the old *dom0, offline to increase
his security, he is the host, yes, that with which handled us in monolithic
systems, if he falls or arrives to fall, all fall, here yes would be *game
*over, therefore, the logic means to be possible to touch the minimum to
*dom0, update and little more.
If to level of system to one liked him this logic, the controllers of the
*USBs (*HDD of external storage, *pendrives, even the keyboard if it is *usb)
also would not have to touch the host, because they could engage to the
system, therefore, in *Qubes a *AppVM (*sys-USB) is the one who commissions
of all the controllers *USBs , with access to the host? No, it could result
dangerous, with access from a *AppVM, this loads (by defect) to the start,
and only allow him changes to level of user
In the technical appearance recommend the reading of for example this article
with regard to the concept of isolation in monolithic systems
https://theinvisiblethings.blogspot.nl/2011/04/linux-security-circus-on-gui-isolation.html
Concept of flexibility by what this logic means, *drivers of printers no
reliable, what would do in a monolithic? Perhaps litter the system, possibly
not knowing if the system finds engaged through some simple *drivers of
printer, in *Qubes You, can devote a *Template for this function and later,
*disconnect the *AppVM that is serving you to print, scan increasing his
security.. What a *driver or software no reliable that can result you useful
does not engage your system.
Also flexibility by all what can you occur from this logic, all what mean to
install programs to level of user or to level of system can mean a lot of
ease to find a better form to order, separate, isolate some uses of others,
administer what results you more reliable or less reliable without having to
engage your system.
In the question that tackle to the games, could install small games,
emulators and all this world, and for big games, from *aventurarse to happen
a second graphic card *virtualizando or easier devote a *HDD with an
exclusive monolithic system for this.
In the computing, can exist today a *chaos in the concept of “comfort”
and do reference to him because it is a subject. All comfort or all ease
never travels alone, always accompanies of his corresponding difficulties,
of his corresponding call “small letter” or “*hit in the eggs”, ease
*feeds to difficulty and difficulty *feeds to ease, would not work the one
without the another. Therefore, when it treats of ease and of comfort of
course that also it is treating of difficulty and of discomfort, but of what
really they treat for us, is of the possibility to recognise an and again
the trace of our results, the advantages or disadvantages that arrive and can
find between our eases and our difficulties
Conclusions not to lengthen me more:
it Is true that the computer security so much and in what ours information
could result committed, is a subject that can extend to a lot of more areas,
as for example, the *fingerprint that can leave one when sailing, the
information that leave in computers(servers) that are not ours neither have
any control on them, the *Bios of the majority of the *Pcs (*x86), or who is
serving us Internet?, and all the *chaos that can surround to connect
machines ones with other (Internet)... The problems of security probably are
part of what is and expects us, increasing. It is possible, although I do
not have neither idea, that to measure that the hardware go being more and
more powerful, was a goodbye definite to reduce our system to a monolithic
system, by questions of basic security as it corresponded *previously to the
classical fashionable past “install you a *antivirus”.
The objectivity is born and nourishes of the subjectivity, the world do it
smaller when we shut us in objectivities and refuse the subjectivity.
Therefore, perhaps it was not a prank this that the greater security find in
the ignorance and the greater freedom in the peaceful and the sober. Perhaps
it do not remain him another to the computer security that tackle to this
ignorance, that arrive to find this in the enciphered or in the isolation of
parts of our system.
Sry for this English, It is a translate by apertium
