Re: connection ssh semi automatique

Le Sat, Dec 09, 2017 at 07:36:59AM +0100, Bernard Schoenacker a écrit : > > j'ai mis en place pour une personne qui utilise l'informatique cette solution > : > https://renoirboulanger.com/blog/2012/02/creer-un-tunnel-ssh-inverse-pour-pouvoir-supporter-a-distance-un-ami-utilisant-linux/ Bonjour

connection ssh semi automatique

bonjour, j'ai mis en place pour une personne qui utilise l'informatique cette solution : https://renoirboulanger.com/blog/2012/02/creer-un-tunnel-ssh-inverse-pour-pouvoir-supporter-a-distance-un-ami-utilisant-linux/ ensuite je souhaiterai mettre le mot de passe dans le script et ainsi

Re: Embarrassing security bug in systemd

Glenn writes: > Even if there's an error in the release note? Less than optimal way to > run a train. You can't retroactively fix the release notes: they are part of the already released release. All you can do is publish an errata and correct the error in the next point release. -- John Hasler

Re: Embarrassing security bug in systemd

On 12/07/2017 02:31 AM, Jonathan Dowland wrote: On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote: I'm running Jessie (with systemd running but booting with sysvinit) and trying to execute halt/poweroff/reboot/shutdown from a terminal without root privileges gives an error saying I must be

Re: Embarrassing security bug in systemd

The OP has never been seen again since the original post. Just sayin’... On Sat, Dec 9, 2017 at 9:39 Menelaos Maglis wrote: > Joe writes: > > > I think there's a case for asking which way to set it during an expert > > install or during the upgrade that

Re: Embarrassing security bug in systemd

On Fri, Dec 8, 2017 at 9:07 PM, John Hasler wrote: > Gene Heskitt writes: >> So now, no effort will ever be made to fix the man pages. Hell of a >> way to run a train. > > That doesn't follow. The release note are specific to the release and > thus obviously cannot be

Re: Filter logcheck reboot messages?

On 08/12/17 16:55, Richard Hector wrote: > Hi all, > > I'm generally a happy user of logcheck, but it makes a lot of noise at > boot time, from kernel messages and startup scripts. > > There are two problems with this: Firstly, it's a lot of work to go > through and create filters for just me -

Re: Embarrassing security bug in systemd

Joe writes: > I think there's a case for asking which way to set it during an expert > install or during the upgrade that reversed the default setting. I think it is policy not to touch locally changed configuration during upgrades. Usually packages ask what to do and/or

Re: Embarrassing security bug in systemd

On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: > On Fri, 8 Dec 2017 17:12:18 -0500 > Cindy-Sue Causey wrote: > > > > > I do remember having to give a password, but I don't remember how long > > ago now. And I have too much open right now to test drive whether mine >

Re: Embarrassing security bug in systemd

tomas writes: > Not a fan of systemd here (have outed myself this way clearly enough, > I think), but systemd is pretty well documented, for sure. Is the Debian default configuration of Systemd also well documented? -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Embarrassing security bug in systemd

On Fri, 8 Dec 2017 17:12:18 -0500 Cindy-Sue Causey wrote: > > I do remember having to give a password, but I don't remember how long > ago now. And I have too much open right now to test drive whether mine > does it or not these days.. :) > As I did the other day.

Re: Embarrassing security bug in systemd

On 12/7/17, Dave Sherohman wrote: > On Thu, Dec 07, 2017 at 11:26:45AM +1300, Ben Caradoc-Davies wrote: >> Special privileges have been granted to console users for as long as I >> can >> remember, long before systemd, because they have physical access to the >> machine.

Re: Embarrassing security bug in systemd

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 08, 2017 at 03:29:20PM -0500, Gene Heskett wrote: [...] > Which until now I have never seen its supposed advantages touted. Maybe I > don't subscribe to the right lists? Hey, to each her/his own... > rant mode on! > > Couldn't a lot

Re: Embarrassing security bug in systemd

