Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > de.comm.software.crosspoint > #3975 > unrolled thread
| Started by | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| First post | 2026-01-01 09:55 +0200 |
| Last post | 2026-01-10 01:07 +0100 |
| Articles | 20 on this page of 29 — 6 participants |
Back to article view | Back to de.comm.software.crosspoint
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-01 09:55 +0200
Re: pgp anyone? "Gunter" <gunter.sandner@googlemail.com> - 2026-01-01 17:59 +0100
Re: pgp anyone? "Martin Wodrich" <martin@martinwodrich.de> - 2026-01-05 18:06 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-05 13:38 +0200
Re: pgp anyone? "Martin Wodrich" <martin@martinwodrich.de> - 2026-01-06 15:25 +0100
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-06 21:10 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-06 19:36 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-08 11:31 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-08 08:21 +0200
Re: pgp anyone? "AugustA" <nospam@nospam.net> - 2026-01-09 18:56 -0500
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-10 01:17 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-09 21:18 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-10 11:29 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-10 08:37 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-10 23:04 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-11 19:34 +0200
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-11 19:55 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-08 15:49 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-08 18:24 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-09 12:17 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-09 08:02 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-09 14:47 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-09 09:00 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-09 16:11 +0100
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-09 16:15 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-09 13:09 +0200
Re: pgp anyone? Thomas Barghahn <Th.Barghahn@t-online.de> - 2026-01-09 20:27 +0100
pgp anyone? August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> - 2026-01-09 15:23 +0200
Re: pgp anyone? "Thomas Barghahn" <Th.Barghahn@t-online.de> - 2026-01-10 01:07 +0100
Page 1 of 2 [1] 2 Next page →
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-01 09:55 +0200 |
| Subject | pgp anyone? |
| Message-ID | <671398913@f1.n221.z2.fidonet.fi> |
Hello gunter.sandner # googlemail.com! Another matter I have been revisiting: how to encrypt a message, but my attempts have been failing. I have defined several functions in the Tools menu: ÚÄ Tools Menu ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Menu Program $FILE S W L A Mem ³ ³ 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer û ³ ³ 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer û ³ ³ 3 gnupg decrypt gpg -d $FILE w/o header û ³ ³ 4 GPG Verify msg gpg --verify $FILE Puffer û ³ ³ 5 ³ 1 and 2 do not seem to work. But 3 and 4 do. What am I doing wrong? Do 1 and 2 need the gpg -o parameter? And if so, what should those lines look like? -- ../|ug
[toc] | [next] | [standalone]
| From | "Gunter" <gunter.sandner@googlemail.com> |
|---|---|
| Date | 2026-01-01 17:59 +0100 |
| Message-ID | <HG0zP$$QyIB@gunter.eternal-september.org> |
| In reply to | #3975 |
Hallo August! > I have defined several functions in the Tools menu: > │ 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer √ │ > │ 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer √ │ > │ 3 gnupg decrypt gpg -d $FILE w/o header √ │ > │ 4 GPG Verify msg gpg --verify $FILE Puffer √ │ > 1 and 2 do not seem to work. > But 3 and 4 do. > What am I doing wrong? > Do 1 and 2 need the gpg -o parameter? And if so, what should > those lines look like? I simply don't know. I haven't used PGP for years and it's currently way out of my focus, sorry... Ciao Gunter
[toc] | [prev] | [next] | [standalone]
| From | "Martin Wodrich" <martin@martinwodrich.de> |
|---|---|
| Date | 2026-01-05 18:06 +0100 |
| Message-ID | <HGGCHXUJZCB@solani.martinwodrich.de> |
| In reply to | #3977 |
Gunter schrieb: > Hallo August! >> I have defined several functions in the Tools menu: >> │ 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer √ │ >> │ 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer √ │ >> │ 3 gnupg decrypt gpg -d $FILE w/o header √ │ >> │ 4 GPG Verify msg gpg --verify $FILE Puffer √ │ >> 1 and 2 do not seem to work. >> But 3 and 4 do. >> What am I doing wrong? >> Do 1 and 2 need the gpg -o parameter? And if so, what should >> those lines look like? > I simply don't know. I haven't used PGP for years and it's currently way > out of my focus, sorry... PGP in XP is not working since pgp 2.6.x is out of use. GPG should work, but no one tested this. -- Mit freundlichen Gruessen, Martin Wodrich
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-05 13:38 +0200 |
| Message-ID | <673509101@f1.n221.z2.fidonet.fi> |
| In reply to | #3991 |
Hello martin # martinwodrich.de! MW> PGP in XP is not working since pgp 2.6.x is out of use. So.. the code makes calls using "pgp" hardcoded? Why not simply replace "pgp" with "gpg" in the source? MW> GPG should work, but no one tested this. These work: Message ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ PGP.. ³ ³ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ 1.³ Decode message ³ 1.³ Test signature ³ 1.ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ And I'm using: H:\>gpg --version gpg (GnuPG) 2.2.19 libgcrypt 1.8.5 I'm just not sure how to use the $ASK and $FILE variables in the Tools menu to make my own "gpg -sea -r " command tool. -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Martin Wodrich" <martin@martinwodrich.de> |
|---|---|
| Date | 2026-01-06 15:25 +0100 |
| Message-ID | <HGKCJue3ZCB@solani.martinwodrich.de> |
| In reply to | #3992 |
August Abolins schrieb: > Hello martin # martinwodrich.de! MW>> PGP in XP is not working since pgp 2.6.x is out of use. > So.. the code makes calls using "pgp" hardcoded? No, there is a config option: ┌─ PGP-Einstellungen ──────────────────────────────┐ │ │ │ PGP-Version GnuPG ↓ │ │ ┌───────┐ │ │ [ ] PGP-U│ 2.6.x │ung │ │ │ 5.x │ │ │ [ ] PGP-R│ 6.5.x │ übergehen │ │ [ ] Warte│ GnuPG │tendruck nach PGP-Aufruf │ │ [ ] Logfi└───────┘tomatische Aktionen │ │ │ │ [x] Keys aus PMs automatisch einlesen │ │ [ ] Keys aus AMs automatisch einlesen │ │ │ │ User-ID martin@martinwodrich.de │ │ │ │ GPG-Optionen --compress-algo 1 --cipher-algo►↓ │ │ │ │ │ │ │ └─────────────────────────────────────────── [F2] ─┘ > Why not simply replace "pgp" with "gpg" in the source? No, just set up GnuPG and use it. PGP-Version 2.6.x is the old PGP. PGP-Version GnuPG means gpg. PGP-Version 5.x and 6.5.x no one knows. -- Mit freundlichen Gruessen, Martin Wodrich
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-06 21:10 +0100 |
| Message-ID | <b3cb.11bb0.dcsc.83oxp@barghahn-online.de> |
| In reply to | #3975 |
*August Abolins* meinte: > > [...] > > What am I doing wrong? Can you tell us what your goal is? Do you want to reply to encrypted emails and also create encrypted emails yourself using GPG? OXP can encrypt and decrypt emails automatically with the correct settings. So you don't need any additional tools like the ones you presented here. Thomas -- == S E N D E Z E I T ================ + DATUM : Dienstag, 06. Januar 2026 + UHRZEIT: 21:10:24 UHR (MEZ) == +++ Heilige Drei Könige +++ ======
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-06 19:36 +0200 |
| Message-ID | <674037901@f1.n221.z2.fidonet.fi> |
| In reply to | #4000 |
Hello Th.Barghahn # gmx.de! ** On Tuesday 06.01.26 - 21:10, Th.Barghahn # gmx.de wrote to All: TB> Can you tell us what your goal is? I want to send netmail/email encrypted. TB> Do you want to reply to encrypted emails and also create TB> encrypted emails yourself using GPG? YES! Basically, I notice that OpenXP decrypts a message fine. And, once it is decrypted, it stays decrypted. So.. there is no need to specifically "reply to encrypted" messages since they will be decrypted by then. TB> OXP can encrypt and decrypt emails automatically with the TB> correct settings. So you don't need any additional tools TB> like the ones you presented here. That sounds wonderful. What needs to be done? -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-08 11:31 +0100 |
| Message-ID | <b3cd.93f2.dcsc.84oxp@barghahn-online.de> |
| In reply to | #4001 |
*August Abolins* meinte: TB>> OXP can encrypt and decrypt emails automatically with the TB>> correct settings. So you don't need any additional tools TB>> like the ones you presented here. > That sounds wonderful. What needs to be done? To avoid any misunderstandings: OXP only supports "gpg/inline"! OXP does not support "gpg/mime", which is used and generated by modern email clients! Your settings are almost identical to mine. Also check your settings for the relevant email addresses: [TAB] => Spezial => PW <https://barghahn-online.de/Pictures/oxp_tab_pw.png> Thomas -- == S E N D E Z E I T =================================== + DATUM : Donnerstag, 08. Januar 2026 + UHRZEIT: 11:31:14 UHR (MEZ) == Heute: Internationaler Tag des Maschinenschreibens ==
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-08 08:21 +0200 |
| Message-ID | <675090789@f1.n221.z2.fidonet.fi> |
| In reply to | #4002 |
Hello Th.Barghahn # gmx.de! ** On Thursday 08.01.26 - 11:31, Th.Barghahn # gmx.de wrote to All: TB> To avoid any misunderstandings: OXP only supports "gpg/inline"! TB> OXP does not support "gpg/mime", which is used and generated by modern TB> email clients! That is no problem. Inline is quite fine. That is how I was doing it manually - creating the pgp block and reediting the outgoing message by dropping in the new block. TB> Your settings are almost identical to mine. TB> Also check your settings for the relevant email addresses: TB> [TAB] => Spezial => PW TB> <https://barghahn-online.de/Pictures/oxp_tab_pw.png> Now.. THAT setting I was not aware of! ÚÄ a#### @ #######.ca ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ³ ³ Password _______________________________ ³ ³ ³ ³ Crypt method PGP ³ ³ ³ ³ [x] Default: Crypt ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Enter the password here with which messages to and º º from the selected user can be coded. You can decide º º each time when you send a message, whether to code it º º or not. º º º º The general rule is: the longer the password, º º the more secure the encryption. º So, it sounds like the PW is optional, and I willbe prompted for it if that field is blank? I am not sure what that password that needs to be. Is it supposed to be my private key password? [time elapses..] OK.. I tried it without a PW and the message went out in the clear. When I entered a PW in the Above settings, and tried again, I got this: ÚÄ Error ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ³ ³ Encoding/signing was not successful. ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Surely there are other settings required to get OXP to enrypt an outgoing message? -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "AugustA" <nospam@nospam.net> |
|---|---|
| Date | 2026-01-09 18:56 -0500 |
| Message-ID | <HGYVpwRxEcB@nospam> |
| In reply to | #4002 |
Hello Th.Barghahn! ** On Thursday 08.01.26 - 11:31, Th.Barghahn wrote to : > Your settings are almost identical to mine. > Also check your settings for the relevant email addresses: > [TAB] => Spezial => PW > <https://barghahn-online.de/Pictures/oxp_tab_pw.png> So.. WHAT needs to be placed in the "Password _______" line? Is that optional? When I leave it blank, and set the other parameter to "PGP" and "[x] Crypt" is set, like this.. ┌─ arnold @ kolico.ca ───────────────────── │ │ Password │ │ Crypt method PGP ↓ │ │ [x] Default: Crypt │ └────────────────────────────────────────── ..a "P" shows up next to the person's email address: √ P ~ 1 sveiks a#####@#####.ca Then, just before I save it, I see this: ┌─ Private message ──────────────────────────────────────── │ │ To: a#####@#####.ca │ │ Subject TEST, FRI 6:50p │ │ Server sveiks Code: PGP │ │ Size 71 Bytes Copies: none │ │ Send... Change... │ ►Yes◄ No Internal Special Subj. Server Code └────────────────────────────────────────────────────────── Then, after I save it, the Sending queue looks like this: ■ +!c 71 09.01.26 arnold@kolico.ca sveiks TEST, FRI 6:50p So.. I would assume that the "c" at the far left means that the message is supposed to be encrypted? But.. I get no gpg prompts to do that, and the message sits in-the-clear - not encrypted. So.. maybe the Linux version does things right, but clearly it's not working in the Windows version. -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-10 01:17 +0100 |
| Message-ID | <b3cf.412.dcsc.92oxp@barghahn-online.de> |
| In reply to | #4018 |
*AugustA* meinte: > Then, just before I save it, I see this: > ┌─ Private message ──────────────────────────────────────── > Then, after I save it, the Sending queue looks like this: > ■ +!c 71 09.01.26 arnold@kolico.ca sveiks TEST, FRI 6:50p That's how it should be! > So.. I would assume that the "c" at the far left means that the > message is supposed to be encrypted? YES! Exactly! :-) Thomas -- == S E N D E Z E I T ======================= + DATUM : Samstag, 10. Januar 2026 + UHRZEIT: 01:17:22 UHR (MEZ) == Heute: Bundesweiter Tag der Blockflöte ==
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-09 21:18 +0200 |
| Message-ID | <675610998@f1.n221.z2.fidonet.fi> |
| In reply to | #4020 |
Hello Th.Barghahn # gmx.de! >> So.. I would assume that the "c" at the far left means that >> the message is supposed to be encrypted? TB> YES! Exactly! :-) SO.. after some monitoring of the new files that openxp creates, I noticed some *new* #####.$$$ files in the TEMP directory. Indeed, I noticed that one of the recent ones had the PGP BLOCK type. That seemed promising. Decrypting it manually proved to be the right message. I did not realize that any ####.$$$ file was being created, and therefore I assumed that the original unencrypted message that I saw in my UNSENT list was not encrypted! It turns out that the encrypted message *DID* get sent. So.. the important thing is to select "[x] Crypt" for the specific email recipient, and that "PGP" is selected too. And, as you nicely illustrated in your Step_N images, signing of that message works as expected too. However, I wonder where the signed block is stored? Which TEMP is it? -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-10 11:29 +0100 |
| Message-ID | <b3cf.9391.dcsc.93oxp@barghahn-online.de> |
| In reply to | #4021 |
*August Abolins* meinte: > So.. the important thing is to select "[x] Crypt" for the > specific email recipient, and that "PGP" is selected too. > And, as you nicely illustrated in your Step_N images, signing > of that message works as expected too. However, I wonder > where the signed block is stored? Which TEMP is it? In the case of PGP/inline, the signature is not stored in a separate TEMP file. The entire signed content is the block between: -----BEGIN PGP MESSAGE----- [...] -----END PGP MESSAGE----- That block already contains the signed data and the OpenPGP signature packet. So there is no additional file — everything is embedded directly in the message body. See: RFC 4880 – OpenPGP Message Format and RFC 9580 – OpenPGP (2024) Thank you for the nice discussion and have fun with encryption and signing in OpenXP! :-) Thomas -- == S E N D E Z E I T ======================= + DATUM : Samstag, 10. Januar 2026 + UHRZEIT: 11:29:37 UHR (MEZ) == Heute: Bundesweiter Tag der Blockflöte ==
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-10 08:37 +0200 |
| Message-ID | <676136523@f1.n221.z2.fidonet.fi> |
| In reply to | #4022 |
Hello Th.Barghahn # gmx.de!
** On Saturday 10.01.26 - 11:29, Th.Barghahn # gmx.de wrote to All:
TB> In the case of PGP/inline, the signature is not stored in
TB> a separate TEMP file. The entire signed content is the
TB> block between:
TB> -----BEGIN PGP MESSAGE-----
TB> [...]
TB> -----END PGP MESSAGE-----
TB> That block already contains the signed data and the
TB> OpenPGP signature packet. So there is no additional file
TB> ± everything is embedded directly in the message body.
Ah.. I should have noticed the "valid signature" when I tested
the ####.$$$ temp file.
Thx.
TB> Thank you for the nice discussion and have fun with
TB> encryption and signing in OpenXP! :-)
Yes.. that went wel.. Thx for your interest to work through the
matter. :)
I have recently received mime-type email from someone. OpenXP
can't seem to handle that on its own. Basically, the messages
seem to arrive in base64.
Eg.
Content-Disposition: inline
This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)
--2wErROdFz89KWACh58u=_36ptLjUNwMbIq
Content-Type: application/pgp-encrypted
Content-Transfer-Encoding: base64
Content-Disposition: attachment
Content-Description: PGP/MIME version identification
VmVyc2lvbjogMQ0KDQo=
--2wErROdFz89KWACh58u=_36ptLjUNwMbIq
Content-Type: application/octet-stream;
name="encrypted.asc"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="encrypted.asc"
Content-Description: OpenPGP encrypted message
LS0tLS1CRUdJTiBQR1AgTUVTU0FHRS0tLS0tDQoNCmhRRU1BMWc3S2ExcDBKbW
VFZyb2dlbUJlaXNBMlNqdjA1dDlKRlI3QldtUSthUmNKK0M2QmcNClNzVzczVT
[...]
OPX can show me the PGP BLOCK of the encrypted.asc file, which
it saves to a temporary external file in the FILES dir, then I
can drop to the cmdline and execute "gpg -d [FILE]" ..and I
can view the message onscreen.
Do you have ready-made macros or a Tools script-line that you
can tell me about that will handle mime-type?
--
../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-10 23:04 +0100 |
| Message-ID | <b3cf.1367c.dcsc.94oxp@barghahn-online.de> |
| In reply to | #4023 |
*August Abolins* meinte: > OPX can show me the PGP BLOCK of the encrypted.asc file, which > it saves to a temporary external file in the FILES dir, then I > can drop to the cmdline and execute "gpg -d [FILE]" ..and I > can view the message onscreen. > Do you have ready-made macros or a Tools script-line that you > can tell me about that will handle mime-type? In this case, you need "Kleopatra" *and* a "base64 decoder" OR: own gpg tools *and* a "base64 decoder". See my procedure: ----------------- Step 1: select the email to be decrypted <https://barghahn-online.de/Pictures/oxp/Step_1_decrypt.png> Step 2: select "File ... encrypted.asc" <https://barghahn-online.de/Pictures/oxp/Step_2_decrypt.png> Step 3: copy/save the entire part: -----BEGIN PGP MESSAGE----- [...] -----END PGP MESSAGE----- to the clipboard (Linux) => Result File: ~/.openxp/temp/.openxp.clipboard.1000 in File: "out.asc" <https://barghahn-online.de/Pictures/oxp/Step_3_decrypt.png> STEP 4.1: +++ with "Kleopatra" - START +++ | | Step 4.1.1: | Tools => Clipboard => encrypt/decrypt | <https://barghahn-online.de/Pictures/oxp/Step_4_1_1_decrypt.png> | | Step 4.1.2: | Enter passphrase | <https://barghahn-online.de/Pictures/oxp/Step_4_1_2_decrypt.png> | | Step 4.1.3: | check Sig and close "Kleopatra" | <https://barghahn-online.de/Pictures/oxp/Step_4_1_3_decrypt.png> | +++ with "Kleopatra" - END +++ STEP 4.2: +++ w/o "Kleopatra" - START +++ | | || !! Create Tools-Menu !! | || Menu display: decr. gpg/mime | || <https://barghahn-online.de/Pictures/oxp/Step_4_2_decrypt.png> | || | || Linux: | || ------ | || Program name: gpg -d -o ~/.openxp/temp/input.txt ~/.openxp/temp/.openxp.clipboard.1000 | || | || Windows11: | || ---------- | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt d:\my_programs\open_xp\files\out.txt | | Step 4.2.1: | Tools => decr. gpg/mime | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png> | | Step 4.2.2: | Enter passphrase | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png> | +++ w/o "Kleopatra" - END +++ Step 5: open the file "input.txt" in your preferred editor and copy the "base64 part" to the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png> Step 6: open your "base64 decoder"[1] and paste from the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png> Step 7: decode the base64 part <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png> Ready! :-) [1] Copyright by Thomas Barghahn ;-) Thomas -- == S E N D E Z E I T ======================= + DATUM : Samstag, 10. Januar 2026 + UHRZEIT: 23:04:44 UHR (MEZ) == Heute: Bundesweiter Tag der Blockflöte ==
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-11 19:34 +0200 |
| Message-ID | <676665569@f1.n221.z2.fidonet.fi> |
| In reply to | #4024 |
Hello Th.Barghahn # gmx.de!
TB> STEP 4.2:
TB> +++ w/o "Kleopatra" - START +++
TB> |
TB> | || !! Create Tools-Menu !!
TB> | || Menu display: decr. gpg/mime
TB> | || <https://barghahn-online.de/Pictures/oxp/Step_4_2_decrypt.png>
TB> | ||
TB> | || Windows11:
TB> | || ----------
TB> | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt
TB> d:\my_programs\open_xp\files\out.txt |
My dilema.. How do I know what file OXP uses as the temp file
after saving a message or seletion to Clipboard?
For example, I saved this message to Clipboard and noticed a
new temp file that contains the content:
3382 2026-01-11 19:24:04.406250000 TEMP/1892.$$$
But.. if that file name is always different, how can I build
the proper Program line to use it as imput?
Is the selection to clipboard represented by the $FILE
variable?
TB> | Step 4.2.1:
TB> | Tools => decr. gpg/mime
TB> | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png>
TB> |
TB> | Step 4.2.2:
TB> | Enter passphrase
TB> | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png>
TB> |
TB> +++ w/o "Kleopatra" - END +++
All that helped. Thx!
TB> Step 5:
TB> open the file "input.txt" in your preferred editor and copy the
TB> "base64 part" to the clipboard.
TB> <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png>
TB> Step 6:
TB> open your "base64 decoder"[1] and paste from the clipboard.
TB> <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png>
TB> Step 7:
TB> decode the base64 part
TB> <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png>
I could prabably build the decrypt base64 tool with:
"busybox base64 -d [FILE]
--
../|ug
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-11 19:55 +0200 |
| Message-ID | <676665737@f1.n221.z2.fidonet.fi> |
| In reply to | #4024 |
Hello Th.Barghahn # gmx.de! TB> STEP 4.2: TB> +++ w/o "Kleopatra" - START +++ TB> | TB> | || !! Create Tools-Menu !! TB> | || Menu display: decr. gpg/mime TB> | || Windows11: TB> | || ---------- TB> | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt TB> d:\my_programs\open_xp\files\out.txt | Ok.. So mine should be this? ÚÄ Tools Menu 5 ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ³ ³ Menu display decrypt gpg/mime ³ ³ ³ ³ Program name gpg -d -o de-mime.txt $FILE ³ ³ ³ ³ $FILE-Msg. w/o header [ ] Subject-name ³ ³ ³ ³ [ ] Wait ³ ³ [x] Fullscreen Memory: 600 KBytes ³ ³ [ ] Output to lister ³ ³ [ ] Look for files in AUTOEXEC directory ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ So... I open the message particulars: ÚÄ Message-Part ÄÄÄÄÄÄÄÄÄÄ Lines ÄÄÄÄÄÄÄÄÄÄÄÄ Filename ÄÄ¿ ³ Vorspann 2 ³ ³ Text 2 ³ ³ File (pgp-encrypted) 2 ³ ³ File 52 encrypted.asc ³ ³ Whole Message 79 ³ ³úEXIT ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ..Then, I select the enrypted.asc, and open that up to view, and then copy that clipboard? TB> | Step 4.2.1: TB> | Tools => decr. gpg/mime TB> | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png> TB> | TB> | Step 4.2.2: TB> | Enter passphrase TB> | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png> TB> | TB> +++ w/o "Kleopatra" - END +++ TB> Step 5: TB> open the file "input.txt" in your preferred editor and copy the TB> "base64 part" to the clipboard. TB> <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png> TB> Step 6: TB> open your "base64 decoder"[1] and paste from the clipboard. TB> <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png> TB> Step 7: TB> decode the base64 part TB> <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png> TB> Ready! :-) TB> [1] Copyright by Thomas Barghahn ;-) TB> Thomas TB> -- TB> == S E N D E Z E I T ======================= TB> + DATUM : Samstag, 10. Januar 2026 TB> + UHRZEIT: 23:04:44 UHR (MEZ) TB> == Heute: Bundesweiter Tag der Blockfl”te == TB> -+- TB> + Origin: rbb sglnx - the fidonet nntp junction (2:221/10) -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-08 15:49 +0100 |
| Message-ID | <b3cd.d08c.dcsc.85oxp@barghahn-online.de> |
| In reply to | #3975 |
*August Abolins* meinte: Sorry, August. Before we discuss further details: Which operating system are you using? Which version of gpg/Gpg4Win are you using? Which version of OXP are you using? Thomas -- == S E N D E Z E I T =================================== + DATUM : Donnerstag, 08. Januar 2026 + UHRZEIT: 15:49:48 UHR (MEZ) == Heute: Internationaler Tag des Maschinenschreibens ==
[toc] | [prev] | [next] | [standalone]
| From | August Abolins <August.Abolins@f1.n221.z2.fidonet.fi> |
|---|---|
| Date | 2026-01-08 18:24 +0200 |
| Message-ID | <675092412@f1.n221.z2.fidonet.fi> |
| In reply to | #4004 |
Hello Th.Barghahn # gmx.de! ** On Thursday 08.01.26 - 15:49, Th.Barghahn # gmx.de wrote to All: TB> From: Thomas Barghahn <Th.Barghahn@t-online.de> TB> *August Abolins* meinte: TB> Sorry, August. Before we discuss further details: TB> Which operating system are you using? TB> Which version of gpg/Gpg4Win are you using? TB> Which version of OXP are you using? [1] XP [2] H:\temp>gpg --version gpg (GnuPG) 2.2.19 libgcrypt 1.8.5 [3] ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³Open \\// 5.0.64 (Win32) (c) 1992-1999 Peter Mandrella ³ ³ //\\ XP (c) 2000-2025 OpenXP-Team ³ ³ OpenSSL 1.0.2u 20 Dec 2019 ³ -- ../|ug
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Barghahn" <Th.Barghahn@t-online.de> |
|---|---|
| Date | 2026-01-09 12:17 +0100 |
| Message-ID | <b3ce.9ed8.dcsc.86oxp@barghahn-online.de> |
| In reply to | #4005 |
*August Abolins* meinte: > Hello Th.Barghahn # gmx.de! > ** On Thursday 08.01.26 - 15:49, Th.Barghahn # gmx.de wrote to All: TB>> Which operating system are you using? TB>> Which version of gpg/Gpg4Win are you using? TB>> Which version of OXP are you using? > [1] XP Ok. > [2] H:\temp>gpg --version > gpg (GnuPG) 2.2.19 > libgcrypt 1.8.5 Oh, that version is quite a bit outdated already. ;-) Please install the 'Gpg4Win 4.4.1' package on your Windows XP system. It includes the current version of 'gpg'. The package also contains the latest version of "Kleopatra", which you can use to manage all your keys. You can download Gpg4Win from the following page: <https://www.gpg4win.de/> My versions: | C:\gpg --version | gpg (GnuPG) 2.4.8 | libgcrypt 1.11.1 | Kleopatra 3.3.0 Import all your relevant keys into Kleopatra — that includes your own key pair as well as all public keys you need for encryption and verification. > OpenXP 5.0.64 (Win32) Ok. | --- your M-ID:<news:675090789@f1.n221.z2.fidonet.fi> --- > [...] > So, it sounds like the PW is optional, and I willbe prompted > for it if that field is blank? This input field has no meaning for current gpg versions and should be left empty. > I am not sure what that password that needs to be. Is it > supposed to be my private key password? First, please install GPG4Win with Kleopatra and import all your keys. Then try sending an email with OpenXP. Thomas -- == S E N D E Z E I T =============== + DATUM : Freitag, 09. Januar 2026 + UHRZEIT: 12:17:44 UHR (MEZ) == Heute: Tag der Aprikose =========
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | de.comm.software.crosspoint
csiph-web