Thursday, December 14, 2017
Home Tags Syslog

Tag: Syslog

amalthyareader comments 35 Share this story A bug in the Telegram Messager app logged anything its users pasted into their chats in its syslog on macOS, even if they had opted for the end-to-end encrypted "secret" mode. The vulnerability was spotted earlier this month by Russian infosec operative Kirill Firsov, who directly and publicly challenged Telegram's flamboyant founder and chief Pavel Durov about the app's latest security flaw. Official #Telegram for MacOS logs every pasted message to syslog, even in secret chats. @durov what's going on? pic.twitter.com/MvbWguAkT0 — Kirill Firsov (@k_firsov) July 23, 2016 In an angry reply, Durov admitted that the vuln existed, but insisted it "applies only to texts that were copy-pasted from clipboard, and such texts are open to all other Mac apps anyway." He continued: "AppStore apps can NOT access syslog (starting 10.12 also true for unsigned apps).

But ANY app can read your clipboard." Durov—in response to Firsov's tweet—promised to fix the logging issue, which doesn't affect either Telegram's Android or desktop apps. He said: "So while copy-paste can not be secure anyway, I see such logging in the stable release redundant and will see it gone." @k_firsov (3)...

AppStore apps are sandboxed and can only WRITE to syslog, not READ it: https://t.co/vjoU8QVtza pic.twitter.com/1tgPMDBfak — Pavel Durov (@durov) July 24, 2016 He added: "Although this turned out to be a minor bug phrased to look big, we fixed it within minutes after learning about it." Telegram has previously boasted to be more secure than WhatsApp, though some infosec experts have cautioned against such claims.

The service uses the MTProto protocol developed by its Russian-born founder Durov, a privacy absolutist, who says that the app's so-called secret chats use end-to-end encryption and aren't backed up in the cloud. The app has attracted unwanted attention over the past year, however, after it was found to be the most popular way for terrorist organisations to stay in touch with each other and the outside world.

A recent study from security firm Trend Micro found that 34 percent of the groups it surveyed listed Telegram as their contact information. In late 2015—following bad publicity about the app—Berlin-based Telegram said it had blocked 78 "public channels" related to the Isis terrorist organisation, adding "we were disturbed to learn that Telegram's public channels were being used by ISIS to spread their propaganda." In its FAQ, the app says: "While we do block terrorist (e.g.
ISIS-related) bots and channels, we will not block anybody who peacefully expresses alternative opinions." This post originated on Ars Technica UK
An updated Samba package that fixes bugs and adds enhancements is now availablefor Red Hat Gluster Storage 3.1 Update 3 Samba is an implementation of the server message block (SMB) protocol.
Itallows the networking of Microsoft Windows®, Linux, UNIX, and otheroperating systems together, enabling access to Windows-based file andprinter shares.
Samba's use of SMB allows it to appear as a Windows serverto Windows clients.This update is a rebase to the latest upstream version of Samba 4.4,which fixes a number of bugs and adds a number of enhancements.

