Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #185652 > unrolled thread

Debian v9 it's a stretch

Back to article view | Back to linux.debian.user

Contents

  Debian v9 it's a stretch tony mollica <tjm3@threedogs.net> - 2017-08-21 18:10 +0200
    Re: Debian v9 it's a stretch Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-21 18:20 +0200
    Re: Debian v9 it's a stretch deloptes <deloptes@gmail.com> - 2017-08-21 18:30 +0200
      Re: Debian v9 it's a stretch Rob van der Putten <rob@sput.nl> - 2017-08-22 21:20 +0200
        Re: Debian v9 it's a stretch Rob van der Putten <rob@sput.nl> - 2017-08-24 14:50 +0200
          Re: Debian v9 it's a stretch Dan Ritter <dsr@randomstring.org> - 2017-08-24 15:50 +0200
            Re: Debian v9 it's a stretch Rob van der Putten <rob@sput.nl> - 2017-08-24 15:50 +0200
              Re: Debian v9 it's a stretch Brian <ad44@cityscape.co.uk> - 2017-08-24 21:00 +0200
                Re: Debian v9 it's a stretch Dejan Jocic <jodejka@gmail.com> - 2017-08-24 21:20 +0200
                  Re: Debian v9 it's a stretch Brian <ad44@cityscape.co.uk> - 2017-08-24 21:30 +0200
                    Re: Debian v9 it's a stretch Dejan Jocic <jodejka@gmail.com> - 2017-08-24 21:40 +0200
                      Re: Debian v9 it's a stretch Brian <ad44@cityscape.co.uk> - 2017-08-24 22:00 +0200
                        Re: Debian v9 it's a stretch Dejan Jocic <jodejka@gmail.com> - 2017-08-24 22:00 +0200
                          Re: Debian v9 it's a stretch Brian <ad44@cityscape.co.uk> - 2017-08-24 23:20 +0200
                            Re: Debian v9 it's a stretch Dejan Jocic <jodejka@gmail.com> - 2017-08-24 23:50 +0200
                              Re: Debian v9 it's a stretch Curt <curty@free.fr> - 2017-08-25 11:00 +0200
    Re: Debian v9 it's a stretch Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-21 18:30 +0200

#185652 — Debian v9 it's a stretch

I don't usually complain about free stuff but, for me, stretch has 
become a distant back-runner to previous releases.  Jessie was fast and 
everything worked.  Stretch has become a day to day challenge for even 
minor issues.  Going back or changing dists.

I'd like to know if others have the same issue or is it my particular 
installation, which was a new, clean install to a new disk.

tjm

[toc] | [next] | [standalone]

#185653

On Mon, Aug 21, 2017 at 09:08:55AM -0700, tony mollica wrote:
> I'd like to know if others have the same issue or is it my particular
> installation, which was a new, clean install to a new disk.

What issues?  You didn't say what's wrong.

For many desktop/laptop systems, the changes in the video drivers will
cause issues, until you add the appropriate non-free firmware.  This
applies even to systems which did not require the firmware under
jessie, because jessie used different drivers.

[toc] | [prev] | [next] | [standalone]

#185655

tony mollica wrote:

> I'd like to know if others have the same issue or is it my particular
> installation, which was a new, clean install to a new disk.

No issues, even with new installation on new disk :)

As Greg wrote, please share the issues.

Going back - might be an option perhaps for the next 2-4y.
changing dists - you may face same on other dist as well

regards

[toc] | [prev] | [next] | [standalone]

#185739

Hi there


On 21/08/17 18:29, deloptes wrote:

> No issues, even with new installation on new disk :)

Upgrade from amd64 Jessie (insserv, bare ALSA).
I kind of miss xfce-mixer Alsamixergui works, but xfce-mixer looked 
better. I'm very happy that Firefox works on bare ALSA.

> As Greg wrote, please share the issues.

I posted a few things, probably kernel bugs.
Apart from that, seamless transition. Even my serial mouse still works.
Rkhunter nags a bit about SSH. Even though things seem to be OK. I still 
have to look into that.

