Hello to everybody,
I want to inform you that for the upcoming maintenance release R14.0.4 the
number of supported distributions will be reduced. Will be excluded versions
of Ubuntu that are no longer supported. In the same way will be reduced
distributions in the Preliminary Stable Builds repository.
Supported distributions:
+ Debian 9 - Stretch (preliminary)
+ Debian 8 - Jessie
+ Debian 7 - Wheezy
+ Debian 6 - Squeeze
+ Raspbian Wheezy
+ Ubuntu 16.10 - Yakkety (preliminary)
+ Ubuntu 16.04 - Xenial (LTS)
+ Ubuntu 14.04 - Trusty (LTS)
+ Ubuntu 12.04 - Precise (LTS)
+ Ubuntu 10.04 - Lucid (LTS)
Discontinued distribution:
+ Ubuntu 15.10 - Wily
+ Ubuntu 15.04 - Vivid
+ Ubuntu 14.10 - Utopic
+ Ubuntu 13.10 - Saucy
+ Ubuntu 13.04 - Raring
+ Ubuntu 12.10 - Quantal
+ Ubuntu 11.10 - Oneiric
+ Ubuntu 11.04 - Natty
+ Ubuntu 10.10 - Maverick
Please, if you use one of discontinued Ubuntu distributions, you should
consider upgrading to one of the LTS versions.
Cheers
--
Slávek
Hi
This is the first time I have such an experience. I installed Kubuntu
14.04 and trinity via
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
deb-src http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Everything went smooth wireless net can be configured with
tdenetworkmanager, but when I try to set up the wired net, via the
networktool I run into a problem.
I use all the parameters I used in previous trinity + Kubuntu
installations (namely 10.04 and 12.04)
static IP number
DNS server
Gateway.
The connection works for a couple of seconds and then crashes the
problem see to be the Gateway, when I restart the configuration tool the
value has been deleted.
Anybody has an idea what do?
That is a very serious problem, right now use the Wifi connection, but
this has severe restriction in the network I am using.
Thanks
Uwe Brauer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The kweather-trinity applet version 4:14.0.3-0debian8.0.0+0 no longer
works in Jessie. When I tried to use it claims that all the weather
stations in the weather stations setup window do not exist.
Regards, Ken Heard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAle9zGcACgkQlNlJzOkJmTd/VQCfSa6qFaiN0BdV0A66VdHMf6jx
BakAnRvVuS80XYJCbO2iQYO0vhGp8jaI
=RJ7c
-----END PGP SIGNATURE-----
Dear Trinity users,
I can't get KMilo plugin to work on my ThinkPad R61 under Debian Wheezy. Firstly, I need
kmilo-legacy-trinity for the KMilo plugin to show up in the Control Center. The /dev/nvram device
exists and has corect permissions (666). I select the checkbox to activate KMilo but nothing
happens. None of the special buttons work, eg. when I press the ThinkVantage button it does not
launch Konsole. The only things that work are sound and brightness control buttons, but these
used to work without KMilo. Also, I believe KMilo should provide a nice OSD for sound and
brightness changes but I have no OSD when changing any of these. Can anyone offer suggestions how
to solve, or at least diagnose, the problem?
Jan
---
Politechnika Łódzka
Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
This email contains information intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient or if you have received this message in error,
please notify the sender and delete it from your system.
Greetings all;
Is there someone familiar with fail2ban here?
I just installed it and started it with the installation defaults, which I do not know since the init script has no "dump" option.
However that bit of hungry guard dog only protects this machine, leaving the other 4 or sometimes 5 on my local network still open.
So specifically, is there a way to broadcast the rules it applies to the other 4 or 5 machines, protecting them at the same time?
Or possibly broadcast them to the router, which is running dd-wrt, and which is considered one of the more bulletproof reflash's about. I may be lucky, but since I do have a port forward to allow my web server, there is a potential attack point.
Advice to a fail2ban new bee?
Thank you.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Thursday 11 August 2016 15:44:24 Doug wrote:
> On 08/11/2016 12:50 PM, Gene Heskett wrote:
> > On Thursday 11 August 2016 12:47:09 Nicolas George wrote:
> > CC:ing emc-developers, and trinity-users who may not yet be aware of
> > this tcp attack vector thats quite dangerous. And my post to
> > trinity-users was in error, so this corrects it.
> >
> >> Le quintidi 25 thermidor, an CCXXIV, Gene Heskett a écrit :
> >>> to add should be changed to forward slashes:
> >>
> >> You are wrong, sysctl supports both slashes and dots as separators.
> >>
> >> Regards,
> >
> > I changed it back Nicolas, and sysctl -p now returns:
> > root@coyote:/etc/init.d# sysctl -p
> > sysctl: cannot stat /proc/sys//net.ipv4.tcp_challenge_ack_limit: No
> > such file or directory
> >
> > Put the slashes back and I get this:
> > root@coyote:/etc/init.d# sysctl -p
> > .net.ipv4.tcp_challenge_ack_limit = 999999999
> >
> > Which I assume is the correct response. And yet the echo shows all
> > dots.
> >
> > WTH? Ahh, my bad, no damned biscuit, an extra leading slash snuck
> > in. But if a dot and a slash are the same to sysctl, I should have a
> > file in the wrong place? But I do not. /net is empty. It is in the
> > right place now. And cats the correct value.
> >
> > Sorry about the confusion everybody.
> >
> > Cheers, Gene Heskett
>
> Running PCLOS. I put in the original command with dots. When I run
> sysctl.p from a root environment I get no response, but no error
> either. Don't know the significance of that.
>
> --doug
Neither do I Doug, sorry. See the announcement on /. today & read the
link to the post from the guys that found it that is in the story,
UCsomething IIRC, see below. A closer read may answer it.
<https://ucrtoday.ucr.edu/39030>
And please keep things like this on the list you read it from. A PM is
unfair to the other readers of the list you read it on, so I'll cc the
three lists it was cross posted to as it sounds pretty serious to me.
And I just noted that the sysctl command you quoted above is incorrect,
its sysctl -p, not sysctl.p.
Maybe that helps?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Thursday 11 August 2016 12:47:09 Nicolas George wrote:
CC:ing emc-developers, and trinity-users who may not yet be aware of this
tcp attack vector thats quite dangerous. And my post to trinity-users
was in error, so this corrects it.
> Le quintidi 25 thermidor, an CCXXIV, Gene Heskett a écrit :
> > to add should be changed to forward slashes:
>
> You are wrong, sysctl supports both slashes and dots as separators.
>
> Regards,
I changed it back Nicolas, and sysctl -p now returns:
root@coyote:/etc/init.d# sysctl -p
sysctl: cannot stat /proc/sys//net.ipv4.tcp_challenge_ack_limit: No such
file or directory
Put the slashes back and I get this:
root@coyote:/etc/init.d# sysctl -p
.net.ipv4.tcp_challenge_ack_limit = 999999999
Which I assume is the correct response. And yet the echo shows all
dots.
WTH? Ahh, my bad, no damned biscuit, an extra leading slash snuck in.
But if a dot and a slash are the same to sysctl, I should have a file in
the wrong place? But I do not. /net is empty. It is in the right place
now. And cats the correct value.
Sorry about the confusion everybody.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Hi
The latest stable seamonkey freezes every 10 min or so, using Kubuntu
14.04, that did not happen in Kubuntu 10.04.
Does anybody have a similar experience?
Uwe Brauer
Greets!
what must we who are using trinity do to avoid the tcp exploit?
I found the following instructions from L. Weinstein's privacy mail
list but they don't corrrespond to anything in my sysctl.conf.
Felmon
----- quote -----
Workaround for serious TCP exploit previously discussed
https://plus.google.com/+LaurenWeinstein/posts/gWSj2sYExoB
Here is the recommended workaround for Linux/Android clients/servers
for the serious TCP exploit discussed in:
https://threatpost.com/serious-tcp-bug-in-linux-systems-allows-traffic-hija…
This one will work for Ubuntu as is, and for various other Linux
distributions with suitable modifications. The point is to bump the
ACK limit way up. Note that some of the pages announcing this exploit
appear to be contaminated with browser hijack "fake technical support"
warning sites. Beware. Close your browser immediately if you hit one
if you can, otherwise reboot and don't restore crashed pages.
The workaround for the TCP exploit:
Open /etc/sysctl.conf, append a command:
/net.ipv4/tcp_challenge_ack_limit = 999999999
Use "sysctl -p" to update the configuration.
_______________________________________________
privacy mailing list
https://lists.vortex.com/mailman/listinfo/privacy
On booting a new installed xenial with trinity tdm I get the error message:
"A start job is running for Hold until boot process finishes up(time/no limit)" which prevents starting the console logins.
Using sddm or lightdm works together with systemd.
I have looked into the systemd configuration of them both and changed the file
/lib/systemd/system/tdm.service according to the sddm configuration to
[Unit]
Description=Trinity Display Manager
Documentation=man:tdm-trinity(1)
Conflicts=getty(a)tty7.service
After=getty(a)tty7.service
# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service plymouth-quit-wait.se
OnFailure=plymouth-quit.service
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(basename $(cat /etc/X11/default-display-manager 2>
ExecStart=/opt/trinity/bin/tdm
Restart=always
RestartSec=1s
With this file the plymouth/systemd handshake seams to work.
Maybe this helps someone else.
Stef
