News for hackers. Stuff that matters.
Re:HipChat security notice by briandear on Monday April 24, 2017 @07:22PM (#14189353)
HipChat has been a pile of crap for a long time. Why people willingly use that over Slack remains a mystery.
Re:HipChat security notice by Consultant32452 on Monday April 24, 2017 @07:34PM (#14189424)
As far as usability and all that I really like Hipchat. I haven't gotten the chance to use Slack, but I've got no complaints on the Hipchat application itself. My current megacorp employer uses it as part of a big contract with Atlassian, but ours is hosted internally. I don't know the intimate details of self-hosting, but I assume that mitigates most of the security concerns.
Re:HipChat security notice by X-Istence on Monday April 24, 2017 @07:31PM (#14189413)
Slack does the same thing... files are uploaded to S3 as well. Slack isn't a panacea when it comes to security.
Re:HipChat security notice by briandear on Monday April 24, 2017 @07:36PM (#14189447)
Being uploaded to S3 isn't the problem; it's public access to the S3 URL that's the issue. You can't publicly access an uploaded Slack S3 file.
Re:HipChat security notice by pavel_lishin on Monday April 24, 2017 @07:33PM (#14189423)
Hipchat offers a self-hosted option, which is a requirement for many companies that very specifically don't want their chat logs and files living in some s3 bucket.