> Going back - might be an option perhaps for the next 2-4y.
> changing dists - you may face same on other dist as well


Regards,
Rob

[toc] | [prev] | [next] | [standalone]

#185820

Hi there


On 22/08/17 21:16, Rob van der Putten wrote:

> Upgrade from amd64 Jessie (insserv, bare ALSA).
> I kind of miss xfce-mixer Alsamixergui works, but xfce-mixer looked 
> better.

I use qasmixer now;
http://www.sput.nl/software/qasmixer.png
I removed the xfce4 meta package, since it insists on pulse related stuff.
There is no xfce4-artwork in Stretch, but the Jessie version works.

> I'm very happy that Firefox works on bare ALSA.

> I posted a few things, probably kernel bugs.
> Apart from that, seamless transition. Even my serial mouse still works.
> Rkhunter nags a bit about SSH. Even though things seem to be OK. I still 
> have to look into that.

I added;
Protocol 2
PermitRootLogin no
to /etc/ssh/sshd_config


Regards,
Rob

[toc] | [prev] | [next] | [standalone]

#185826

On Thu, Aug 24, 2017 at 02:49:00PM +0200, Rob van der Putten wrote:
> Hi there
> 
> 
> On 22/08/17 21:16, Rob van der Putten wrote:
> 
> > Upgrade from amd64 Jessie (insserv, bare ALSA).
> > I kind of miss xfce-mixer Alsamixergui works, but xfce-mixer looked
> > better.
> 
> I use qasmixer now;
> http://www.sput.nl/software/qasmixer.png
> I removed the xfce4 meta package, since it insists on pulse related stuff.
> There is no xfce4-artwork in Stretch, but the Jessie version works.
> 
> > I'm very happy that Firefox works on bare ALSA.
> 
> > I posted a few things, probably kernel bugs.
> > Apart from that, seamless transition. Even my serial mouse still works.
> > Rkhunter nags a bit about SSH. Even though things seem to be OK. I still
> > have to look into that.
> 
> I added;
> Protocol 2
> PermitRootLogin no
> to /etc/ssh/sshd_config

As of Stretch, the standard OpenSSH sshd does not support
Protocol 1, so there's no particular reason to enforce it 
by stating Protocol 2.

PermitRootLogin now defaults to "prohibit-password", which
means that you can log in as root with a proper SSH key or
via other methods you have set up, but not with a password.
Another useful argument is forced-commands-only, which requires
both public-key authentication and a command="blah blah" option
in the authorized_keys file, and only allows those commands to
be run. If you've got a pull backup system, that can help.

-dsr-

[toc] | [prev] | [next] | [standalone]

#185827

Hi there


On 24/08/17 15:39, Dan Ritter wrote:

> As of Stretch, the standard OpenSSH sshd does not support
> Protocol 1, so there's no particular reason to enforce it
> by stating Protocol 2.

I assumed as much. It's just a simple way to keep rkhunter happy.

> PermitRootLogin now defaults to "prohibit-password", which
> means that you can log in as root with a proper SSH key or
> via other methods you have set up, but not with a password.
> Another useful argument is forced-commands-only, which requires
> both public-key authentication and a command="blah blah" option
> in the authorized_keys file, and only allows those commands to
> be run. If you've got a pull backup system, that can help.

The alternative would be to reconfigure rkhunter.


Regards,
Rob

[toc] | [prev] | [next] | [standalone]

#185851

On Thu 24 Aug 2017 at 15:44:30 +0200, Rob van der Putten wrote:

> Hi there
> 
> 
> On 24/08/17 15:39, Dan Ritter wrote:
> 
> >As of Stretch, the standard OpenSSH sshd does not support
> >Protocol 1, so there's no particular reason to enforce it
> >by stating Protocol 2.
> 
> I assumed as much. It's just a simple way to keep rkhunter happy.
> 
> >PermitRootLogin now defaults to "prohibit-password", which
> >means that you can log in as root with a proper SSH key or
> >via other methods you have set up, but not with a password.
> >Another useful argument is forced-commands-only, which requires
> >both public-key authentication and a command="blah blah" option
> >in the authorized_keys file, and only allows those commands to
> >be run. If you've got a pull backup system, that can help.
> 
> The alternative would be to reconfigure rkhunter.

