Revision as of 06:18, 9 December 2015 edit L235 (talk \| contribs) Edit filter managers, Autopatrolled, Checkusers, Interface administrators, Oversighters, Administrators 27,992 edits done; add {{copied}} ← Previous edit		Revision as of 05:27, 9 May 2016 edit undo Psycho Chicken (talk \| contribs) 55 edits →Securing Local Data: new section Next edit →
Line 62: I am [[WP:BOLD\|BOLDly]] implementing the proposed merge of [[Reciprocal cipher]] into this page ([[Symmetric-key algorithm]]) from [[Special:Diff/470191675\|January 2012]], having seen no objection under [[WP:MERGECLOSE]]. Please feel free to reopen discussion on this if you think that's needed. Thanks, '''[[User:L235\|L235]]''' ([[User talk:L235#top\|t]] / [[Special:Contribs/L235\|c]] / [[User:L235/siginfo\|<small>ping in reply</small>]]) 06:11, 9 December 2015 (UTC) :Done. '''[[User:L235\|L235]]''' ([[User talk:L235#top\|t]] / [[Special:Contribs/L235\|c]] / [[User:L235/siginfo\|<small>ping in reply</small>]]) 06:17, 9 December 2015 (UTC) == Securing Local Data == While the article on asymmetric or public key cryptography lays an emphasis on securing communication channels, here, you also talk about sharing keys. I am missing information which allows to classify and qualify encryption systems for use on locally stored data. Currently there is no easy way to deduce that symmetric algorithms should be preferable in such a context. TIA --[[User:Psycho Chicken\|Psycho Chicken]] ([[User talk:Psycho Chicken\|talk]]) 05:27, 9 May 2016 (UTC)

Talk:Symmetric-key algorithm: Difference between revisions