Re: [vox-tech] vim question

[Rick Moen]

Quoting Mark K. Kim ([EMAIL PROTECTED]):

> So what happens if you type:
> 
>xhost +username
> 
> and someone creates a machine named "username"?  Can anyone from that
> machine access your X?

Damned if I know, partner.

You'll note that I very cautiously said "the xhost manpage says...", and
pointed out that I'd deliberately eschewed usage of xhost entirely up
until now, as a hopeless security risk.

But you can answer your question for yourself using one or both of the
following two time-tested methods:

1.  Experiment.
2.  Read the Fine Source Code.

-- 
Cheers, Bah humbug.  Shop late.
Rick Moen   Happy unChristmas. 
[EMAIL PROTECTED]
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] vim question

[Troy Arnold]

On Wed, Nov 13, 2002 at 09:11:33AM -0800, Henry House wrote:
> On Tue, Nov 12, 2002 at 04:59:11PM -0800, Peter Jay Salzman wrote:
> > damn, matt.  you're good!   :)
> > 
> > i thought rusty used debian though.  this doesn't seem like something
> > debian would do...
> 
> This can be due to vim being built with support for changing and restoring
> the title of the terminal window in which it runs. This is true by default of
> even the non-GTK version in Debian.
> 
> If the error message under su-shell is bothersome, simply unset the DISPLAY
> variable. Vim will no longer try to mess with the X display.

Also, vim -X #Do not connect to X server

I have ssh forwarding my X connections, and that comes in handy, so I
don't want to unset $DISPLAY.  But having vim  contact my Xserver over
slow-ass dialup every time i reply to an e-mail is laggy and annoying,
hence -X.

I'm a new vim convert and found the vimtips at
 to be very helpful as far
as learning how to do stuff as well as just getting a better idea of all
the cool stuff vim can do.

There's some quick perl to pick out a random tip here:
http://zenux.net/linux/vimtip.pl

-ta

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Sound Problem

[Ryan Castellucci]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 13 November 2002 02:20 pm, Shawn P. Neugebauer wrote:
> Rod touched on what is likely the root cause of the problem:  the artsd
> sound server.  I don't know what KDE was thinking.  Well, I know they
> were trying to "standardize" and "centralize" but the problem is nothing
> "standard" works well with artsd.

No, they were trying to allow more then one app to use the sound device at a 
time. Gnome has a simmilar thing, caled esd.
- -- 
PGP/GPG Fingerprint: 3B30 C6BE B1C6 9526 7A90  34E7 11DF 44F3 7217 7BC7
On pgp.mit.edu, import with `gpg --keyserver pgp.mit.edu --recv-key 72177BC7`
Also available at http://www.cal.net/~ryan/ryan_at_mother_dot_com.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE90uIMEd9E83IXe8cRAsZHAJ9MVyPAdYcn7fWirJ4KyzQVg5r1OwCghwjV
PwVZHiu43sMqTyEzEXj7fEc=
=RUIj
-END PGP SIGNATURE-
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Sound Problem

[Shawn P. Neugebauer]

Rod touched on what is likely the root cause of the problem:  the artsd
sound server.  I don't know what KDE was thinking.  Well, I know they
were trying to "standardize" and "centralize" but the problem is nothing
"standard" works well with artsd.

I think there are essentially two choices, without doing lots and lots of
work:  run the sound server and accept that RealPlayer won't work,
or do not run the sound server and use RealPlayer but accept that
some of the KDE stuff may not work well.  There's an option in the control
panel to specify whether artsd runs at startup.  I do not use it, and
I can use sound in apps just fine, although I'm certainly not taking care
of all the mixing features and what not of artsd.

I don't think RealPlayer screwed up the sound in your system.  You
probably tried to use RealPlayer, the sound server doesn't cooperate
well, it crashes (but only after occupying lots of CPU time), and that
leaves sound support for other applications iffy.

The artswrapper that is referred to is designed to run as a wrapper
for another application, e.g., invoked using "artswrapper realplayer"
(note: this is not the precise syntax).  It doesn't do anything by
itself.

Make sure realplayer is not being started automatically at login.

Does anyone know what the situation is in, say, KDE 3.1?

Good luck.

shawn.


If you google for artsd user guide you'll find some FAQ info that
discusses much of this.
On Wednesday 13 November 2002 11:35 am, Rod Roark wrote:
> Hi Bob,
>
> You might try going into the KDE Control Center, select
> Sound and Sound Server, and turning off the sound server.
> Or if it's off, turn it on.  Frankly the artsd server is
> kind of a mystery to me, very poorly documented.
>
> It could also be that some lock file in /tmp was left when
> Konqueror crashed, so deleting stuff there might fix it.
>
> -- Rod
>
> On Wednesday 13 November 2002 10:58 am, Robert G. Scofield wrote:
> > I just installed RealPlayer8 and it's screwed up the sound in my system.
> > The one thing I can still do is play the CD player okay and listen to
> > music. However, there is now now sound when I start or leave KDE.  Also
> > RealPlayer did not do it's startup sound.  I have deleted RealPlayer. 
> > This problem happened after a crash using Kongueror when I was trying to
> > listen to a radio station.  I also get some static now when logging onto
> > Linux, and clicking on icons in KDE.  I get these two error messages:
> >
> > "Sound server warning message:
> > Can't set real-time scheduling priority.
> > You need to run artswrapper as root or
> > setuid root. This means that you will
> > likely not be able to produce acceptable
> > sound (i.e. without clicks and breaks)."
> >
> >
> > "Sound server informational message:
> > sound server suspended"
> >
> > When I log on as root and type "artswrapper" I get this message:
> >
> > ">> running as realtime process now (priority 50)
> > /tmp/mcop-bob is not owned by user"
> >
> > If I type "artswrapper" when I am not root I get this message:
> >
> > "Error while initializing the sound driver:
> > device /dev/dsp can't be opened (Resource temporarily unavailable)"
> >
> > Any ideas as to fix this?
> >
> > Thank you.
> >
> > Bob
>
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Sound Problem