You could make a start by purging it from your system. It performs no
useful function.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#185852

On 24-08-17, Brian wrote:
> On Thu 24 Aug 2017 at 15:44:30 +0200, Rob van der Putten wrote:
> 
> > Hi there
> > 
> > 
> > On 24/08/17 15:39, Dan Ritter wrote:
> > 
> > >As of Stretch, the standard OpenSSH sshd does not support
> > >Protocol 1, so there's no particular reason to enforce it
> > >by stating Protocol 2.
> > 
> > I assumed as much. It's just a simple way to keep rkhunter happy.
> > 
> > >PermitRootLogin now defaults to "prohibit-password", which
> > >means that you can log in as root with a proper SSH key or
> > >via other methods you have set up, but not with a password.
> > >Another useful argument is forced-commands-only, which requires
> > >both public-key authentication and a command="blah blah" option
> > >in the authorized_keys file, and only allows those commands to
> > >be run. If you've got a pull backup system, that can help.
> > 
> > The alternative would be to reconfigure rkhunter.
> 
> You could make a start by purging it from your system. It performs no
> useful function.
> 
> -- 
> Brian.
> 

Could you explain that bit more, please?

[toc] | [prev] | [next] | [standalone]

#185854

On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:

> On 24-08-17, Brian wrote:
> > On Thu 24 Aug 2017 at 15:44:30 +0200, Rob van der Putten wrote:
> > 
> > > Hi there
> > > 
> > > 
> > > On 24/08/17 15:39, Dan Ritter wrote:
> > > 
> > > >As of Stretch, the standard OpenSSH sshd does not support
> > > >Protocol 1, so there's no particular reason to enforce it
> > > >by stating Protocol 2.
> > > 
> > > I assumed as much. It's just a simple way to keep rkhunter happy.
> > > 
> > > >PermitRootLogin now defaults to "prohibit-password", which
> > > >means that you can log in as root with a proper SSH key or
> > > >via other methods you have set up, but not with a password.
> > > >Another useful argument is forced-commands-only, which requires
> > > >both public-key authentication and a command="blah blah" option
> > > >in the authorized_keys file, and only allows those commands to
> > > >be run. If you've got a pull backup system, that can help.
> > > 
> > > The alternative would be to reconfigure rkhunter.
> > 
> > You could make a start by purging it from your system. It performs no
> > useful function.
> > 
> > -- 
> > Brian.
> > 
> 
> Could you explain that bit more, please?

apt-get purge rkhunter. Enough?

[toc] | [prev] | [next] | [standalone]

#185855

On 24-08-17, Brian wrote:
> On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:
> 
> > On 24-08-17, Brian wrote:
> > > On Thu 24 Aug 2017 at 15:44:30 +0200, Rob van der Putten wrote:
> > > 
> > > > Hi there
> > > > 
> > > > 
> > > > On 24/08/17 15:39, Dan Ritter wrote:
> > > > 
> > > > >As of Stretch, the standard OpenSSH sshd does not support
> > > > >Protocol 1, so there's no particular reason to enforce it
> > > > >by stating Protocol 2.
> > > > 
> > > > I assumed as much. It's just a simple way to keep rkhunter happy.
> > > > 
> > > > >PermitRootLogin now defaults to "prohibit-password", which
> > > > >means that you can log in as root with a proper SSH key or
> > > > >via other methods you have set up, but not with a password.
> > > > >Another useful argument is forced-commands-only, which requires
> > > > >both public-key authentication and a command="blah blah" option
> > > > >in the authorized_keys file, and only allows those commands to
> > > > >be run. If you've got a pull backup system, that can help.
> > > > 
> > > > The alternative would be to reconfigure rkhunter.
> > > 
> > > You could make a start by purging it from your system. It performs no
> > > useful function.
> > > 
> > > -- 
> > > Brian.
> > > 
> > 
> > Could you explain that bit more, please?
> 
> apt-get purge rkhunter. Enough?
> 

