SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The rules clearly invites anyone to open new threads...
"When posting in an existing thread, ensure that what you're posting is on-topic and relevant to the thread. If the content of your post will interfere with the current discussion, you should start a new thread."
Do not post any messages that are obscene, vulgar, sexually-orientated, hateful, threatening, hostile or insulting.
Personal attacks on others will not be tolerated.
Flame Wars will not be tolerated.
Do not post if you do not have anything constructive to say in the post.
When posting in an existing thread, ensure that what you're posting is on-topic and relevant to the thread. If the content of your post will interfere with the current discussion, you should start a new thread.
Please try to stay on topic.
Please be civil to each other and there is nothing wrong with regular members asking to stay on topic.
This is a security release in order to address the following defects:
o CVE-2016-2124: SMB1 client connections can be downgraded to plaintext
authentication.
https://www.samba.org/samba/security/CVE-2016-2124.html
o CVE-2020-25717: A user on the domain can become root on domain members.
https://www.samba.org/samba/security/CVE-2020-25717.html
(PLEASE READ! There are important behaviour changes described)
o CVE-2020-25718: Samba AD DC did not correctly sandbox Kerberos tickets issued
by an RODC.
https://www.samba.org/samba/security/CVE-2020-25718.html
o CVE-2020-25719: Samba AD DC did not always rely on the SID and PAC in Kerberos
tickets.
https://www.samba.org/samba/security/CVE-2020-25719.html
o CVE-2020-25721: Kerberos acceptors need easy access to stable AD identifiers
(eg objectSid).
https://www.samba.org/samba/security/CVE-2020-25721.html
o CVE-2020-25722: Samba AD DC did not do suffienct access and conformance
checking of data stored.
https://www.samba.org/samba/security/CVE-2020-25722.html
o CVE-2021-3738: Use after free in Samba AD DC RPC server.
https://www.samba.org/samba/security/CVE-2021-3738.html
o CVE-2021-23192: Subsequent DCE/RPC fragment injection vulnerability.
https://www.samba.org/samba/security/CVE-2021-23192.html
Aside from the NVIDIA GBM support, the rest of XWayland 21.1.3 is basic bug fixing. Notable, it includes a small but of impact bugfix for constant superfluous eglMakeCurrent calls with negative effects on rendering performances.
I have built XWayland 21.1.3 by myself and the applications which uses XWayland are visible snappy on Wayland/Plasma5, while I found NO adverse effects.
Last edited by LuckyCyborg; 11-10-2021 at 02:33 PM.
Not sure if this has been requested before, but kwalletcli provides pinentry-kwallet, which saves entries given to a pinentry to KWallet. mksh is a dependency; this gives the MirBSD Korn Shell, an implementation of ksh. These are both already in the Slackbuilds repository - kwalletcli is in ./desktop/kwalletcli, mksh is in ./system/mksh. Can confirm these Slackbuilds work on -current as of 2021/11/10.
(If anyone does what I am trying to achieve here in a different way I'm all ears - this is all I could find to help me not need to type in my GPG passwords every time I use them!)
The candidates window rendering off-screen in all GTK3 apps is a huge problem, making ibus almost unusable. You basically do not see what you are typing.
found a problem:
each time after my laptop resume from sleep, there is a dhcpcd remained.
can't told which update caused this, just noticed recently.
my system is always updated to slackware64-current.
found a problem:
each time after my laptop resume from sleep, there is a dhcpcd remained.
can't told which update caused this, just noticed recently.
my system is always updated to slackware64-current.
LOL no. thats not how you add http to iptables especially so since http dopes not use UDP but you knew that, and a special outbound rule for 80, now I KNOW your just trolling and after I've finished laughing my arse off at you, you shall be ignored accordingly.
Man this firewall request thing is not going to stop until 2022 apparently.
And to be fair, there was only dport 80 and sport 80 specified so can you explain how port 1900 is relevant here?
There can be many reasons for someone to open the port 80 for outbound, like a video surveillance system behind that router (LC talked about his custom made router) or just torrenting with fallback to this port, when the ISP uses a strong hand on the dedicated ports for torrent. And probably many other reasons about I do not care.
However, I fully agree to others said here, that this overreaction to a request to add whatever program is too much and not in the right place. In the end, nobody asked for the removal of iptables, but just to add a software, supposedly more facile.
Last edited by ZhaoLin1457; 11-11-2021 at 12:18 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
