Those who joined Slack after 2015 – roughly 99% of its current user base, according to Slack – are apparently unaffected, as are accounts that require single-sign through a company’s network. “However, we do recognize that this is inconvenient for affected users, and we apologize.” “We have no reason to believe that any of these accounts were compromised, but we believe that this precaution is worth any inconvenience the reset may cause,” the company said in a blog post. That prompted the decision to reset passwords for all accounts active during that period. The company was anonymously tipped off recently that user credentials related to accounts logged in to Slack during the 2015 security incident might be affected. The attackers also inserted code that stole passwords in plain text as they were entered by users, prompting Slack to encourage customers to reset passwords. The incident allowed hackers to gain access to a database containing profile information such as usernames and encrypted passwords. On an unrelated note, Slack last week announced that it will reset passwords for users that may have been affected by a 2015 hack. Company rolls out password reset related to ’15 breach
In addition, the desktop app will soon have some offline capabilities, allowing users with a spotty internet connection to launch the software and maintain access to previously cached conversations. "I haven’t heard of any problems before this, but it’s good that Slack recognized the limitations in their current approach and moved to fix them,” he said. “Companies that use a large number of workspaces will see improvements in desktop memory use and startup times, likely leading to snappier desktop performance for users. “These changes are mostly under-the-hood and should be unnoticed by users,” said Larry Cannell, a research director at Gartner. While many users may be unaware of the change, those that routinely switch between memory-draining applications may benefit. Slack also said the desktop app will run more efficiently, with a 50% reduction in memory use in some cases.
0 kommentar(er)