The mostimportant of these updates are:* Samba now supports version 3.1.1 of the SMB protocol.* The CTDB_LOGGING option has replaced the previous options CTDB_LOGFILEand CTDB_SYSLOG.* A new 'logging' option for smb.conf and several new logging backends(systemd-journal and lttng) are now available.* The 'change notify' and 'kernel change notify' options are now globaloptions rather than being specific to a share.* SMB multi-channel has been added as a Technology Preview.All users of Red Hat Gluster Storage with Samba are advised to upgrade tothis updated package. Before applying this update, make sure all previously released erratarelevant to your system have been applied.For details on how to apply this update, refer to:https://access.redhat.com/articles/11258Red Hat Gluster Storage Server 3.1 on RHEL-7 SRPMS: libtalloc-2.1.6-1.el7rhgs.src.rpm     MD5: bfac41d62ab87fd3b68d7cd4904aa7e9SHA-256: 48f21654c2f365f82fc90d7ed05749098194d441b7243914e1cc58c4a14c5baf samba-4.4.3-7.el7rhgs.src.rpm     MD5: 4556d02db2811cf2dfb2e4e38e31e736SHA-256: 0a25cabc4eec2d615f776dc5500a28c9257e99a531db5b8b26e9c1bbe73ae397   x86_64: ctdb-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 03b4c0df813c5caa33a77cc8dda386aeSHA-256: 4885728a15e9c17fd963ebaf9f04c30f47c1bb2a594df11083df1359ba5213f4 ctdb-tests-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 5740d8a1c6af97be2c1e633ccefb7a88SHA-256: 01ccd14be6d60e30c2465c42979fd9284f7e394960d6e7ab217104c3e612fbe9 libsmbclient-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 3c1291c9a1dc3bf2ba2946323044ea27SHA-256: f3137044160a8aac9d77615537ca68fcca51bed89fd164ce53f4367137397725 libsmbclient-devel-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 86abd48853e6a0fd267999b17c3816fbSHA-256: 5bd61f0257166f0710aee430a9eb87d1b19b79669510d9388dafa4366e7fb5b2 libtalloc-2.1.6-1.el7rhgs.x86_64.rpm     MD5: 1bbbfbf0e36e483d09278bbaa9bbbe39SHA-256: 55f9e4913bd398b17a92c85ad1c91cb54af1b8e2d964cbd833b049f5837f57de libtalloc-devel-2.1.6-1.el7rhgs.x86_64.rpm     MD5: f9d1647715ef786de5cb587273cbd805SHA-256: 9bab8312d6e922c1bf8511bf384f3ee9ba115f9b5acf26dcc186701676692cee libwbclient-4.4.3-7.el7rhgs.x86_64.rpm     MD5: bdb63ebe71b2805bbf114c65e19aa87dSHA-256: b2b77f7e58781d0d44011f6ff575b6fd3df6c1155b40d3f8827a326542d63b78 libwbclient-devel-4.4.3-7.el7rhgs.x86_64.rpm     MD5: eab80d7a9d91157e1fd187404093bb59SHA-256: a2cff0c66dc02ccfec853edb866778eade67a8fff35254b74304ef0ee656c34c pytalloc-2.1.6-1.el7rhgs.x86_64.rpm     MD5: 2791549ecae30a9c2320af599319a115SHA-256: 45400cc7656b53fb07f4e9d862b31adfcaaaeabf82807cf8c260987738fe688c pytalloc-devel-2.1.6-1.el7rhgs.x86_64.rpm     MD5: b102c846925459c1cb76783e1540248fSHA-256: f6a03c2e9a9ec6a85aa55fad8765088aae60a4f7dd2e8f3f41ed286b3b1b4ccc samba-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 08c69cf8d8d17d7c4630f17b709313c6SHA-256: 315097b961816aa61c4278e285c0b15fa03f0d6894f90d36d6983c776ab492f7 samba-client-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 99cd59b0e3192816a36f661bcf44aa86SHA-256: 3168c10d78f47dfd620644deb14a61fae8ca6112b20b0246d5c2959e468660c8 samba-client-libs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: af0ad60d744e7eaed98ca9a78e6d0aecSHA-256: c4d08610f93b3a89a89d5f588fef5e963e59e53bd74027ae23e491437572451c samba-common-4.4.3-7.el7rhgs.noarch.rpm     MD5: 8afdcf2fd07687e689675780ce4395a0SHA-256: 5a91d965b7434eb6baa0207e2d2891142528dfd49b40ec3510fae1ea92026fa7 samba-common-libs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: b4478a69bec6c6b6197a72581ed5dfbbSHA-256: 9073573ce722b58475f298ca5068c675dea5321931c36733852a2e59e6fbc98b samba-common-tools-4.4.3-7.el7rhgs.x86_64.rpm     MD5: bd24e0dd978247e00816e81f81a69e3aSHA-256: d7cf7721d4a5c0cdf46d907db83c28cfcfeeaef3a77d8c867add8557e0255c0f samba-dc-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 74ea3f2ef567cbf113d7966c12a32f1aSHA-256: 3c3561363438d4e1ca23a1a09a0abfa77f29a9b28c0fd6d69d9bac71fa4e1b85 samba-dc-libs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 522a0ce55e49cada20936030b5e2bcb1SHA-256: 44cb9763bcd6004609e48ab6f7a14d28a009a7c89d6655b2fb756f40ccd68599 samba-devel-4.4.3-7.el7rhgs.x86_64.rpm     MD5: cd2b6b07c1f2aceb2ba976c5b9d47c71SHA-256: f11db5aedc86169e9fbe378ab5915c40a6d78b1c9f1bc86dca528119e61c641d samba-libs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: cacc9e55ea6a0ce0ecfc3b08e337f6edSHA-256: 2195b0356d95bfcdcc0ac82b1aa644825123e6fe5a5ef93485de56f31293f10b samba-pidl-4.4.3-7.el7rhgs.noarch.rpm     MD5: e0926df67de098891ec3371b510137b7SHA-256: c90d0523e7221e184c582c656f13de1e7d52498e6d95f2861fc03caa37194186 samba-python-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 416685d77b4a1fbff4976c4fdfd22b45SHA-256: d5d557650830ebf7470c8dc34b6a4f95eaac73074c4b5e6e86873238a7b1710c samba-test-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 815e2af1d30ba86047d54eb75b21de68SHA-256: 07dc06796aad66f5197912656fb71c8dd6150961a685b161d1b4db10c28503e1 samba-test-libs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 68e7e1a8f601c8aaa641f5170e59e078SHA-256: 0a0cc2a554dd0d0b4eba1c44ae50ad0f11e6fd268b76a82d38d2f754bb70c0f9 samba-vfs-glusterfs-4.4.3-7.el7rhgs.x86_64.rpm     MD5: d0b0647da5257c5fc996e58e6171a994SHA-256: 19818a2ba51066ca273284bf3ba9bce5f622cf8c75b065705d2a108f9d8f29eb samba-winbind-4.4.3-7.el7rhgs.x86_64.rpm     MD5: e3a3ba9a627d9607cbe6fa5d26c285aeSHA-256: 594bde517b53a6ffe83eaf0ee3aa8dd121b8c4082a5978de3cbecd827feb8051 samba-winbind-clients-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 5daf7245de8b96420bff114a8377cd10SHA-256: abee757da4fba6c31898ecd44250dcdf0b2f7f860897f044ca4bb915c8ceb91b samba-winbind-krb5-locator-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 3247b2c9a6f747cf96fce2a5dc50320fSHA-256: f948443b46e888e0ea8daa7d580b7b5f85cc04923b95bfc3070b69aa514f25e8 samba-winbind-modules-4.4.3-7.el7rhgs.x86_64.rpm     MD5: 741ba0623feb6cfa5fd409357f17eedfSHA-256: d8d71c9f43e882a5c02883eba1da585e66d2622d51fa378d021fbd19bc210267   (The unlinked packages above are only available from the Red Hat Network) 1318624 - [RHEL7] [RFE] Samba rebase to 4.4 + Samba libs update1322677 - CTDB: ctdb node remains in banned state until the ctdb service is restarted.1332237 - SAMBA : New file created in windows mount is not listed in share for quite a while even after multiple refresh on the share1333360 - Samba: Multiple smbd crashes (notifyd) after a ctdb-internal network interface is brought down in a ctdb cluster.1335584 - SAMBA CRASH : Multiple smbd crash while performing VSS functionality in windows client1337569 - SMB: Getting error with upgrade and net join ldb: unable to stat module /usr/lib64/samba/ldb : No such file or directory These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from: