Hi Chris,
We've started to use an HTTPS link on port 4201. The usual 4200 port is
automatically redirected as well.
The self-signed certificate warning is a temporary evil to protect a new
token requested for access control.
We are working on additional security parts for snapweb, like SSO/macaro
El 24/10/16 a las 11:54, Didier Roche escribió:
Also, I don't see any reason why we are preventing underscores in app
name (nothing in yaml prevents key to be underscores). I don't link such
command name in general, but I don't see any good reasons for this.
Gustavo, is that deliberate?
Jami
On Tue, 2016-10-25 at 10:24 +0200, David Barth wrote:
> Hi Chris,
>
> We've started to use an HTTPS link on port 4201. The usual 4200 port
> is automatically redirected as well.
> The self-signed certificate warning is a temporary evil to protect a
> new token requested for access control.
>
> We
On Mon, 2016-10-24 at 16:54 +0200, Didier Roche wrote:
> Le 24/10/2016 à 16:13, Gordon Ball a écrit :
>
> >
> > Hello
> Hey Gordon,
>
> >
> > I have been trying to create a snap package for the `cufflinks` [1]
> > biofinformatics tools. These are packaged for debian/ubuntu, but the
> > package
On Tue, 2016-10-25 at 08:24 +0200, Didier Roche wrote:
> Le 24/10/2016 à 21:52, Dan Kegel a écrit :
> >
> > I'm trying to snap a largish package; works fine in devmode,
> > but as the app likes to use unix sockets and fifos, it fails in
> > confined mode with
> >
> > $ sudo /snap/bin/snappy-debug
Hi Gordon,
On Mon, Oct 24, 2016 at 12:13 PM, Gordon Ball wrote:
>
> * The package contains multiple binaries, and the links in /snap/bin
> are named, eg `cufflinks.cuffdiff`, which makes them incompatible with
> existing scripts.
As you can imagine the problem here is namespacing. Unlike in tr
On Tue, Oct 25, 2016 at 6:33 AM, Jamie Strandboge wrote:
> Instead of using an abstract or anonymous socket, use a named socket and put
> in
> SNAP_DATA
Sounds very doable, I'll try.
> It is planned to allow snaps via
> seccomp arg filtering policy the ability to create S_IFIFO and S_IFREG file
Hi all!
I've a weird issue in my snap which needs some debugging. I understand
that
snap run --shell
is the command I want to use in order to start a shell with the same
confinement and environment of my snap (which BTW is in --devmode), and
so far so good. But now I want to use "strace" on
On Tue, 2016-10-25 at 07:53 -0700, Dan Kegel wrote:
> On Tue, Oct 25, 2016 at 6:33 AM, Jamie Strandboge wrote:
> >
> > It is planned to allow snaps via
> > seccomp arg filtering policy the ability to create S_IFIFO and S_IFREG files
> > (ie, pipes and regular files, but not character and block de
El 25/10/16 a las 12:05, Alberto Mardegan escribió:
Hi all!
I've a weird issue in my snap which needs some debugging. I understand
that
snap run --shell
is the command I want to use in order to start a shell with the same
confinement and environment of my snap (which BTW is in --devmode)
On Mon, Oct 24, 2016 at 8:54 AM, Didier Roche wrote:
>
> Also, I don't see any reason why we are preventing underscores in app
> name (nothing in yaml prevents key to be underscores). I don't link such
> command name in general, but I don't see any good reasons for this.
> Gustavo, is that deliber
On Tue, Oct 25, 2016 at 2:37 PM, Sergio Schvezov <
sergio.schve...@canonical.com> wrote:
> This is how I do it on the fly (there was a session at the sprint for this
> to be easier)...
>
> ```
> snapcraft prime
> snap try prime --devmode
> cp /usr/bin/strace prime
> snap shell --shell
>
This is
On 25/10/2016 21:42, Gustavo Niemeyer wrote:
> On Tue, Oct 25, 2016 at 2:37 PM, Sergio Schvezov
> mailto:sergio.schve...@canonical.com>>
> wrote:
>
> This is how I do it on the fly (there was a session at the sprint
> for this to be easier)...
[...]
Thanks guys! :-)
Ciao,
Alberto
--
13 matches
Mail list logo
