84685f24c9
Ssh.hostKeys now also installs any available SshEd25519 keys.
2015-01-04 15:59:54 -04:00
f1a1d0001a
sshPubKey is renamed to Ssh.pubKey, and has an added SshKeyType parameter.
2015-01-04 15:57:27 -04:00
52664e6220
sshPubKey is renamed to Ssh.pubKey
2015-01-04 15:36:53 -04:00
0f41071cb5
transition docs
2015-01-04 15:22:22 -04:00
ad984e74e4
propellor spin
2015-01-04 15:00:40 -04:00
bb7b8e7891
add $INCLUDE of pubkeys before zone file is written, to avoid pogoing
2015-01-04 14:22:44 -04:00
43e15c8add
fix serial incrementing
2015-01-04 14:17:33 -04:00
f36443755e
propellor spin
2015-01-04 14:05:42 -04:00
8c1006c654
propellor spin
2015-01-04 13:56:55 -04:00
ce7f14b9b3
propellor spin
2015-01-04 13:52:59 -04:00
bf34d6f423
propellor spin
2015-01-04 13:42:01 -04:00
e67901a77b
use separate directory for dnssec files
2015-01-04 13:22:23 -04:00
d6c8ddb955
resign zone if keys change
2015-01-04 13:13:06 -04:00
8172f243d7
DNS WIP
2015-01-04 12:44:05 -04:00
a1f61e09b8
stub signedPrimary
2015-01-03 19:10:28 -04:00
4dd6596919
add DnsSec module
2015-01-03 19:10:17 -04:00
932cb7c5d6
add hasPrivContentFrom
2015-01-03 19:07:59 -04:00
d5cfadd899
Detect #774376 and refuse to use docker if the system is so broken that docker exec doesn't enter a chroot.
2015-01-01 15:41:31 -04:00
858ded043b
more cruft from new image
2015-01-01 15:15:44 -04:00
c7aac0b35e
remove screen workaround
...
Turns out elephant's oldusenet shellbox docker instance somehow had a
non-setguid screen binary. Dunno how; reinstall fixed it.
2014-12-23 15:45:35 -04:00
35ccb0fac6
fix screen dir mode
2014-12-23 15:29:23 -04:00
a48f5916e1
propellor spin
2014-12-23 14:22:50 -04:00
b8be8c244e
propellor spin
2014-12-22 17:16:52 -04:00
26a4c164e4
gitriddance
2014-12-22 15:05:05 -04:00
dc36a98fc1
Revert ensureProperty warning message, too many false positives in places where Info is correctly propigated. Better approach needed.
2014-12-21 21:33:03 -04:00
d194765e10
propellor spin
2014-12-21 21:14:11 -04:00
23399416f1
broke up big function to describe PrivDataField
2014-12-14 16:14:05 -04:00
71723ca09f
support for crypted passwords in privdata
...
* Added CryptPassword to PrivDataField, for password hashes as produced
by crypt(3).
* User.hasPassword and User.hasSomePassword will now use either
a CryptPassword or a Password from privdata, depending on which is set.
2014-12-14 15:24:10 -04:00
2e2438ae66
improve haddock formating of filenames
2014-12-09 14:22:37 -04:00
b22201e36b
Fix Apache.siteEnabled to update the config file and reload apache when configuration has changed.
2014-12-09 00:34:24 -04:00
f8943c2036
fix a case where fileProperty reported a change despite not making one
...
The problem occurred because two lists of lines of the file can be
different, while representing the same file content. For example:
["foo", "bar"]
["foo\nbar"]
2014-12-09 00:30:04 -04:00
834a05e25a
refactor
2014-12-08 01:22:29 -04:00
06975ec5e1
another place to use toResult
2014-12-08 01:12:55 -04:00
3c7219874b
finished accidentially committed bit
2014-12-08 01:07:31 -04:00
4e9b01a8a7
propellor spin
...
(cherry picked from commit 1d02d589c7
2014-12-08 01:07:25 -04:00
2fe0b28982
more uses for hostContext
2014-12-07 15:21:55 -04:00
089b7131a6
caution
2014-12-07 15:13:28 -04:00
9ca332e481
Fixed privdata introspection for User.hasPassword and User.hasSomePassword
...
This is not a complete fix for the problem that Info doen't propigate
from the called property when code does something like:
do
hostname <- asks hostName
ensureProperty $ foo hostname
Instead, I just eliminated the need to implement hasPassword that way,
by making the PrivData Info use a HostContext which automatically
gets the right hostname passed to it.
All other uses of withPrivData don't have the problem. It's still possible
for the user to run into the problem if they write something like the
above, where foo is a property that uses privdata. However, all properties
that take a Context now also accept a HostContext, so it's at least less
likely the user needs to write that.
2014-12-07 15:03:06 -04:00
8c12047b6b
simplify using makeChange
2014-12-07 14:49:12 -04:00
6a906c8a4c
typo
2014-12-07 12:50:40 -04:00
52a83a8911
enable shadow passwords
...
I have seen weird almost boot failures when they're disabled, including a
segfault.
2014-12-06 15:39:02 -04:00
7983046cd5
update
2014-12-06 15:28:30 -04:00
bdbf787e2c
keep and use Reboot.now
2014-12-06 13:32:53 -04:00
29442f222e
Reboot.atEnd
2014-12-06 13:21:19 -04:00
62697c7b7f
reboot at end of propellor run when clean os has been installed
2014-12-06 06:41:21 -04:00
a7e71faaaa
forgot to add new Mount lib
2014-12-05 17:54:29 -04:00
5ae6a302df
some comments
2014-12-05 17:44:09 -04:00
00ab240164
fix install of debootstrap from source
2014-12-05 16:48:52 -04:00
527975dffe
hasSomePassword and hasPassword now check to make sure shadow passwords are enabled.
2014-12-05 16:33:23 -04:00
bf9284d05c
I have now successfully used propellor to convert a Fedora system into a bootable and fully working Debian system
2014-12-05 16:22:11 -04:00
Joey Hess
Joey Hess