1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
|
Return-Path: <obnam-support-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
by pieni.net (Postfix) with ESMTPS id B29C840297
for <distix@pieni.net>; Thu, 3 Aug 2017 11:17:59 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
by yaffle.pepperfish.net (Postfix) with ESMTP id 2F26041737;
Thu, 3 Aug 2017 12:17:59 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1ddE8d-00032T-5N; Thu, 03 Aug 2017 12:17:59 +0100
Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
id 1ddE8c-00032G-3C
for <obnam-support@obnam.org>; Thu, 03 Aug 2017 12:17:58 +0100
Received: from avasout07.plus.net ([84.93.230.235])
by mx3.pepperfish.net with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128)
(Exim 4.89) (envelope-from <boudiccas@skimble.plus.com>)
id 1ddE8Y-0001yp-M2
for obnam-support@obnam.org; Thu, 03 Aug 2017 12:17:58 +0100
Received: from London.london ([31.185.147.16]) by avasout07 with smtp
id sbHl1v0070MTadK01bHmsk; Thu, 03 Aug 2017 12:17:46 +0100
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.2 cv=CrLPSjwD c=1 sm=1 tr=0
a=ljAp/NMcg50riqJ2O12TGw==:117 a=ljAp/NMcg50riqJ2O12TGw==:17 a=I7GaCn8XAAAA:8
a=L_ukxX83AAAA:8 a=LlzXLoV6AAAA:8 a=iI7HsYTVAAAA:8 a=bAHfVwKlAAAA:8
a=fVMChspewakBUb0vd_AA:9 a=rz29lDPWmXG_TEs3:21 a=G6jOf2WipQisRhAS:21
a=KHhItjxdNSoA:10 a=4XQGLAyZJPL5xXjmCU8A:9 a=ONNS8QRKHyMA:10
a=MqHOEnJRy3ywZKdsp40R:22 a=fpVuLz-ZQmFK_HtBcPKU:22 a=diwpeB1DDhFXqWA7J4Up:22
a=KxyM1Xthmv57RbWRIpnN:22 a=fjrkRJ71zQ2jzMzczd-K:22
X-AUTH: skimble@:2500
From: Sharon Kimble <boudiccas@skimble.plus.com>
To: obnam-support@obnam.org
Date: Thu, 03 Aug 2017 12:17:44 +0100
Message-ID: <87poccgasn.fsf@skimble.plus.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
X-Pepperfish-Transaction: 9eda-9652-9158-cf99
X-Spam-Score: -3.4
X-Spam-Score-int: -33
X-Spam-Bar: ---
X-Scanned-By: pepperfish.net, Thu, 03 Aug 2017 12:17:58 +0100
X-Spam-Report: Content analysis details: (-3.4 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.3 PPF_FROM_UK RBL: A Received line involves an address from the UK
[31.185.147.16 listed in gb.country.dnsbl.rjek.com]
-0.5 PPF_USER_AGENT User-Agent: exists
-0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
[84.93.230.235 listed in wl.mailspike.net]
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust [84.93.230.235 listed in list.dnswl.org]
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
X-ACL-Warn: message may be spam
X-Scan-Signature: ba526989c802b3f197cd2fc106aa2555
Subject: using obnam on a synology server
X-BeenThere: obnam-support@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam backup software discussion <obnam-support-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
List-Post: <mailto:obnam-support@obnam.org>
List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3118299784841322266=="
Mime-version: 1.0
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org
--===============3118299784841322266==
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha512; protocol="application/pgp-signature"
--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I've recently acquired a synology box and have spent a long time getting
it set up so that I can backup using obnam to it. Currently, I can back
up to it, and restore from it, but - with each operation it =3Dalways=3D
asks for my ssh keyphrase, and I haven't found any way round it as yet.
This is my obnam conf file for it -
=2D-8<---------------cut here---------------start------------->8---
[config]
# repository =3D sftp://boztu@192.168.1.108/NetBackup/obnam
repository =3D sftp://boztu@192.168.1.108/homes/boztu/obnam
root =3D /home/boudiccas/kindle5
client-name =3D London
# ssh =3D boxname
# compress-with =3D gzip
keep =3D 14d,5w,6m
lru-size=3D1024
upload-queue-size=3D512
#upload-queue-size=3D4096
chunk-size=3D67108864
checkpoint=3D8G
log =3D /home/boudiccas/logs/obsyn.txt
log-level =3D info
log-keep =3D 5
log-max =3D 25 mb
log-mode =3D 0600
=2D-8<---------------cut here---------------end--------------->8---
This is my bash script to run it -
=2D-8<---------------cut here---------------start------------->8---
#!/bin/bash
#: Title : obsync
#: Date : 03 August 2017
#: Author : Sharon Kimble
#: Version : 1.0
#: Description : script to help in running obnam for backups to a synolog=
y box
#: License : GNU GPL 3.0 or later
####################################################
# How to use.
# Change the lines in the '#Variables' section to fit your situation and yo=
ur file tree. And save it in ~/bin/notify, and then run 'chmod +x ~/bin/not=
ify' to make it executable.
# Then put an entry for it in your crontab, this is mine -
# 00 */2 * * * DISPLAY=3D:0 /home/boudiccas/bin/obmusic #backup /home and l=
et it run every 2 hours for backups.
####################################################
# Variables
logfile=3D"/home/boudiccas/logs/ob-sync.txt"
obsyn=3D"/home/boudiccas/cron/conf/obsyn.conf"
# obsynology=3D"sftp://boztu@192.168.1.108/NetBackup/obnam"
####################################################
/usr/bin/notify-send "Starting obnam-synology backup..."
=20
exec > >(tee -a $logfile) 2>&1
obnam --config=3D"$obsyn" backup
if [ "$?" -ne 0 ]; then
notify-send "Unable to finish obnam-synology backup."
exit 1
else
=20=20
# du -sh "$obsynology"
=20=20=20=20
echo 'Sending Backup report : Backup to obnam-synology completed', "$(date =
-R)" 'logged to' "$logfile"
echo '####################################'
notify-send "Finished obnam-synology backup."
fi
=2D-8<---------------cut here---------------end--------------->8---
There is a lot of stuff commented out in both scripts from where I've
tried various things, which have been left in to show what doesn't work.
I have generated a new key-pair in ssh, and saved the public key to
./ssh on the synology box but its failing to recognise that and asking
at every command for my keyphrase.
On the box itself I have the following setup -
=2D-8<---------------cut here---------------start------------->8---
=2D boxname
| - homes=20
| - admin
| - boztu
| - obnam
| - .ssh
| authorised_keys
=2D-8<---------------cut here---------------end--------------->8---
I have tried following these pages [1], [2], [3] and [4], but they don't
seem to affect running obnam at all as I keep being asked for my
passphrase.
So can any kind soul please help me out with not being asked for my
passphrase as part of a bash script or obnam conf please?
Thanks
Sharon.
[1] https://www.chainsawonatireswing.com/2012/01/15/ssh-into-your-synology-=
diskstation-with-ssh-keys/?from=3D@
[2] http://www.chainsawonatireswing.com/2012/01/16/log-in-to-a-synology-dis=
kstation-using-ssh-keys-as-a-user-other-than-root/
[3] http://www.chainsawonatireswing.com/2012/01/17/change-the-ssh-port-you-=
use-to-log-in-to-a-synology-diskstation/
[4] http://www.chainsawonatireswing.com/2012/01/22/log-in-to-a-synology-dis=
kstation-quicker-easier-using-an-ssh-config-file/
=2D-=20
A taste of linux =3D http://www.sharons.org.uk
TGmeds =3D http://www.tgmeds.org.uk
DrugFacts =3D https://www.drugfacts.org.uk=20=20
Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.0.9
--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAlmDBlgACgkQNoGAGQr4
g1u6HQ/9EkPCB9Lk5icY7PHl4SKA73WOSXFxC49Y2Bu3x6Usfg67CuQMzOs077sX
e6LUFnCzREvBZIKOO92ETgaNsW1tZnkI1sAmtPZiqvvrdNNENJLHf3+GNKgZd1+m
Ou+DLnrlRLMW38ERIrUy10jM9aLi8kFIIk4anUofLLVHh/FcUEJbj/7ZNDf2vKpH
GVR2Kc4Y0NUw3xMvL+65Dp8luGt6VcISITvuWqzcNfBfZ04mTrOhj8UH5UL89ZZU
QladPYs714QZwHUorHqvQaBPFFrPLYgSWpsCSDVjZwmaMMrJZyDkhaweOuAU4yDS
y4GJO3I/lXjQxiR2SoYQLHa7RFLdy+elfkXFX+/VtrN0Zan3NTw6SuXqIlTEBeAC
FPHqpEu6xy4IF1du9YT3f6PeYYFwKxNDfZYKn+FSRq6vzuxBl772rElc3ljSsAIs
MYJE+E3ohke9wGxzGLHljjHrx3IL/9zQfLe8eZJp2aPnXFQz98q9Dg1ScuYSAiJH
C/1c7CaTHt/d9yOPblxueMH/FnbYl8QAsu6QlV7P7WepeCAjEUkjh+CjRKcNQ6vZ
du0DOXyNB//uN8V59pJRRml8V7ndw4nwbL7gIERU9ko4zH67kIqoyZieRKLzDb7Y
83kqeuL56lyrnf2/Nfg5rxhQ9jX/tsTHYGKPtOiediKQ21KkyCY=
=qPTj
-----END PGP SIGNATURE-----
--=-=-=--
--===============3118299784841322266==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
obnam-support mailing list
obnam-support@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
--===============3118299784841322266==--
|