No, not really. Why do you think that rkhunter is useless?

[toc] | [prev] | [next] | [standalone]

#185856

On Thu 24 Aug 2017 at 21:31:55 +0200, Dejan Jocic wrote:

> On 24-08-17, Brian wrote:
> > On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:
> > 
> > > On 24-08-17, Brian wrote:
> > > > On Thu 24 Aug 2017 at 15:44:30 +0200, Rob van der Putten wrote:
> > > > 
> > > > > Hi there
> > > > > 
> > > > > 
> > > > > On 24/08/17 15:39, Dan Ritter wrote:
> > > > > 
> > > > > >As of Stretch, the standard OpenSSH sshd does not support
> > > > > >Protocol 1, so there's no particular reason to enforce it
> > > > > >by stating Protocol 2.
> > > > > 
> > > > > I assumed as much. It's just a simple way to keep rkhunter happy.
> > > > > 
> > > > > >PermitRootLogin now defaults to "prohibit-password", which
> > > > > >means that you can log in as root with a proper SSH key or
> > > > > >via other methods you have set up, but not with a password.
> > > > > >Another useful argument is forced-commands-only, which requires
> > > > > >both public-key authentication and a command="blah blah" option
> > > > > >in the authorized_keys file, and only allows those commands to
> > > > > >be run. If you've got a pull backup system, that can help.
> > > > > 
> > > > > The alternative would be to reconfigure rkhunter.
> > > > 
> > > > You could make a start by purging it from your system. It performs no
> > > > useful function.
> > > > 
> > > > -- 
> > > > Brian.
> > > > 
> > > 
> > > Could you explain that bit more, please?
> > 
> > apt-get purge rkhunter. Enough?
> > 
> 
> No, not really. Why do you think that rkhunter is useless?

It does not anything of consequence.

-- 
Brian

[toc] | [prev] | [next] | [standalone]

#185857

On 24-08-17, Brian wrote:
> On Thu 24 Aug 2017 at 21:31:55 +0200, Dejan Jocic wrote:
> 
> > On 24-08-17, Brian wrote:
> > > On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:
> > > 
> > > > On 24-08-17, Brian wrote:
> > > > > > The alternative would be to reconfigure rkhunter.
> > > > > 
> > > > > You could make a start by purging it from your system. It performs no
> > > > > useful function.
> > > > > 
> > > > > -- 
> > > > > Brian.
> > > > > 
> > > > 
> > > > Could you explain that bit more, please?
> > > 
> > > apt-get purge rkhunter. Enough?
> > > 
> > 
> > No, not really. Why do you think that rkhunter is useless?
> 
> It does not anything of consequence.
> 
> -- 
> Brian
> 

Do you find checking for possible rootkits is useless, or you are just
not happy how rkhunter performs that function?

[toc] | [prev] | [next] | [standalone]

#185865

On Thu 24 Aug 2017 at 21:56:51 +0200, Dejan Jocic wrote:

> On 24-08-17, Brian wrote:
> > On Thu 24 Aug 2017 at 21:31:55 +0200, Dejan Jocic wrote:
> > 
> > > On 24-08-17, Brian wrote:
> > > > On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:
> > > > 
> > > > > On 24-08-17, Brian wrote:
> > > > > > > The alternative would be to reconfigure rkhunter.
> > > > > > 
> > > > > > You could make a start by purging it from your system. It performs no
> > > > > > useful function.
> > > > > > 
> > > > > > -- 
> > > > > > Brian.
> > > > > > 
> > > > > 
> > > > > Could you explain that bit more, please?
> > > > 
> > > > apt-get purge rkhunter. Enough?
> > > > 
> > > 
> > > No, not really. Why do you think that rkhunter is useless?
> > 
> > It does not anything of consequence.
> > 
> > -- 
> > Brian
> > 
> 
> Do you find checking for possible rootkits is useless, or you are just
> not happy how rkhunter performs that function?

