burp-users Mailing List for burp backup and restore program
Brought to you by:
grke
You can subscribe to this list here.
2011 |
Jan
(2) |
Feb
(13) |
Mar
(27) |
Apr
(12) |
May
(15) |
Jun
(58) |
Jul
(67) |
Aug
(19) |
Sep
(53) |
Oct
(2) |
Nov
(46) |
Dec
(22) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
(34) |
Feb
(21) |
Mar
(49) |
Apr
(28) |
May
(67) |
Jun
(92) |
Jul
(32) |
Aug
(16) |
Sep
(21) |
Oct
(70) |
Nov
(13) |
Dec
(28) |
2013 |
Jan
(100) |
Feb
(32) |
Mar
(21) |
Apr
(90) |
May
(69) |
Jun
(67) |
Jul
(63) |
Aug
(29) |
Sep
(42) |
Oct
(47) |
Nov
(39) |
Dec
(30) |
2014 |
Jan
(41) |
Feb
(13) |
Mar
(6) |
Apr
(21) |
May
(48) |
Jun
(75) |
Jul
(52) |
Aug
(49) |
Sep
(45) |
Oct
(58) |
Nov
(44) |
Dec
(72) |
2015 |
Jan
(68) |
Feb
(73) |
Mar
(288) |
Apr
(191) |
May
(124) |
Jun
(70) |
Jul
(88) |
Aug
(86) |
Sep
(71) |
Oct
(123) |
Nov
(103) |
Dec
(74) |
2016 |
Jan
(76) |
Feb
(60) |
Mar
(66) |
Apr
(77) |
May
(113) |
Jun
(81) |
Jul
(77) |
Aug
(91) |
Sep
(116) |
Oct
(126) |
Nov
(57) |
Dec
(49) |
2017 |
Jan
(36) |
Feb
(48) |
Mar
(69) |
Apr
(55) |
May
(84) |
Jun
(41) |
Jul
(45) |
Aug
(44) |
Sep
(93) |
Oct
(57) |
Nov
(56) |
Dec
(12) |
2018 |
Jan
(76) |
Feb
(46) |
Mar
(29) |
Apr
(28) |
May
(30) |
Jun
(48) |
Jul
(32) |
Aug
(78) |
Sep
(60) |
Oct
(34) |
Nov
(6) |
Dec
(17) |
2019 |
Jan
(6) |
Feb
(77) |
Mar
(12) |
Apr
(5) |
May
(9) |
Jun
(11) |
Jul
(16) |
Aug
(18) |
Sep
(5) |
Oct
(9) |
Nov
(13) |
Dec
(23) |
2020 |
Jan
(20) |
Feb
(36) |
Mar
(52) |
Apr
(38) |
May
(26) |
Jun
(3) |
Jul
(16) |
Aug
(18) |
Sep
(13) |
Oct
(12) |
Nov
(12) |
Dec
(12) |
2021 |
Jan
(10) |
Feb
(21) |
Mar
(15) |
Apr
(16) |
May
(13) |
Jun
(2) |
Jul
(6) |
Aug
(30) |
Sep
(16) |
Oct
(4) |
Nov
(4) |
Dec
(23) |
2022 |
Jan
|
Feb
(2) |
Mar
(14) |
Apr
(10) |
May
(4) |
Jun
(7) |
Jul
(5) |
Aug
(1) |
Sep
(15) |
Oct
(28) |
Nov
(7) |
Dec
(8) |
2023 |
Jan
(23) |
Feb
(24) |
Mar
(3) |
Apr
(9) |
May
(27) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(11) |
Oct
(8) |
Nov
|
Dec
(13) |
2024 |
Jan
(5) |
Feb
(16) |
Mar
|
Apr
(7) |
May
(23) |
Jun
(1) |
Jul
|
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(1) |
2025 |
Jan
|
Feb
|
Mar
(8) |
Apr
|
May
(7) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Henrik S. <hb...@in...> - 2025-06-19 11:14:56
|
That helped. Thanks Peter! Am 19.06.2025 um 12:51 schrieb Peter Ruegg: > Hi Henrik > > On 19/06/2025 10:02, Henrik Schmidt via Burp-users wrote: >> The client ends up with size 0 files ssl_cert_ca.pem and ssl_cert- >> client.pem. >> and the server is stuck with the pem file in the /newcerts folder. > > We had the same problem after doing upgrades. IIRC this happens when > the Server CA doesn't work correctly. In our case this was due to a > line in /etc/burp/CA.cnf that contained a parameter RANDFILE. This > is not needed anymore and can simply be removed. Maybe that helps? > > Regards > |
From: Peter R. <pet...@vs...> - 2025-06-19 11:06:13
|
Hi Henrik On 19/06/2025 10:02, Henrik Schmidt via Burp-users wrote: > The client ends up with size 0 files ssl_cert_ca.pem and ssl_cert- > client.pem. > and the server is stuck with the pem file in the /newcerts folder. We had the same problem after doing upgrades. IIRC this happens when the Server CA doesn't work correctly. In our case this was due to a line in /etc/burp/CA.cnf that contained a parameter RANDFILE. This is not needed anymore and can simply be removed. Maybe that helps? Regards -- Peter H. Ruegg DevOps VSHN AG | Neugasse 10 | CH-8005 Zurich T: +41 44 545 53 00 | https://vshn.ch |
From: Henrik S. <hb...@in...> - 2025-06-19 08:20:14
|
Hi, I have problems getting burp to work with a new client. Both server & client are running 3.1.4 on Ubuntu Linux. The cert data transfer seems to fail but I have no clue why. The client ends up with size 0 files ssl_cert_ca.pem and ssl_cert-client.pem. and the server is stuck with the pem file in the /newcerts folder. Any help is appreciated. Regards, Henrik root@client_name:/etc/burp# burp -v -a l 2025-06-19 09:48:04 +0200: burp[14698] Could not find ssl_cert /etc/burp/ssl_cert-client.pem: No such file or directory 2025-06-19 09:48:04 +0200: burp[14698] Could not find ssl_key /etc/burp/ssl_cert-client.key: No such file or directory 2025-06-19 09:48:04 +0200: burp[14698] Could not find ssl_cert_ca /etc/burp/ssl_cert_ca.pem: No such file or directory 2025-06-19 09:48:04 +0200: burp[14698] Connecting to server_name:4971 2025-06-19 09:48:04 +0200: burp[14698] auth ok 2025-06-19 09:48:04 +0200: burp[14698] Server version: 3.1.4 2025-06-19 09:48:04 +0200: burp[14698] Server will sign a certificate request 2025-06-19 09:48:04 +0200: burp[14698] Generating SSL key and certificate signing request 2025-06-19 09:48:04 +0200: burp[14698] Running '/usr/sbin/burp_ca --key --keypath /etc/burp/ssl_cert-client.key --request --requestpath /etc/burp/CA-client/client_name.csr --name client_name' generating key lagune: /etc/burp/ssl_cert-client.key generating request client_name 2025-06-19 09:48:04 +0200: burp[14698] /usr/sbin/burp_ca returned: 0 2025-06-19 09:48:04 +0200: burp[14698] Sent /etc/burp/CA-client/client_name.csr 2025-06-19 09:48:04 +0200: burp[14698] main socket 3: Peer closed SSL session 2025-06-19 09:48:04 +0200: burp[14698] transfer file returning: -1 2025-06-19 09:48:04 +0200: burp[14698] Received: /etc/burp/ssl_cert-client.pem.14698 2025-06-19 09:48:04 +0200: burp[14698] main socket 3: Peer closed SSL session 2025-06-19 09:48:04 +0200: burp[14698] transfer file returning: -1 2025-06-19 09:48:04 +0200: burp[14698] Received: /etc/burp/ssl_cert_ca.pem.14698 2025-06-19 09:48:04 +0200: burp[14698] Re-opening connection to server_name:4971 2025-06-19 09:48:09 +0200: burp[14698] Can't read ssl_cert: /etc/burp/ssl_cert-client.pem 8025CC8AAD7F0000:error:0480006C:PEM routines:get_name:no start line:../crypto/pem/pem_lib.c:763:Expecting: TRUSTED CERTIFICATE 8025CC8AAD7F0000:error:0A080009:SSL routines:use_certificate_chain_file:PEM lib:../ssl/ssl_rsa.c:459: 2025-06-19 09:48:09 +0200: burp[14698] error initialising ssl ctx |
From: Mark S. <ma...@st...> - 2025-05-29 07:40:40
|
On Thu, 2025-05-29 at 07:37 +1000, gr...@gr... wrote: > Hello, > > If all the child processes are exited, then it sounds like a memory > leak. > What version is the burp server? 3.1.4, as are the clients. I'm running under Fedora (42) (both server and clients). I hope this is the latest Mark |
From: <gr...@gr...> - 2025-05-28 21:53:57
|
On Wed, May 28, 2025 at 11:22:00AM +0100, Mark Stanton wrote: > Thanks for that Norbert. > > Both child processes are listed as exited (the last one six hours ago) > and I can't see any "finishing" links, but I do see the memory usage > gone down a little since I wrote my initial message so I'll do as you > suggest and just watch. > > It's a small office setup so my server having 8Gb, whilst tiny, is > generally ok. And in truth I'm not particularly seeing a server speed > problem. > > Thanks again > Mark > > On Wed, 2025-05-28 at 11:32 +0200, burp--- via Burp-users wrote: > > It is the cleanup process after the backup, what makes deduplication > > and remove old backups for example. It is running a while, leave it > > to run.... > > If that is the case, you see "finishing" symlinks in the backup > > folders. > > Otherwise, 5GB is not much (but it is depending on the data size), > > in my backup servers has 256GB ram, 128GB was nearly narrow in a few > > case. > > > > Regards > > Norbert > > 28.05.25 10:53, Mark Stanton: > > > > > My nightly backups have finished successfully without error and the > > > Burp server now has just one process running, presumably waiting > > > for > > > clients to call. However, the machine is showing 4.76Gb of memory > > > still allocated to Burp. This is more than 50% of the memory on > > > the > > > machine, which seems to me to be a problem. > > > > > > If I restart Burp it shows a very small amount of memory allocated > > > so > > > presumably all those gigabytes should have been given back? Is > > > there a > > > configuration change I can make to reduce this "idle load"? > > > > > > TIA > > > Mark Hello, If all the child processes are exited, then it sounds like a memory leak. What version is the burp server? |
From: Mark S. <ma...@st...> - 2025-05-28 10:58:27
|
Thanks for that Norbert. Both child processes are listed as exited (the last one six hours ago) and I can't see any "finishing" links, but I do see the memory usage gone down a little since I wrote my initial message so I'll do as you suggest and just watch. It's a small office setup so my server having 8Gb, whilst tiny, is generally ok. And in truth I'm not particularly seeing a server speed problem. Thanks again Mark On Wed, 2025-05-28 at 11:32 +0200, burp--- via Burp-users wrote: > It is the cleanup process after the backup, what makes deduplication > and remove old backups for example. It is running a while, leave it > to run.... > If that is the case, you see "finishing" symlinks in the backup > folders. > Otherwise, 5GB is not much (but it is depending on the data size), > in my backup servers has 256GB ram, 128GB was nearly narrow in a few > case. > > Regards > Norbert > 28.05.25 10:53, Mark Stanton: > > > My nightly backups have finished successfully without error and the > > Burp server now has just one process running, presumably waiting > > for > > clients to call. However, the machine is showing 4.76Gb of memory > > still allocated to Burp. This is more than 50% of the memory on > > the > > machine, which seems to me to be a problem. > > > > If I restart Burp it shows a very small amount of memory allocated > > so > > presumably all those gigabytes should have been given back? Is > > there a > > configuration change I can make to reduce this "idle load"? > > > > TIA > > Mark > > > > _______________________________________________ > > Burp-users mailing list > > Bur...@li... > > https://lists.sourceforge.net/lists/listinfo/burp-users |
From: <bu...@on...> - 2025-05-28 09:32:32
|
It is the cleanup process after the backup, what makes deduplication and remove old backups for example. It is running a while, leave it to run.... If that is the case, you see "finishing" symlinks in the backup folders. Otherwise, 5GB is not much (but it is depending on the data size), in my backup servers has 256GB ram, 128GB was nearly narrow in a few case. Regards Norbert 28.05.25 10:53, Mark Stanton: > My nightly backups have finished successfully without error and the > Burp server now has just one process running, presumably waiting for > clients to call. However, the machine is showing 4.76Gb of memory > still allocated to Burp. This is more than 50% of the memory on the > machine, which seems to me to be a problem. > > If I restart Burp it shows a very small amount of memory allocated so > presumably all those gigabytes should have been given back? Is there a > configuration change I can make to reduce this "idle load"? > > TIA > Mark > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users |
From: Mark S. <ma...@st...> - 2025-05-28 09:10:02
|
My nightly backups have finished successfully without error and the Burp server now has just one process running, presumably waiting for clients to call. However, the machine is showing 4.76Gb of memory still allocated to Burp. This is more than 50% of the memory on the machine, which seems to me to be a problem. If I restart Burp it shows a very small amount of memory allocated so presumably all those gigabytes should have been given back? Is there a configuration change I can make to reduce this "idle load"? TIA Mark |
From: Benedikt H. <tic...@gm...> - 2025-05-06 16:59:54
|
I resorted to putting the server name in the mail's subject line as our system here replaces all header lines (except the reply-to) with the gateway sender name. burp--- via Burp-users <bur...@li...> schrieb am Di., 6. Mai 2025, 07:56: > Hi! > > I small but useful feature is missing for me. > I use burp with multiple server, referenced az backup.company.com domain > in the clients config. This providing some load balancing based on how DNS > works. > For me be very useful, if there will be a "Server name" in the reply > header above or after Server version after connecting the client. > > Can you change this little modification? > > Regards, > Norbert > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users > |
From: <bu...@on...> - 2025-05-06 05:55:25
|
Hi! I small but useful feature is missing for me. I use burp with multiple server, referenced az backup.company.com domain in the clients config. This providing some load balancing based on how DNS works. For me be very useful, if there will be a "Server name" in the reply header above or after Server version after connecting the client. Can you change this little modification? Regards, Norbert |
From: Thomas C. <th...@op...> - 2025-03-27 07:06:32
|
The client server version are already in the log. That's how I found out. Regards On 26 March 2025 21:41:17 CET, John Stoffel <jo...@st...> wrote: >>>>>> "Graham" == Graham Keeling <gr...@gr...> writes: > >> Great! Thank you for updating, I was out of ideas. > >I also want to thank you Graham for building burp, it saved my data >earlier today and I'm really happy. > >But maybe the next version needs to have a better client/server >protocol with some versioning information when connecting? Just so >you can see something like: > > burp client v3.2.x connecting to server v2.1.0 > >in the log messages. This might make debugging easier in the future. > >John > > >_______________________________________________ >Burp-users mailing list >Bur...@li... >https://lists.sourceforge.net/lists/listinfo/burp-users Thomas Constans openDoor sent from phone, excuse brevity |
From: <bu...@on...> - 2025-03-27 06:30:16
|
Hi, Regarding to this, for me might be useful if also print the server ip address where client connected is, rhen need to debug or simply check something. I refer my server with DNS names in the config, and more IP behind this name. Thanks, Norbert 26.03.25 21:41, John Stoffel: >>>>>> "Graham" == Graham Keeling<gr...@gr...> writes: >> Great! Thank you for updating, I was out of ideas. > I also want to thank you Graham for building burp, it saved my data > earlier today and I'm really happy. > > But maybe the next version needs to have a better client/server > protocol with some versioning information when connecting? Just so > you can see something like: > > burp client v3.2.x connecting to server v2.1.0 > > in the log messages. This might make debugging easier in the future. > > John > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users |
From: John S. <jo...@st...> - 2025-03-26 20:59:37
|
>>>>> "Graham" == Graham Keeling <gr...@gr...> writes: > Great! Thank you for updating, I was out of ideas. I also want to thank you Graham for building burp, it saved my data earlier today and I'm really happy. But maybe the next version needs to have a better client/server protocol with some versioning information when connecting? Just so you can see something like: burp client v3.2.x connecting to server v2.1.0 in the log messages. This might make debugging easier in the future. John |
From: Graham K. <gr...@gr...> - 2025-03-24 21:41:06
|
Great! Thank you for updating, I was out of ideas. On Mon, Mar 24, 2025 at 12:33:09PM +0100, Thomas Constans wrote: > Good news, > > > Errors were caused by client version issue. > > > server was using version 3.1.4 whereas i was using version 2.4 > > > I ve been able to access backup using a 3.1.4 client. > > > Restoring in progress ! > > Le 19/03/2025 à 22:21, gr...@gr... a écrit : > > On Wed, Mar 19, 2025 at 08:58:27AM +0100, Thomas Constans via Burp-users wrote: > > > Hello, > > > > > > > > > Trying to restore crypted burp backups from a crashed server > > > > > > > > > I have first restored (from another backup) the /etc/burp of dead server > > > > > > So i am using the same configuration files and certificates of server, > > > including the encryption_password > > > > > > > > > I have first got the error "EVP_CipherInit_ex failed" and fixed it by > > > enabling legacy algo in openssl.cnf > > > > > > > > > but now i get an error : > > > > > > > > > sudo rm -fr recupe ; sudo burp -v -c restauration.conf -a r -r /etc -d > > > recupe > > > > > > 2025-03-19 08:53:10 +0100: burp[431759] No backup specified. Using the most > > > recent. > > > 2025-03-19 08:53:10 +0100: burp[431759] Connecting to backup_serveur:4971 > > > 2025-03-19 08:53:10 +0100: burp[431759] auth ok > > > 2025-03-19 08:53:10 +0100: burp[431759] Server version: 2.4.0 > > > 2025-03-19 08:53:11 +0100: burp[431759] nocsr ok > > > 2025-03-19 08:53:11 +0100: burp[431759] SSL is using cipher: > > > TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any > > > Enc=AESGCM(256) Mac=AEAD > > > > > > 2025-03-19 08:53:11 +0100: burp[431759] extra_comms_begin ok:autoupgrade:incexc:orig_client:uname:failover:vss_restore:regex_icase:counters_json:msg:csetproto:rshash=blake2:seed: > > > 2025-03-19 08:53:11 +0100: burp[431759] Using protocol=1 > > > 2025-03-19 08:53:11 +0100: burp[431759] Doing restore 0:/etc > > > 2025-03-19 08:53:11 +0100: burp[431759] Doing restore confirmed > > > 2025-03-19 08:53:11 +0100: burp[431759] Directory: '/blah/recupe/' > > > > > > 2025-03-19 08:51:51 +0100: burp[431248] Decryption failure at the end. > > > 2025-03-19 08:51:51 +0100: burp[431248] transfer file returning: -1 > > > 2025-03-19 08:51:51 +0100: burp[431248] WARNING: Could not transfer file in: > > > /blah/recupe/etc. > > > 2025-03-19 08:51:54 +0100: burp[431248] unexpected command in > > > restore_interrupt(): c:000A:restoreend > > > 2025-03-19 08:51:54 +0100: burp[431248] restore_file error > > > > > > > > > I have the same error if i try to restore from an other machine of the same > > > OS/Version of dead server > > > > > > > > > Any help and pointer greatly appreciated. > > Hello, > > > > Sorry that you are having troubles. > > > > It seems strange that it is talking about a file with a name that looks > > like it's a directory (/etc). > > I'm wondering whether it is finding any actual files in the manifest? > > > > Does listing instead of restoring show the files that you expect? > > > > sudo burp -c restauration.conf -a l -r /etc > > > > You could also try a verify command: > > > > sudo burp -c restauration.conf -a v -r /etc > > > > Also, I am wondering whether you are trying to restore a Windows backup > > onto a linux machine (or vice versa)? Linux backups have no encrypted data to > > restore for directories, but Windows backups do. > > > > > > _______________________________________________ > > Burp-users mailing list > > Bur...@li... > > https://lists.sourceforge.net/lists/listinfo/burp-users > > > -- > Thomas Constans > Solutions informatiques libres, > locales et respectueuses de vos > données personnelles > 📞 33(0)6 23 37 87 85 > 🌐 https://opendoor.fr > 🐱 membre du collectif Chatons.org > 🐘 https://framapiaf.org/@thomasconstans > 🔑 0xBA19745F80410541 > |
From: Thomas C. <th...@op...> - 2025-03-24 11:33:31
|
Good news, Errors were caused by client version issue. server was using version 3.1.4 whereas i was using version 2.4 I ve been able to access backup using a 3.1.4 client. Restoring in progress ! Le 19/03/2025 à 22:21, gr...@gr... a écrit : > On Wed, Mar 19, 2025 at 08:58:27AM +0100, Thomas Constans via Burp-users wrote: >> Hello, >> >> >> Trying to restore crypted burp backups from a crashed server >> >> >> I have first restored (from another backup) the /etc/burp of dead server >> >> So i am using the same configuration files and certificates of server, >> including the encryption_password >> >> >> I have first got the error "EVP_CipherInit_ex failed" and fixed it by >> enabling legacy algo in openssl.cnf >> >> >> but now i get an error : >> >> >> sudo rm -fr recupe ; sudo burp -v -c restauration.conf -a r -r /etc -d >> recupe >> >> 2025-03-19 08:53:10 +0100: burp[431759] No backup specified. Using the most >> recent. >> 2025-03-19 08:53:10 +0100: burp[431759] Connecting to backup_serveur:4971 >> 2025-03-19 08:53:10 +0100: burp[431759] auth ok >> 2025-03-19 08:53:10 +0100: burp[431759] Server version: 2.4.0 >> 2025-03-19 08:53:11 +0100: burp[431759] nocsr ok >> 2025-03-19 08:53:11 +0100: burp[431759] SSL is using cipher: >> TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any >> Enc=AESGCM(256) Mac=AEAD >> >> 2025-03-19 08:53:11 +0100: burp[431759] extra_comms_begin ok:autoupgrade:incexc:orig_client:uname:failover:vss_restore:regex_icase:counters_json:msg:csetproto:rshash=blake2:seed: >> 2025-03-19 08:53:11 +0100: burp[431759] Using protocol=1 >> 2025-03-19 08:53:11 +0100: burp[431759] Doing restore 0:/etc >> 2025-03-19 08:53:11 +0100: burp[431759] Doing restore confirmed >> 2025-03-19 08:53:11 +0100: burp[431759] Directory: '/blah/recupe/' >> >> 2025-03-19 08:51:51 +0100: burp[431248] Decryption failure at the end. >> 2025-03-19 08:51:51 +0100: burp[431248] transfer file returning: -1 >> 2025-03-19 08:51:51 +0100: burp[431248] WARNING: Could not transfer file in: >> /blah/recupe/etc. >> 2025-03-19 08:51:54 +0100: burp[431248] unexpected command in >> restore_interrupt(): c:000A:restoreend >> 2025-03-19 08:51:54 +0100: burp[431248] restore_file error >> >> >> I have the same error if i try to restore from an other machine of the same >> OS/Version of dead server >> >> >> Any help and pointer greatly appreciated. > Hello, > > Sorry that you are having troubles. > > It seems strange that it is talking about a file with a name that looks > like it's a directory (/etc). > I'm wondering whether it is finding any actual files in the manifest? > > Does listing instead of restoring show the files that you expect? > > sudo burp -c restauration.conf -a l -r /etc > > You could also try a verify command: > > sudo burp -c restauration.conf -a v -r /etc > > Also, I am wondering whether you are trying to restore a Windows backup > onto a linux machine (or vice versa)? Linux backups have no encrypted data to > restore for directories, but Windows backups do. > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users > -- Thomas Constans Solutions informatiques libres, locales et respectueuses de vos données personnelles 📞 33(0)6 23 37 87 85 🌐 https://opendoor.fr 🐱 membre du collectif Chatons.org 🐘 https://framapiaf.org/@thomasconstans 🔑 0xBA19745F80410541 |
From: Tomato R. <tom...@gm...> - 2025-03-19 22:06:59
|
I have obfuscated file and directory name for privacy issue, original dead server i want to restore backup is a linux Centos 7 i am restoring on a linux CentOS 7 too to avoid any compatibility / version issue sudo burp -c restauration.conf -a l -r /etc gives me the list of files and folders in /etc of dead server sudo burp -c restauration.conf -a v -r /etc gives me a progress bar and the following results: Attempted | Expected ------------------------------ Files (encrypted): 20548 | 20548 Meta data (enc): 340 | 340 Directories: 1121 | 1121 Hard links: 4 | 4 Soft links: 242 | 242 Grand total: 22255 | 22255 ------------------------------ Messages: 0 Warnings: 0 Bytes estimated: 117358118 (111.92 MB) Bytes checked: 0 Bytes received: 4183065 (3.99 MB) Bytes sent: 891 looks like files are here, can be downloaded, but decryption fails for unknown reason |
From: <gr...@gr...> - 2025-03-19 21:39:44
|
On Wed, Mar 19, 2025 at 08:58:27AM +0100, Thomas Constans via Burp-users wrote: > Hello, > > > Trying to restore crypted burp backups from a crashed server > > > I have first restored (from another backup) the /etc/burp of dead server > > So i am using the same configuration files and certificates of server, > including the encryption_password > > > I have first got the error "EVP_CipherInit_ex failed" and fixed it by > enabling legacy algo in openssl.cnf > > > but now i get an error : > > > sudo rm -fr recupe ; sudo burp -v -c restauration.conf -a r -r /etc -d > recupe > > 2025-03-19 08:53:10 +0100: burp[431759] No backup specified. Using the most > recent. > 2025-03-19 08:53:10 +0100: burp[431759] Connecting to backup_serveur:4971 > 2025-03-19 08:53:10 +0100: burp[431759] auth ok > 2025-03-19 08:53:10 +0100: burp[431759] Server version: 2.4.0 > 2025-03-19 08:53:11 +0100: burp[431759] nocsr ok > 2025-03-19 08:53:11 +0100: burp[431759] SSL is using cipher: > TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any > Enc=AESGCM(256) Mac=AEAD > > 2025-03-19 08:53:11 +0100: burp[431759] extra_comms_begin ok:autoupgrade:incexc:orig_client:uname:failover:vss_restore:regex_icase:counters_json:msg:csetproto:rshash=blake2:seed: > 2025-03-19 08:53:11 +0100: burp[431759] Using protocol=1 > 2025-03-19 08:53:11 +0100: burp[431759] Doing restore 0:/etc > 2025-03-19 08:53:11 +0100: burp[431759] Doing restore confirmed > 2025-03-19 08:53:11 +0100: burp[431759] Directory: '/blah/recupe/' > > 2025-03-19 08:51:51 +0100: burp[431248] Decryption failure at the end. > 2025-03-19 08:51:51 +0100: burp[431248] transfer file returning: -1 > 2025-03-19 08:51:51 +0100: burp[431248] WARNING: Could not transfer file in: > /blah/recupe/etc. > 2025-03-19 08:51:54 +0100: burp[431248] unexpected command in > restore_interrupt(): c:000A:restoreend > 2025-03-19 08:51:54 +0100: burp[431248] restore_file error > > > I have the same error if i try to restore from an other machine of the same > OS/Version of dead server > > > Any help and pointer greatly appreciated. Hello, Sorry that you are having troubles. It seems strange that it is talking about a file with a name that looks like it's a directory (/etc). I'm wondering whether it is finding any actual files in the manifest? Does listing instead of restoring show the files that you expect? sudo burp -c restauration.conf -a l -r /etc You could also try a verify command: sudo burp -c restauration.conf -a v -r /etc Also, I am wondering whether you are trying to restore a Windows backup onto a linux machine (or vice versa)? Linux backups have no encrypted data to restore for directories, but Windows backups do. |
From: Thomas C. <th...@op...> - 2025-03-19 08:15:25
|
Hello, Trying to restore crypted burp backups from a crashed server I have first restored (from another backup) the /etc/burp of dead server So i am using the same configuration files and certificates of server, including the encryption_password I have first got the error "EVP_CipherInit_ex failed" and fixed it by enabling legacy algo in openssl.cnf but now i get an error : sudo rm -fr recupe ; sudo burp -v -c restauration.conf -a r -r /etc -d recupe 2025-03-19 08:53:10 +0100: burp[431759] No backup specified. Using the most recent. 2025-03-19 08:53:10 +0100: burp[431759] Connecting to backup_serveur:4971 2025-03-19 08:53:10 +0100: burp[431759] auth ok 2025-03-19 08:53:10 +0100: burp[431759] Server version: 2.4.0 2025-03-19 08:53:11 +0100: burp[431759] nocsr ok 2025-03-19 08:53:11 +0100: burp[431759] SSL is using cipher: TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD 2025-03-19 08:53:11 +0100: burp[431759] extra_comms_begin ok:autoupgrade:incexc:orig_client:uname:failover:vss_restore:regex_icase:counters_json:msg:csetproto:rshash=blake2:seed: 2025-03-19 08:53:11 +0100: burp[431759] Using protocol=1 2025-03-19 08:53:11 +0100: burp[431759] Doing restore 0:/etc 2025-03-19 08:53:11 +0100: burp[431759] Doing restore confirmed 2025-03-19 08:53:11 +0100: burp[431759] Directory: '/blah/recupe/' 2025-03-19 08:51:51 +0100: burp[431248] Decryption failure at the end. 2025-03-19 08:51:51 +0100: burp[431248] transfer file returning: -1 2025-03-19 08:51:51 +0100: burp[431248] WARNING: Could not transfer file in: /blah/recupe/etc. 2025-03-19 08:51:54 +0100: burp[431248] unexpected command in restore_interrupt(): c:000A:restoreend 2025-03-19 08:51:54 +0100: burp[431248] restore_file error I have the same error if i try to restore from an other machine of the same OS/Version of dead server Any help and pointer greatly appreciated. -- Thomas Constans |
From: Koen D. <koe...@gm...> - 2024-12-13 22:03:13
|
Hi, The friendly archive provided me with the two earlier threads mentioned below.. I became a bit wiser but still can't solve this puzzle. Has anyone already succeeded in doing so? I have the following puzzles pieces. manifest (redacted): t001At/home/kd/texten/test.txt r004AQME zh0v IHt B Po Po A V2 BAA I BnOR0J BSSygR BnFNjk A A J C -Dg90a/+KfZ A y0019/home/kd/texten/test.txt x00251398:53c099dfe902265aec1e918bbedf90d1 So -Dg90a/+KfZ seems to be the base64 encoded salt. Base64decode.org translates that to ø8=ѯþ)ö in ISO-8859-1 encoding. Using a hex editor, I think this translates into F8383DD1AFFE29F6 in hex. (as requested by openssl: -S val Salt, in hex) Then I try: openssl enc -d -pbkdf2 -aes-256-cbc -S F8383DD1AFFE29F6 -in test.txt -out un_encrypted.data Which results in: enter AES-256-CBC decryption password: bad decrypt 40F73ABB527F0000:error:1C800064:Provider routines:ossl_cipher_unpadblock:bad decrypt:../providers/implementations/ciphers/ciphercommon_block.c:129: Same result when leaving out -pbkdf2 Same result when using a key file with -k Same result also when using ASCII for decoding the salt. Thanks for any help! K https://sourceforge.net/p/burp/mailman/burp-users/thread/20180715135815.u2xzwi3t2ioq2cco%40mail.ziirish.info/#msg36368419 https://sourceforge.net/p/burp/mailman/burp-users/thread/CACFcbG_kfXr1%2Ba7k-ugZ17CZQXzspZU_R1C9mNq-kLW6-pU62w%40mail.gmail.com/#msg36916801 |
From: <bu...@on...> - 2024-11-15 10:29:53
|
Regex, bro. 'session-*' means 'session' or 'session-' or 'session--' and so on. 14.11.24 20:27, Nigel Reed via Burp-users: > > Maybe I’m misunderstanding… > > include = / > > exclude = /var/lib/mysql/* > > exclude = /news/spool > > exclude = /zpool* > > exclude = /swapfile > > exclude = /dev > > exclude = /var/nfs > > exclude = /var/www/pnews/cache > > exclude_regex = /home/*/\.php/session-*/* > > exclude = /export > > The main thing is the exclusion of /home/*/.php/session-*/* > > For example, I had over 2 million sess_ files in > /home/family/.php/session-family/ > > But the exclusion doesn’t seem to be working. > > What am I doing wrong here? > > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users |
From: Graham K. <gr...@gr...> - 2024-11-15 03:20:42
|
On Thu, Nov 14, 2024 at 07:27:08PM +0000, Nigel Reed via Burp-users wrote: > Maybe I’m misunderstanding… > > > > include = / > > exclude = /var/lib/mysql/* > > exclude = /news/spool > > exclude = /zpool* > > exclude = /swapfile > > exclude = /dev > > exclude = /var/nfs > > exclude = /var/www/pnews/cache > > exclude_regex = /home/*/\.php/session-*/* > > exclude = /export > > > > The main thing is the exclusion of /home/*/.php/session-*/* > > > > For example, I had over 2 million sess_ files in > /home/family/.php/session-family/ > > > > But the exclusion doesn’t seem to be working. > > > > What am I doing wrong here? My best guess without trying to debug it manually is that you are using glob-like syntax, rather than regex syntax: exclude_regex = /home/*/\.php/session-*/* In regular expressions, a '*' means zero or many occurrences of the preceeding character. That means, for example, /session-*/ will not match /session-123/. Maybe try something like: exclude_regex = /home/.*/\.php/session-.* |
From: Benedikt H. <tic...@gm...> - 2024-11-14 23:43:28
|
did ypu try the same without blanks around the "=" ? Does the server override what's in the client's configuration (eg by including some incexc.conf file? Best, Ben Nigel Reed via Burp-users <bur...@li...> schrieb am Fr., 15. Nov. 2024, 00:03: > Maybe I’m misunderstanding… > > > > include = / > > exclude = /var/lib/mysql/* > > exclude = /news/spool > > exclude = /zpool* > > exclude = /swapfile > > exclude = /dev > > exclude = /var/nfs > > exclude = /var/www/pnews/cache > > exclude_regex = /home/*/\.php/session-*/* > > exclude = /export > > > > The main thing is the exclusion of /home/*/.php/session-*/* > > > > For example, I had over 2 million sess_ files in > /home/family/.php/session-family/ > > > > But the exclusion doesn’t seem to be working. > > > > What am I doing wrong here? > > > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users > |
From: Nigel R. <ni...@ni...> - 2024-11-14 23:02:20
|
Maybe I'm misunderstanding... include = / exclude = /var/lib/mysql/* exclude = /news/spool exclude = /zpool* exclude = /swapfile exclude = /dev exclude = /var/nfs exclude = /var/www/pnews/cache exclude_regex = /home/*/\.php/session-*/* exclude = /export The main thing is the exclusion of /home/*/.php/session-*/* For example, I had over 2 million sess_ files in /home/family/.php/session-family/ But the exclusion doesn't seem to be working. What am I doing wrong here? |
From: Graham K. <gr...@gr...> - 2024-10-24 21:21:35
|
> Le 22.10.2024 à 00:03, Graham Keeling a écrit : > > On Sat, Oct 19, 2024 at 12:06:55PM +0200, Nicolas Karlen wrote: > > > Hi all, > > > > > > I use burp for backups of my computer and my server on Linux. > > > I really like burp and I would like to use it also for backups of websites > > > of clients that are not hosted on my premises. They are mostly shared > > > hosting and therefore do not have access to a burp installation. > > > > > > The vast majority of the time, I have an ssh access. So I think I will set > > > up a logic with a script in pre or post backup using something like > > > rsync -avzH --delete-after --delay-updates --compare-dest > > > > > > So this is different from the example script > > > "https://github.com/grke/burp/blob/master/configs/server/offsite-backup". > > > This is the server that has a local burp installation and that will fetch > > > the content of the remote site to make incremental backups with burp > > > afterwards. > > > What do you think would be the best way to set up a backup this way? > > > > > > I am particularly wondering about directories. Is there an efficient way to > > > avoid creating a temporary directory and save space by using the burp backup > > > directories directly? > > > > > > Your ideas are welcome. > > > > > > Best, Nicolas > > Hello, > > > > Thank you for your kind words. > > > > I am not 100% sure what you mean, but I think you want to rsync some remote > > data to your local server, then use burp on your local server to make backups > > of the local rsynced data. > > I think this will work, but I have never tried it. If I were to try it, I > > would probably > > *) have a local burp client for each remote host > > *) add a "backup_script_pre" script containing the rsync command > > *) configure the burp clients with the script and "include" the rsync > > target directory to be backed up > > > > Sorry, it won't work for rsync and burp to both share the same target > > directories as rsync will overwrite things that burp wants to manage, and > > therefore backups will break. > Hello, > > Thank you for your answer Graham. > > I finally tried a static build of Burp as a client and I added 2 bash > scripts that take care of saving and restoring the databases that I added to > the burp folder. It works well on the remote hosting. > > I will try on other hostings, I am not sure if it works in most cases. > > For cases where it would not work, do you think burp can backup a sshfs > mount (mount a directory via ssh) ? > > I think about something like pre and post scripts to mount / umount a remote > directory. > > Good day, > Nicolas Hello, I don't like the idea of backing up network mounts because they may not always be up, and may also break in peculiar ways without proper errors being returned to burp. Having said that, burp will happily try to do what you tell it and if your mount is reliable, you might have success. |
From: Nicolas K. <nic...@gm...> - 2024-10-24 17:26:10
|
Hello, Thank you for your answer Graham. I finally tried a static build of Burp as a client and I added 2 bash scripts that take care of saving and restoring the databases that I added to the burp folder. It works well on the remote hosting. I will try on other hostings, I am not sure if it works in most cases. For cases where it would not work, do you think burp can backup a sshfs mount (mount a directory via ssh) ? I think about something like pre and post scripts to mount / umount a remote directory. Good day, Nicolas Le 22.10.2024 à 00:03, Graham Keeling a écrit : > On Sat, Oct 19, 2024 at 12:06:55PM +0200, Nicolas Karlen wrote: >> Hi all, >> >> I use burp for backups of my computer and my server on Linux. >> I really like burp and I would like to use it also for backups of websites >> of clients that are not hosted on my premises. They are mostly shared >> hosting and therefore do not have access to a burp installation. >> >> The vast majority of the time, I have an ssh access. So I think I will set >> up a logic with a script in pre or post backup using something like >> rsync -avzH --delete-after --delay-updates --compare-dest >> >> So this is different from the example script >> "https://github.com/grke/burp/blob/master/configs/server/offsite-backup". >> This is the server that has a local burp installation and that will fetch >> the content of the remote site to make incremental backups with burp >> afterwards. >> What do you think would be the best way to set up a backup this way? >> >> I am particularly wondering about directories. Is there an efficient way to >> avoid creating a temporary directory and save space by using the burp backup >> directories directly? >> >> Your ideas are welcome. >> >> Best, Nicolas > Hello, > > Thank you for your kind words. > > I am not 100% sure what you mean, but I think you want to rsync some remote > data to your local server, then use burp on your local server to make backups > of the local rsynced data. > I think this will work, but I have never tried it. If I were to try it, I > would probably > *) have a local burp client for each remote host > *) add a "backup_script_pre" script containing the rsync command > *) configure the burp clients with the script and "include" the rsync > target directory to be backed up > > Sorry, it won't work for rsync and burp to both share the same target > directories as rsync will overwrite things that burp wants to manage, and > therefore backups will break. > > > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users |