Linked by Thom Holwerda on Fri 12th Jun 2009 18:25 UTC
Thread beginning with comment 368517
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2007-09-06
My personal problem with Samba stems directly from CIFS; clear text protocol. Why does Windows still spray my user password hash across the network like this? While your grabbing your important document or sending your print job, anyone on the network can grab your login info and start working on it. Granted, complicated passwords make breaking the PreAth but the fact that I can get that information still already created security problems at home and work.
Thanks to a lack of support for ssh and sshfs on the Windows side (I think it's the only OS that doesn't offer support still), it's not even a choice. All my other platforms integrate safely on the network but I have to jump through hoops to come close to that same security as soon as Windows is involved.
I think the difference between the three though is this; WINE and Samba provide a function. Mono is a .net clone. It's a programming framework for the Studio.net folk.
Unlike Samba, I don't have personal investment in Mono or Gnome so I'm a third party observer on this one.