A well-documented case of rkhunter discovering a rootkit in the last
ten years (the 1000s of false positives do not count) would go a long
way to establishing its credence,

[toc] | [prev] | [next] | [standalone]

#185866

On 24-08-17, Brian wrote:
> On Thu 24 Aug 2017 at 21:56:51 +0200, Dejan Jocic wrote:
> 
> > On 24-08-17, Brian wrote:
> > > On Thu 24 Aug 2017 at 21:31:55 +0200, Dejan Jocic wrote:
> > > 
> > > > On 24-08-17, Brian wrote:
> > > > > On Thu 24 Aug 2017 at 21:16:26 +0200, Dejan Jocic wrote:
> > > > > 
> > > > > > On 24-08-17, Brian wrote:
> > > > > > > > The alternative would be to reconfigure rkhunter.
> > > > > > > 
> > > > > > > You could make a start by purging it from your system. It performs no
> > > > > > > useful function.
> > > > > > > 
> > > > > > > -- 
> > > > > > > Brian.
> > > > > > > 
> > > > > > 
> > > > > > Could you explain that bit more, please?
> > > > > 
> > > > > apt-get purge rkhunter. Enough?
> > > > > 
> > > > 
> > > > No, not really. Why do you think that rkhunter is useless?
> > > 
> > > It does not anything of consequence.
> > > 
> > > -- 
> > > Brian
> > > 
> > 
> > Do you find checking for possible rootkits is useless, or you are just
> > not happy how rkhunter performs that function?
> 
> A well-documented case of rkhunter discovering a rootkit in the last
> ten years (the 1000s of false positives do not count) would go a long
> way to establishing its credence,
> 

So, those in security/forensics who recommend use of rkhunter have just
been silly? Interesting. But think that I'll use it anyway, just to be
on the safe side. It does not hurt.

[toc] | [prev] | [next] | [standalone]

#185892

On 2017-08-24, Dejan Jocic <jodejka@gmail.com> wrote:
>> > 
>> > Do you find checking for possible rootkits is useless, or you are just
>> > not happy how rkhunter performs that function?
>> 
>> A well-documented case of rkhunter discovering a rootkit in the last
>> ten years (the 1000s of false positives do not count) would go a long
>> way to establishing its credence,
>> 
>
> So, those in security/forensics who recommend use of rkhunter have just
> been silly? Interesting. But think that I'll use it anyway, just to be
> on the safe side. It does not hurt.
>

The validity of a statement should be judged by its evidence, not its
source.

Of course, an appeal to authority without citing the authoritative
source to which one appeals is unlikely to convince anyone but some poor
sap already convinced in the first place.

This way, we can all settle back into the comfortable armchairs of our
preconceived convictions.

Thank you for a pause that refreshes.


-- 
Only the coward who has more fear of death than dignity can comfort himself with the fact that
his body will in time live again in the grass, in the stones, in the toad. To find one's
immortality in the transmutation of substances is as strange as to prophesy a brilliant future
for the case after a precious violin has been broken and becomes useless. — "Ward 6"

[toc] | [prev] | [next] | [standalone]

#185656

[Multipart message — attachments visible in raw view] — view raw

On 2017-08-21 09:08 -0700 tony mollica <tjm3@threedogs.net> wrote:
>I don't usually complain about free stuff but, for me, stretch has 
>become a distant back-runner to previous releases.  Jessie was fast and 
>everything worked.  Stretch has become a day to day challenge for even 
>minor issues.  Going back or changing dists.
>
>I'd like to know if others have the same issue or is it my particular 
>installation, which was a new, clean install to a new disk.

I made a fresh install too and I have not had any major problem.

Something that stopped working (apparently because of the change
to libinput) is changing "Device Accel Constant Deceleration" with xinput
to make the cursor slower. But now I use “Coordinate Transformation
Matrix“ for the same effect.

-- 
Do not eat animals, respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web