All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erich Schubert <erich@debian.org>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: Skype (for Linux)
Date: Thu, 22 Jul 2004 01:33:12 +0200	[thread overview]
Message-ID: <20040721233312.GD9916@wintermute.xmldesign.de> (raw)
In-Reply-To: <20040721170652.GC12344@lkcl.net>

> has anyone written an selinux policy for skype at all?

I for myself wouldn't touch such a proprietary closed-protocol
application. Especially not if it is hyped that way ("by the makers of
kazaa" - there i nothing to gain by using filesharing technologies
unless you want to broadcast your voice)
Being a firewall-buster also is not a good but a bad thing.
Firewalls were installed to prevent access. Applications busting through
firewalls are written by authors *fighting* against their network
admins, not working together with them.

I prefer using standard protocols such has H.323 and SIP.
The biggest problem with these protocols is that the windows clients
suck (i.e. netmeeting not supporting gatekeepers properly), but i don't
care about that.

Gruß,
Erich Schubert
-- 
     erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
   To understand recursion you first need to understand recursion.   //\
        Es gibt kein idiotensicheres Programm, weil Idioten so       V_/_
                      genial sind. -- E. Murphy


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2004-07-21 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 17:06 Skype (for Linux) Luke Kenneth Casson Leighton
2004-07-21 23:33 ` Erich Schubert [this message]
2004-07-22  8:17   ` Luke Kenneth Casson Leighton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040721233312.GD9916@wintermute.xmldesign.de \
    --to=erich@debian.org \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.