What are the dangers of using snap's classic confinement?
While following a video tutorial on Linux bash scripting, the teacher uses atom for editor.
When I did I tried to install atom :
*sudo snap install atom*
I got the message:
error: This revision of snap "atom" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which may put your system at risk.
If you understand and want to proceed repeat the command including --classic.
What would you do/suggest?
ubuntu snap atom
edited Jan 8 at 0:33
Sparhawk
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
add a comment |
While following a video tutorial on Linux bash scripting, the teacher uses atom for editor.
When I did I tried to install atom :
*sudo snap install atom*
I got the message:
error: This revision of snap "atom" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which may put your system at risk.
If you understand and want to proceed repeat the command including --classic.
What would you do/suggest?
ubuntu snap atom
edited Jan 8 at 0:33
Sparhawk
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52
add a comment |
While following a video tutorial on Linux bash scripting, the teacher uses atom for editor.
When I did I tried to install atom :
*sudo snap install atom*
I got the message:
error: This revision of snap "atom" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which may put your system at risk.
If you understand and want to proceed repeat the command including --classic.
What would you do/suggest?
ubuntu snap atom
edited Jan 8 at 0:33
Sparhawk
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
While following a video tutorial on Linux bash scripting, the teacher uses atom for editor.
When I did I tried to install atom :
*sudo snap install atom*
I got the message:
error: This revision of snap "atom" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which may put your system at risk.
If you understand and want to proceed repeat the command including --classic.
What would you do/suggest?
ubuntu snap atom
ubuntu snap atom
edited Jan 8 at 0:33
Sparhawk
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
edited Jan 8 at 0:33
Sparhawk
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
edited Jan 8 at 0:33
Sparhawk
9,41263992
edited Jan 8 at 0:33
Sparhawk
9,41263992
edited Jan 8 at 0:33
Sparhawk
9,41263992
9,41263992
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
asked Jan 7 at 16:33
Philippe MoisanPhilippe Moisan
133
133
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52
add a comment |
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52
add a comment |
1 Answer
1
active
oldest
votes
This is answered well in snapcraft's official documentation.
In the interest of time, here is the pertinent portion:
Classic confinement is effectively un-confining the applications inside a snap. Applications which use classic confinement have the
same full system access as traditionally packaged applications.
Classic confinement is intended as a stop-gap measure to enable
developers to publish applications which need more access than the
current set of interfaces enable. Over time, as more interfaces are
developed, snap publishers can migrate away from classic confinement
to strict.
Classically confined snaps must be reviewed by the snap store
reviewers team before they can be published in the stable channel.
Snaps which use classic confinement may be rejected if they don’t meet
the requirements.
Users should not attempt to override a strictly confined snap to make
it ‘classic’ as this undoes the confinement and interfaces defined by
the developer. In addition applications published as strict snaps may
misbehave when installed with the ‘–classic’ switch.
As for a recommendation, you'll need to weigh the risks in your own mind. Consider the publisher of the software, their reputation/recognition and the fact that classic confinement snaps are reviewed before being published. Classic confinement is not all that different than having done a traditional apt install in terms of the access it allows to the program.
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493033%2fwhat-are-the-dangers-of-using-snaps-classic-confinement%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is answered well in snapcraft's official documentation.
In the interest of time, here is the pertinent portion:
Classic confinement is effectively un-confining the applications inside a snap. Applications which use classic confinement have the
same full system access as traditionally packaged applications.
Classic confinement is intended as a stop-gap measure to enable
developers to publish applications which need more access than the
current set of interfaces enable. Over time, as more interfaces are
developed, snap publishers can migrate away from classic confinement
to strict.
Classically confined snaps must be reviewed by the snap store
reviewers team before they can be published in the stable channel.
Snaps which use classic confinement may be rejected if they don’t meet
the requirements.
Users should not attempt to override a strictly confined snap to make
it ‘classic’ as this undoes the confinement and interfaces defined by
the developer. In addition applications published as strict snaps may
misbehave when installed with the ‘–classic’ switch.
As for a recommendation, you'll need to weigh the risks in your own mind. Consider the publisher of the software, their reputation/recognition and the fact that classic confinement snaps are reviewed before being published. Classic confinement is not all that different than having done a traditional apt install in terms of the access it allows to the program.
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
add a comment |
This is answered well in snapcraft's official documentation.
In the interest of time, here is the pertinent portion:
Classic confinement is effectively un-confining the applications inside a snap. Applications which use classic confinement have the
same full system access as traditionally packaged applications.
Classic confinement is intended as a stop-gap measure to enable
developers to publish applications which need more access than the
current set of interfaces enable. Over time, as more interfaces are
developed, snap publishers can migrate away from classic confinement
to strict.
Classically confined snaps must be reviewed by the snap store
reviewers team before they can be published in the stable channel.
Snaps which use classic confinement may be rejected if they don’t meet
the requirements.
Users should not attempt to override a strictly confined snap to make
it ‘classic’ as this undoes the confinement and interfaces defined by
the developer. In addition applications published as strict snaps may
misbehave when installed with the ‘–classic’ switch.
As for a recommendation, you'll need to weigh the risks in your own mind. Consider the publisher of the software, their reputation/recognition and the fact that classic confinement snaps are reviewed before being published. Classic confinement is not all that different than having done a traditional apt install in terms of the access it allows to the program.
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
add a comment |
This is answered well in snapcraft's official documentation.
In the interest of time, here is the pertinent portion:
Classic confinement is effectively un-confining the applications inside a snap. Applications which use classic confinement have the
same full system access as traditionally packaged applications.
Classic confinement is intended as a stop-gap measure to enable
developers to publish applications which need more access than the
current set of interfaces enable. Over time, as more interfaces are
developed, snap publishers can migrate away from classic confinement
to strict.
Classically confined snaps must be reviewed by the snap store
reviewers team before they can be published in the stable channel.
Snaps which use classic confinement may be rejected if they don’t meet
the requirements.
Users should not attempt to override a strictly confined snap to make
it ‘classic’ as this undoes the confinement and interfaces defined by
the developer. In addition applications published as strict snaps may
misbehave when installed with the ‘–classic’ switch.
As for a recommendation, you'll need to weigh the risks in your own mind. Consider the publisher of the software, their reputation/recognition and the fact that classic confinement snaps are reviewed before being published. Classic confinement is not all that different than having done a traditional apt install in terms of the access it allows to the program.
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
This is answered well in snapcraft's official documentation.
In the interest of time, here is the pertinent portion:
Classic confinement is effectively un-confining the applications inside a snap. Applications which use classic confinement have the
same full system access as traditionally packaged applications.
Classic confinement is intended as a stop-gap measure to enable
developers to publish applications which need more access than the
current set of interfaces enable. Over time, as more interfaces are
developed, snap publishers can migrate away from classic confinement
to strict.
Classically confined snaps must be reviewed by the snap store
reviewers team before they can be published in the stable channel.
Snaps which use classic confinement may be rejected if they don’t meet
the requirements.
Users should not attempt to override a strictly confined snap to make
it ‘classic’ as this undoes the confinement and interfaces defined by
the developer. In addition applications published as strict snaps may
misbehave when installed with the ‘–classic’ switch.
As for a recommendation, you'll need to weigh the risks in your own mind. Consider the publisher of the software, their reputation/recognition and the fact that classic confinement snaps are reviewed before being published. Classic confinement is not all that different than having done a traditional apt install in terms of the access it allows to the program.
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
answered Jan 8 at 0:56
Jeff H.Jeff H.
32629
32629
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493033%2fwhat-are-the-dangers-of-using-snaps-classic-confinement%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Thanks for clarifying my question, Sparhawk. :)
– Philippe Moisan
Jan 8 at 0:52