Evaluating Confidential Info
Now that Playground is saving all snippets for later use, how would one evaluate something for which there should be no record e.g. logging into a server? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Sean P. DeNigris wrote
Now that Playground is saving all snippets for later use, how would one evaluate something for which there should be no record e.g. logging into a server?
Bump. This is a big security hole. Maybe I should cross-post to the Moose list... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615p4837488.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Write your code in the new/re-implementation of the old workspace ? Workspace open. Write code that asks for the password via a dialog ? When a bad guy has access to your machine you are doomed anyway, no ?
On 14 Jul 2015, at 21:41, Sean P. DeNigris <sean@clipperadams.com> wrote:
Sean P. DeNigris wrote
Now that Playground is saving all snippets for later use, how would one evaluate something for which there should be no record e.g. logging into a server?
Bump. This is a big security hole. Maybe I should cross-post to the Moose list...
----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615p4837488.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Sven Van Caekenberghe-2 wrote
Write your code in the new/re-implementation of the old workspace ?
That works, thanks. Sven Van Caekenberghe-2 wrote
When a bad guy has access to your machine you are doomed anyway, no ?
Probably true, but one can imagine, say, I log in on someone else's machine. Also, in my particular case, once logged in, the user was limited to a few actions unless they were extremely savvy, where having the credentials would give them much more/easier access. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615p4837505.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Hi Sean, Sorry for the slow reaction. Indeed, you raise a good point that was not considered until now. As the ESUG talk from today showed, we area already working on the new version of the Playground, and we will consider your use case as well. In the meantime, is using the Workspace a good enough workaround? Cheers, Doru On Tue, Jul 14, 2015 at 11:38 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Sven Van Caekenberghe-2 wrote
Write your code in the new/re-implementation of the old workspace ?
That works, thanks.
Sven Van Caekenberghe-2 wrote
When a bad guy has access to your machine you are doomed anyway, no ?
Probably true, but one can imagine, say, I log in on someone else's machine. Also, in my particular case, once logged in, the user was limited to a few actions unless they were extremely savvy, where having the credentials would give them much more/easier access.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615p4837505.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com "Every thing has its own flow"
Tudor Girba-2 wrote
In the meantime, is using the Workspace a good enough workaround?
Yes, that's fine for my use case. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Evaluating-Confidential-Info-tp4836615p4837718.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (3)
-
Sean P. DeNigris -
Sven Van Caekenberghe -
Tudor Girba