[Rod Roark]

Hi Bob,

You might try going into the KDE Control Center, select 
Sound and Sound Server, and turning off the sound server.
Or if it's off, turn it on.  Frankly the artsd server is 
kind of a mystery to me, very poorly documented.

It could also be that some lock file in /tmp was left when 
Konqueror crashed, so deleting stuff there might fix it.

-- Rod

On Wednesday 13 November 2002 10:58 am, Robert G. Scofield wrote:
> I just installed RealPlayer8 and it's screwed up the sound in my system. 
> The one thing I can still do is play the CD player okay and listen to
> music. However, there is now now sound when I start or leave KDE.  Also
> RealPlayer did not do it's startup sound.  I have deleted RealPlayer.  This
> problem happened after a crash using Kongueror when I was trying to listen
> to a radio station.  I also get some static now when logging onto Linux,
> and clicking on icons in KDE.  I get these two error messages:
>
> "Sound server warning message:
> Can't set real-time scheduling priority.
> You need to run artswrapper as root or
> setuid root. This means that you will
> likely not be able to produce acceptable
> sound (i.e. without clicks and breaks)."
>
>
> "Sound server informational message:
> sound server suspended"
>
> When I log on as root and type "artswrapper" I get this message:
>
> ">> running as realtime process now (priority 50)
> /tmp/mcop-bob is not owned by user"
>
> If I type "artswrapper" when I am not root I get this message:
>
> "Error while initializing the sound driver:
> device /dev/dsp can't be opened (Resource temporarily unavailable)"
>
> Any ideas as to fix this?
>
> Thank you.
>
> Bob

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] Sound Problem

[Robert G. Scofield]

I just installed RealPlayer8 and it's screwed up the sound in my system.  The 
one thing I can still do is play the CD player okay and listen to music.  
However, there is now now sound when I start or leave KDE.  Also RealPlayer 
did not do it's startup sound.  I have deleted RealPlayer.  This problem 
happened after a crash using Kongueror when I was trying to listen to a radio 
station.  I also get some static now when logging onto Linux, and clicking on 
icons in KDE.  I get these two error messages:

"Sound server warning message:
Can't set real-time scheduling priority.
You need to run artswrapper as root or
setuid root. This means that you will
likely not be able to produce acceptable
sound (i.e. without clicks and breaks)."


"Sound server informational message:
sound server suspended"

When I log on as root and type "artswrapper" I get this message:

">> running as realtime process now (priority 50)
/tmp/mcop-bob is not owned by user"

If I type "artswrapper" when I am not root I get this message:

"Error while initializing the sound driver:
device /dev/dsp can't be opened (Resource temporarily unavailable)"

Any ideas as to fix this?

Thank you.

Bob





___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] vim question

[Henry House]

On Tue, Nov 12, 2002 at 04:59:11PM -0800, Peter Jay Salzman wrote:
> damn, matt.  you're good!   :)
> 
> i thought rusty used debian though.  this doesn't seem like something
> debian would do...

This can be due to vim being built with support for changing and restoring
the title of the terminal window in which it runs. This is true by default of
even the non-GTK version in Debian.

If the error message under su-shell is bothersome, simply unset the DISPLAY
variable. Vim will no longer try to mess with the X display.

-- 
Henry House
The attached file is a digital signature. See 
for information.  My OpenPGP key: .



msg03628/pgp0.pgp
Description: PGP signature

Re: [vox-tech] vim question

[Mark K. Kim]

So what happens if you type:

   xhost +username

and someone creates a machine named "username"?  Can anyone from that
machine access your X?

Let's assume that's not a problem because X first checks /etc/passwd,
and if there's a user named "username", it gives that user the permission
but not to any machine.  What if you want to give all the users on
"hostname" access to your X, like this:

   xhost +hostname

then the root on the system decides to create a user named "hostname"?
Then now you can't connect from "hostname" and you've inadvertantly
given the user "hostname" a complete control over your X.

How does xhost work to get around these problems?

-Mark


On Tue, 12 Nov 2002, Rick Moen wrote:

> Quoting Michael Wenk ([EMAIL PROTECTED]):
>
> > Hmm, I was just about to say... :-)
> >
> > Yes the others will work, xhost tho, IMO is the fastest and requires the
> > least effort.  And I agree that xhost + is not a good way to go, in fact,
> > you may want to go a bit further and do an xhost +root@localhost
> >
> > I forget if xhost assumes wildcards, but why take chances, if you're
> > explicit, then you lessen the risk.
>
> For what it's worth, the xhost manpage says that the name following the
> "+" may be either a hostname or a username.
>
> Prior to reading your post attentively _and_ reading the manpage, I had
> been mislead by a recent thread on debian-security where one of the
> regulars swore up and down that (quoting) "xhost is _host_ based access
> control, so of course xhost +username doesn't work!"
>
> You can see posts from that thread at
> http://linuxmafia.com/~rick/linux-info/root-with-x11 , where your post
> is now immortalised at the end.
>
> And here, all these years, I've been eschewing xhost as a hopeless
> security risk.  Well, I learned something today.
>
> --
> Cheers,  Right to keep and bear
> Rick Moen  Haiku shall not be abridged
> [EMAIL PROTECTED]   Or denied.  So there.
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
>

-- 
Mark K. Kim
http://www.cbreak.org/
PGP key available upon request.


___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech