3
auth=0c1295085dca124e6ba5a3cea7993c22
4
account=9f04221fe44762047894adeb96ffd069
5
session=2e9a42f2a3b6573891ff9e6bf0c31c9e
6
password=4cf59ec48caad2a06ea2e183d8bc007a
9
if dpkg --compare-versions "$2" lt-nl 53-1ubuntu6; then
10
# If we're upgrading from an older ecryptfs-utils,
11
# and the pam configuration precisely matches that
12
# which was written by auth-client-config, we can
13
# safely force the pam-auth-update.
15
for type in auth account session password
17
sum="$(md5sum /etc/pam.d/common-$type 2>/dev/null | awk '{ print $1 }')"
18
[ "$sum" = "$(eval echo \$$type)" ] || force=
21
pam-auth-update --package $force
32
# Basically, if a user chooses to encrypt their entire home
33
# directory, we're going to need someplace to put their
34
# ~/.ecryptfs directory that's available prior to mounting their
35
# home directory. Classic chicken/egg bootstrapping.
37
if [ ! -d /var/lib/ecryptfs ]
39
mkdir -p /var/lib/ecryptfs
40
chmod 1777 /var/lib/ecryptfs
44
abort-upgrade|abort-remove|abort-deconfigure)
49
echo "postinst called with unknown argument \`{$1}'" >&2