seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2018/01/17, 13:57:01


Help

Recent Posts

Pages: [1] 2 3 ... 10
1
Upgrade Warnings (DE / EN) / Re: mate-applet-brisk-menu
« Last post by devil on Today at 13:40:00 »
Please submit a bug-report with debian for the broken package, if such a bug report does not yet exist.
2
Upgrade Warnings (DE / EN) / Re: Info about Meltdown and Spectre Bugs
« Last post by devil on Today at 11:54:03 »
The vulnerability against Spectre might be mitigated after the weekend if:

Kernel 4.15 is released (most likely)

and

GCC 7.3 is released in Debian (needed to build 4.15 in a useful way (where it makes use of Retpoline-Patches against Spectre-Types Variant 1 (Bounds Check Bypass) and Variant 2 (Branch Target Injection)).
3
Upgrade Warnings (DE / EN) / mate-applet-brisk-menu
« Last post by threepio on Today at 11:02:44 »
In >mate-applet-brisk-menu_0.5.0-1_amd64.deb< is a bug.
If you are opening "edit menue" = "mozo" from brisk-menue it disappears itself in mate-panel, so you have to restart mate-panel or use
>mate-applet-brisk-menu_0.4.5-1_amd64.deb< ,which is working fine.
Maybe someone of you is using mate too.
4
Thanks a lot for this very good info.
I don`t need it for SIDU, it is safe, but it is helpfully for others in Linux community.  :)
5
Here is mine
Code: [Select]
Spectre and Meltdown mitigation detection tool v0.31

Checking for vulnerabilities against running kernel Linux 4.14.13-towo.2-siduction-amd64 #1 SMP PREEMPT siduction 4.14-24 (2018-01-15) x86_64
CPU is Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable: Minimal generic ASM retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Checking whether we're safe according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

A false sense of security is worse than no security at all, see --disclaimer
6
Software Support (EN) / [SOLVED] new problem with cron
« Last post by hightime on Today at 02:47:54 »

UPDATE: Problem was with my home directory. My existing login continued to work so I did not notice the problem until I tried to start a new session. Not a cron or script problem at all.

I have line in my crontab that calls getmail to fetch my mail. A few days ago it stopped working. syslog shows that cron ran it, but it never fetches my mail.
After some experimenting I found that scripts don't seem to work anymore. Here are two very simple cases.


This works:
Code: [Select]
10 * * * * /bin/touch somefile


This does not:
Code: [Select]
10 * * * * /path/to/myscript.sh  # simple bash script that calls /bin/touch somefile


I also tried calling /bin/bash with myscript.sh as an argument. In both cases, cron logs to syslog that it ran the script, but the script doesn't do anything.
Has there been some change, possibly for security reasons, that prevents scripts from actually running when invoked from cron?


7
Tried right now what is suggested on https://www.cyberciti.biz/faq/check-linux-server-for-spectre-meltdown-vulnerability/

Tested my System ...

Code: [Select]
Spectre and Meltdown mitigation detection tool v0.31

Checking for vulnerabilities against running kernel Linux 4.14.13-towo.2-siduction-amd64 #1 SMP PREEMPT siduction 4.14-24 (2018-01-15) x86_64
CPU is AMD Ryzen 7 1800X Eight-Core Processor

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable: Minimal AMD ASM retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Checking whether we're safe according to the /sys interface:  YES  (kernel confirms that your CPU is unaffected)
> STATUS:  NOT VULNERABLE  (Not affected)

A false sense of security is worse than no security at all, see --disclaimer
8
Und nu mal Butter bei die Fische: Um mal ein "Verschulden" von siduction auszuschließen, habe ich mir ein astreines und über jeglichen Verdacht einer Einmischung seitens siduction erhabenes Windows 10 Pro gestartet - und darauf jeweils einmal ein Virtualbox 5.2.6 udn 5.1.x installiert und versucht, jeweils ein debian i386 oder siduction mit liquorix-kernel zu starten - Resultat: backtrace und kernel-panic.

Daraus ergeben sich 3 Schlussfolgerungen:
a) VBox ist karpott, am Kernel des Gastsystems kann es nicht liegen.
b) Noch ein einziger Post mit diesen oder ähnlichen Anwürfen und und ich beantrage die dauerhafte Sperrung Deinen Accounts, lieber Hanisch. Es ist mir sehr ernst damit.

Um möglichen Antworten von Dir zuvorzukommen:
* Deine Meinungs- und Redefreiheit wird dadurch nicht eingeschränkt, Du darfst Deine Meinung ruhig für Dich behalten und überall verbreiten. Sogar hier, nur halt mit entsprechenden Konsequenzen.
* Auch wenn Linux freie und offene Software ist und Dir schutz-, hilf- und wehrlos ausgeliefert ist - wir sind es nicht.
* Um noch ein Missverständnis Deinerseits aufzuklären: Der Fakt, dass Linux FOSS ist, bedeutet wirklich nicht, dass Foren, die sich mit diesem Thema befassen, für Jeden offen sein müssen und man ein verbrieftes Recht darauf hat, seinen Unsinn ohne auf die Wünsche und Befindlichkeiten der Betreiber und User dieses Forums auch nur ansatzweise einzugehen zu verbreiten.
9
Prima. Da kannst Du ja Deine "Tests" endlich abschließen und woanders herumquängeln.

Und aktuell ist VBox 5.2.6. Von den Kernel-Versionen gar nicht zu reden.
10
Freie Rede (DE) / Re: liquorix-kernel
« Last post by piper on Yesterday at 17:03:44 »
Sorry, I couldn't test the installer on a real hd/ssd install, I don't have have a 386 box, my wife would have chopped a nut, it would have been ok, as I have another one, but ..  :)
Pages: [1] 2 3 ... 10