Anonymous user
Talk:One-time pad: Difference between revisions
m
→So little on the Page: added a comment.
(→Clarity: More on beginning a draft task.) |
m (→So little on the Page: added a comment.) |
||
| (7 intermediate revisions by 6 users not shown) | |||
Line 15:
Oh, and yep - that task suggestion page probably does need a cleanup. I would not be surprised if some suggestions are available as tasks and so probably should have their (approximate) task match appended. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 01:24, 25 November 2014 (UTC)
== Some cautions ==
/dev/random is operating system specific and often has security constraints on its use (to prevent denial of service attacks).
That means that this task is implicitly operating system specific (don't expect /dev/random to work on Windows, or an iPhone, for example) and even if the operating system is specified, you should expect this code to fail on some machines - perhaps all available examples of machines of the specified operating system.
And, of course, there's no way to guarantee that there are no eavesdroppers watching the one-time-pad being built.
Because of these constraints, either the task or the implementations should specify the operational requirements for the code. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 06:13, 13 December 2014 (UTC)
:Sure, /dev/random on Unix is easy to use, and accessible from all languages.
:On Windows, e.g. there is the [http://msdn.microsoft.com/en-us/library/windows/desktop/aa379942%28v=vs.85%29.aspx CryptGenRandom_function], which MS claims "fills a buffer with cryptographically random bytes". --[[User:Hajo|Hajo]] ([[User talk:Hajo|talk]]) 12:45, 13 December 2014 (UTC)
::Looks like you are right - /dev/random is available on iPhone and android. I'm still a bit concerned about the underlying kernel implementation on some of those systems - the whole "entropy management" thing could be better in some cases. Even Solaris has /dev/random nowadays. So it's mostly stuff like Windows, forth machines, specialty hardware, and stuff like that which don't have /dev/random --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 13:35, 13 December 2014 (UTC)
==So little on the Page ==
We need to get solutions actually on Rosetta Code. If the solution isn't on RC then it is not a solution. RC should not degenerate into a list of off-site links. This is different to cases where people link to needed libraries and /or documentation that may be off site. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 10:10, 31 March 2015 (UTC)
: Agreed. Rosetta is not a link directory. [[User:Fwend|Fwend]] ([[User talk:Fwend|talk]]) 21:42, 2 May 2016 (UTC)
: Another thing is the use (storage) of cookies when going to other sites (without even so much as a note or warning). Even worse, some sites aren't supported by the web browser that I'm currently using, making viewing of that solution problematic. I'm sure that there are Rosetta Code uses that experienced the same problem(s), but are reluctant to complain about the problem. Also, I'm fearful of one day when a site may have a virus on it, unbeknownst to the web's site owner. It would be nice if some-power-that-be make a more direct and clearer (if not forceful) statement about a Rosetta Code solution having to be on the Rosetta Code site. I don't like to enter another site and having to worry about what that site is or may be doing to my session, and that includes "harmless" cookies. It's a slippery slope, and steep. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 22:55, 11 February 2020 (UTC)
== Promote to Task ==
This draft task has several implementations, and clear specifications. Recommend upgrading to a task.
--[[User:DavidFashion|DavidFashion]] ([[User talk:DavidFashion|talk]]) 22:40, 11 February 2020 (UTC)
| |||