view pixmaps/quest.xpm @ 32719:185f2a160d5d v9.0.1682

patch 9.0.1682: sodium encryption is not portable Commit: https://github.com/vim/vim/commit/6019fed0c50a31f0f9bb6c80e4e2b97d3f71565a Author: Christian Brabandt <cb@256bit.org> Date: Tue Jul 11 22:38:29 2023 +0200 patch 9.0.1682: sodium encryption is not portable Problem: crypt: sodium encryption is not portable Solution: use little-endian byte order for sodium encrypted files As mentioned in #12586, sodium encryption only works on little ending architectures, because reading and writing the sodium encryption parameters are stored in the encrypted files in an arch-dependent way. This of course fails for big-endian architectures like s390. So make sure to use little-endian byte order when reading and writing sodium encrypted files. fixes: #12586 closes: 12655
author Christian Brabandt <cb@256bit.org>
date Wed, 09 Aug 2023 21:45:03 +0200
parents 3fc0f57ecb91
children
line wrap: on
line source

/* XPM */
static char * quest_xpm[] = {
/* width height ncolors cpp [x_hot y_hot] */
"34 34 4 1 0 0",
/* colors */
" 	s none	m none	c none",
".	s bottomShadowColor	m black	c #5D6069",
"X	s iconColor2	m white	c #FFFFFF",
"o	s iconColor1	m black	c #000000",
/* pixels */
"                                  ",
"            ........              ",
"         ...XXXXXXXX...           ",
"       ..XXXXXXXXXXXXXX..         ",
"      .XXXXXXXXXXXXXXXXXX.        ",
"     .XXXXXXXXoooooXXXXXXXo       ",
"    .XXXXXXXXoXXXXooXXXXXXXo      ",
"   .XXXXXXXXoooXXXXooXXXXXXXo     ",
"  .XXXXXXXXXooooXXXooXXXXXXXXo    ",
"  .XXXXXXXXXXooXXXoooXXXXXXXXo.   ",
" .XXXXXXXXXXXXXXXooooXXXXXXXXXo.  ",
" .XXXXXXXXXXXXXXooooXXXXXXXXXXo.  ",
" .XXXXXXXXXXXXXoooooXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoooXXXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXooXXXXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoXXXXXXXXXXXXXXXo.. ",
"  .XXXXXXXXXXXoXXXXXXXXXXXXXXo... ",
"  .XXXXXXXXXXXXXXXXXXXXXXXXXXo... ",
"   .XXXXXXXXXXooXXXXXXXXXXXXo...  ",
"    oXXXXXXXXooooXXXXXXXXXXo....  ",
"     oXXXXXXXXooXXXXXXXXXXo....   ",
"      oXXXXXXXXXXXXXXXXXXo....    ",
"       ooXXXXXXXXXXXXXXoo....     ",
"        .oooXXXXXXXXooo.....      ",
"         ...oooXXXXo.......       ",
"           ....oXXXo.....         ",
"              .oXXXo..            ",
"                oXXo..            ",
"                 oXo..            ",
"                  oo..            ",
"                   ...            ",
"                    ..            ",
"                                  "};