Gene Heskitt writes: > So now, no effort will ever be made to fix the man pages. Hell of a > way to run a train. That doesn't follow. The release note are specific to the release and thus obviously cannot be fixed. The man pages can be fixed in any future release of the subject packages. File

Re: Embarrassing security bug in systemd

On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote: > On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote: > >>> > Basically, it was a completely inconsistent mess before systemd. > >>> > Now you at least have a central place where you can configure > >>> > your system

Re: Embarrassing security bug in systemd

On Friday 08 December 2017 13:09:06 Menelaos Maglis wrote: > >> > Basically, it was a completely inconsistent mess before systemd. > >> > Now you at least have a central place where you can configure > >> > your system behaviour. > > > > In the past, we had *no consistency*: inittab had one

Re: MATE Search Tool -- forcing a default search path

On Fri 08 Dec 2017 at 14:31:25 -0600, Richard Owlett wrote: > On 12/08/2017 01:46 PM, Brian wrote: > > On Fri 08 Dec 2017 at 07:25:48 -0600, Richard Owlett wrote: > > > > > For the *VAST majority* of my searches, I don't know the folder where the > > > desired file is. Either I'm researching a

Re: MATE Search Tool -- forcing a default search path

On 12/08/2017 01:46 PM, Brian wrote: On Fri 08 Dec 2017 at 07:25:48 -0600, Richard Owlett wrote: For the *VAST majority* of my searches, I don't know the folder where the desired file is. Either I'm researching a problem with an unfamiliar program or I know that very similar file names exist

Re: Embarrassing security bug in systemd

