Aduke.1675
net.games.rogue
utzoo!decvax!duke!cjp
Mon Jan 25 18:47:24 1982
Re: we13.131: Rogue.save
There is no "rogue.save header".  The save process works
(I hope I'm not giving away classified information) by
writing out to disk the entire data space of the program
(encrypted of course) including a stat of the file it is
being saved in.  So you'd have to know the encryption key
as well as the relative location of the inum data.  Which
probably changes, depending on how many mallocs have been
done.  Sorry.
At least rogue gives you a choice of where you want to save
the file.  Just be sure it's where you want to leave it.
(I don't know how to help people on systems with automatic
inum scrambling.  Not checking it would be a big security hole,
but not being able to save and restore is much worse.)