to...@tuxteam.de wrote: > Now watch all the old skoolers dashing out of their little caves and > waving their fists at something which could be read as a provocation > (I'm myself one of those, just look a bit upthread :) > It is not about old or new, but about known and unknown. Unkown exposes

Re: Embarrassing security bug in systemd

On Fri 08 Dec 2017 at 19:26:41 +, Jonathan Dowland wrote: > On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote: > > > > > Basically, it was a completely inconsistent mess before systemd. > > > > > Now you at least have a central place where you can configure your > > > > > system

Re: MATE Search Tool -- forcing a default search path

On Fri 08 Dec 2017 at 07:25:48 -0600, Richard Owlett wrote: > For the *VAST majority* of my searches, I don't know the folder where the > desired file is. Either I'm researching a problem with an unfamiliar program > or I know that very similar file names exist in several folders. > > Therefore,

Re: Embarrassing security bug in systemd

On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote: > Basically, it was a completely inconsistent mess before systemd. > Now you at least have a central place where you can configure your > system behaviour. In the past, we had *no consistency*: inittab had one thing, display

RE: OT: Troubleshooting an IP device on a LAN from another LAN--would a VPN work?

> I'll look into LogMein later today or tomorrow A free option but they irritate you with advertising is Teamviewer FREE for individual use. Just pay attention and keep it patched up. They keep finding security holes... WFIW, Richard

Re: Embarrassing security bug in systemd

Roberto C. Sánchez wrote: > That is really the problem that I have with this while issue that was > brought up.  I get that it is a "sensible" default to allow users on the > console (TTY or via DM) permission to reboot the machine.  However, when > an admin has configured the system to disallow

Re: Embarrassing security bug in systemd

>> > Basically, it was a completely inconsistent mess before systemd. >> > Now you at least have a central place where you can configure your >> > system behaviour. > In the past, we had *no consistency*: inittab had one thing, display > managers another, ACPI scripts another...if you wanted a

Re: Embarrassing security bug in systemd

>> > Basically, it was a completely inconsistent mess before systemd. >> > Now you at least have a central place where you can configure your >> > system behaviour. > In the past, we had *no consistency*: inittab had one thing, display > managers another, ACPI scripts another...if you wanted a

Re: [OT] Reinstalar navegador Fairfox en Debian Buster

->Así<-... se hace top posting 2017-12-08 8:21 GMT-04:00 Ignacio Martirén : > Gracias a todos. Me orientaron. Perdón por usar vuestro tiempo un poco mal, > veré cómo es que hago top posting. Suerte y Sl2 > > El 8 de diciembre de 2017, 7:10, Angel Vicente

Re: Embarrassing security bug in systemd

On 2017-12-08, Jonathan Dowland wrote: > On Fri, 2017-12-08 at 12:17 +0100, deloptes wrote: >> Michael Biebl wrote: >> >> > Basically, it was a completely inconsistent mess before systemd. >> > Now you at least have a central place where you can configure your >> > system

Re: Re: javascript

Sent from Shannon Price iPhone

Re: naviguer dans les répertoires en mode script

Fri, 8 Dec 2017 10:13:13 +0100 (CET) Bernard Schoenacker écrivait : > bonjour, > > > je recherche la syntaxe pour revenir à la base d'un user > en employant cd ... > > $ORIGIN=$HOME > > cd ~/Téléchargements/libfreetype6 > sudo -i dpkg -i toto.deb (exemple) > >

Re: OT: Troubleshooting an IP device on a LAN from another LAN--would a VPN work?

On Friday, December 08, 2017 11:01:52 AM Mark Fletcher wrote: > I think you have two options — a paid service like LogMeIn or OpenVPN. > > LogMeIn is the easier option if a solution is considered worth money. Your > friend would install LogMeIn on their Windows computer and you’d need a >

Re: OT: Troubleshooting an IP device on a LAN from another LAN--would a VPN work?

On Fri, Dec 8, 2017 at 23:47 wrote: > This may become on-topic if I need to learn how to set up a VPN, and > especially if I have to have a non-computer savvy person at the other end > (using a Windows computer) do something to set up the VPN on their end. > > I have a friend

Re: Embarrassing security bug in systemd

On Fri, 2017-12-08 at 12:17 +0100, deloptes wrote: > Michael Biebl wrote: > > > Basically, it was a completely inconsistent mess before systemd. > > Now you at least have a central place where you can configure your > > system behaviour. > > This is your opinion - if you can not understand the

Re: kernle 4.13 and headphones not work

On 12/08, behrad eslami wrote: Hi I have Thinkpad x260 with debian stretch. I switch to kernel 4.13 in backport , because hibernate work well. But headphones not work.  # lspci -k...00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise Point-LP HD

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

On 08.12.2017 17:35, Alexandre Rossi wrote: > (please CC me as I am not subscribed to the list) > >> A screenshot would be helpful. Does these artifacts appear every single time >> or sporadically? > The artifact appear at the same place every single time and seem to > follow (in videos) a single

OT: Troubleshooting an IP device on a LAN from another LAN--would a VPN work?

This may become on-topic if I need to learn how to set up a VPN, and especially if I have to have a non-computer savvy person at the other end (using a Windows computer) do something to set up the VPN on their end. I have a friend about 100 miles away with an IP device (specifically, an Obi

MATE Search Tool -- forcing a default search path

For the *VAST majority* of my searches, I don't know the folder where the desired file is. Either I'm researching a problem with an unfamiliar program or I know that very similar file names exist in several folders. Therefore, I wish to set "Look in folder: to "File System". How? TIA

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

(please CC me as I am not subscribed to the list) > A screenshot would be helpful. Does these artifacts appear every single time > or sporadically? The artifact appear at the same place every single time and seem to follow (in videos) a single set of colors (dark brownish areas). You can look at

Re: Embarrassing security bug in systemd

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 08, 2017 at 12:17:16PM +0100, deloptes wrote: > Michael Biebl wrote: > > > Basically, it was a completely inconsistent mess before systemd. [...] > This is your opinion - if you can not understand the "mess" it is a mess. > For most

Re: Embarrassing security bug in systemd

On Fri, Dec 08, 2017 at 10:17:36AM +0100, Menelaos Maglis wrote: > > It is an improvement to have a consistent (central) way to configure > this behavior. > > It is probably a "good thing" to allow users with physical access to > reboot/shutdown a desktop/laptop system. > > It is probably not a

Re: [OT] Reinstalar navegador Fairfox en Debian Buster

Gracias a todos. Me orientaron. Perdón por usar vuestro tiempo un poco mal, veré cómo es que hago top posting. Suerte y Sl2 El 8 de diciembre de 2017, 7:10, Angel Vicente escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > El Thu, 7 Dec 2017 17:44:55 -0300 >

Re: Embarrassing security bug in systemd

Michael Biebl wrote: > Basically, it was a completely inconsistent mess before systemd. > Now you at least have a central place where you can configure your > system behaviour. This is your opinion - if you can not understand the "mess" it is a mess. For most of us who dislike systemd your same

Re: naviguer dans les répertoires en mode script

jérémy prego wrote on Fri, Dec 08, 2017 at 10:17:44AM +0100 > bonjour, > cd ~ ou cd # fonctionne ici Et si on veut revenir au rép. précédemment quitter, quel qu'il soit donc, cd - dom > > jerem > Le 08/12/2017 à 10:13, Bernard Schoenacker a écrit : > >bonjour, > > > > > >je recherche la

Re: [OT] Reinstalar navegador Fairfox en Debian Buster

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 El Thu, 7 Dec 2017 17:44:55 -0300 Felix Perez escribió: > 2017-12-07 10:21 GMT-03:00 Ignacio Martirén : > > Hola lista. Soy usuario inexperto. El navegador Fairfox se ha > > puesto lento y no sé

Re: naviguer dans les répertoires en mode script

On Fri, Dec 08, 2017 at 10:17:44AM +0100, jérémy prego wrote: > bonjour, > cd ~ ou cd # fonctionne ici > > jerem > Le 08/12/2017 à 10:13, Bernard Schoenacker a écrit : > > bonjour, > > > > > > je recherche la syntaxe pour revenir à la base d'un user > > en employant cd ... > > > >

Re: Embarrassing security bug in systemd

>>> I wonder how can such a severe bug make it into a Debian stable >>> distribution? And is this just an insane default setting on Debian's >>> side or is it yet another instance of brain-dead systemd behavior? >> >> Maybe I am just a brain-dead loony, but personally I prefer to be able to >>

Re: naviguer dans les répertoires en mode script

Bonjour Bernard, peut-être que cd sans argument répond à ta question ? Vincent. Le vendredi 08 décembre 2017 à 10:13 +0100, Bernard Schoenacker a écrit : > bonjour, > > > je recherche la syntaxe pour revenir à la base d'un user > en employant cd ... > > $ORIGIN=$HOME > > cd

Re: naviguer dans les répertoires en mode script

bonjour, cd ~ ou cd # fonctionne ici jerem Le 08/12/2017 à 10:13, Bernard Schoenacker a écrit : bonjour, je recherche la syntaxe pour revenir à la base d'un user en employant cd ... $ORIGIN=$HOME cd ~/Téléchargements/libfreetype6 sudo -i dpkg -i toto.deb (exemple) cd $ORIGIN slt bernard

Re: naviguer dans les répertoires en mode script

Bonjour Bernard, On 12/08/2017 10:13 AM, Bernard Schoenacker wrote: > je recherche la syntaxe pour revenir à la base d'un user > en employant cd ... > Essaye tout simplement : cd sans arguments. À plus, -- Étienne Mollier

naviguer dans les répertoires en mode script

bonjour, je recherche la syntaxe pour revenir à la base d'un user en employant cd ... $ORIGIN=$HOME cd ~/Téléchargements/libfreetype6 sudo -i dpkg -i toto.deb (exemple) cd $ORIGIN slt bernard

Re: Embarrassing security bug in systemd

On Thu, Dec 07, 2017 at 09:37:25AM -0500, Roberto C. Sánchez wrote: > On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote: > > > > I no longer have any non-systemd machines handy to verify this on, but > > my memory is that I have *always* been able to use halt/poweroff/reboot > >

Re: Embarrassing security bug in systemd

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 07, 2017 at 08:03:47PM +0100, Michael Biebl wrote: [...] > Basically, it was a completely inconsistent mess before systemd. > Now you at least have a central place where you can configure your > system behaviour. Hey, I'm "before