I'm trying to develop something on fido and I need to know where to
look at to find the node that originated a message.
Do I have to look at the MSGID or at the PATH? :)
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
I'm trying to develop something on fido and I need to know where to look at find the node that originated a message.
Do I have to look at the MSGID or at the PATH? :)
I'm trying to develop something on fido and I need to know where
to look at find the node that originated a message.
Do I have to look at the MSGID or at the PATH? :)
The PATH.
The PATH.
Many Thank, but now I have to ask how to get the Zone? :)
In the path you have the first node that is the originating node plus all the traversed nodes, but it's without the preceding zone.
So use the origin line:
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
Which should always be present, and/or the header of the mail.
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
Which should always be present, and/or the header of the mail.
The PATH.
Many Thank, but now I have to ask how to get the Zone? :)
In the path you have the first node that is the originating node
plus all the traversed nodes, but it's without the preceding
zone.
That's another reason why you shouldn't use the PATH... ;)
So use the origin line:
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
Which should always be present, and/or the header of the mail.
Many Thanks, what header are you referring to,
all the informations of the headers or an Echo message can be forged.
:)
Many Thanks, what header are you referring to,
That depends where you intercept the messages to get the information.
Is it from the .pkt file or is it already in a message base?
all the informations of the headers or an Echo message can be
forged.
:)
If everything can be forged, your software can't know if some part or
all of the message is forged, so it doesn't have to consider that. And it's not a consideration to not use the header, instead of other parts
of the message. ;)
I'm trying to develop something on fido and I need to know where to look atto find the node that originated a message.
Do I have to look at the MSGID or at the PATH? :)
beforeThat depends where you intercept the messages to get the information.
Is it from the .pkt file or is it already in a message base?
In the between. :)
In HPT you can intercept the single message unpacked from the bundle
the delivery to the message base, there you are in GOD MODE [(c) DOOM]
and you can do all that you want with perl scripts.
If everything can be forged, your software can't know if some part or
all of the message is forged, so it doesn't have to consider that.
And it's not a consideration to not use the header, instead of other
parts of the message. ;)
You're right, but there should be someting that is injected by the main node to know where the message is originated and not forgeable by a user editor (BBS/Point/JAMNNTPD and so on), do you know about something like this?
Are you sure that the first node of the path can be rewritten?
* Origin: ]\/[imac Rebirth Boss Point (6:666/666.6)
Hello Wilfred!
25 Sep 19 15:39, you wrote to me:
The PATH.
Many Thank, but now I have to ask how to get the Zone? :)
In the path you have the first node that is the originating node
plus all the traversed nodes, but it's without the preceding
zone.
That's another reason why you shouldn't use the PATH... ;)
Ok, but:
- The PATH can be cleared
- The MSGID is not mandatory and can be omitted
- The Origin can be forged
- The Headers can be forged
So, how can I determine the originating node of a message? :D
* Origin: ]\/[imac Rebirth Boss Point (6:666/666.6)
Don't ... do ... that ... !!
Then you have to figure out how the header is represented in that intercepted message from HPT.
and you can do all that you want with perl scripts.
'perl'!? You're a masochist! ;)
Well in an echomail message you have 4 possible sources:
Header
MSGID kludge
Origin line
PATH line
If you don't trust any, you could compare the ones that are present.
And if there are inconsistencies report/log/move-to-bad or do whatever
you seem appropriate with it. I don't think it's worth it...
If you're referring to EchoMail, then FTS-4 is the spec (http://ftsc.org/docs/fts-0004.001) and it instructs you to use the
Origin line to determine where a message originated.
NNTPWell in an echomail message you have 4 possible sources:
Header
MSGID kludge
Origin line
PATH line
If you don't trust any, you could compare the ones that are present.
And if there are inconsistencies report/log/move-to-bad or do whatever
you seem appropriate with it. I don't think it's worth it...
Ok, I see that to forge any header you need to have a full editor like golded or msged or similar, with a normal user access like BBS, QWK or
you can't forge these fields.
Well, now I have enough informations and options to choose in.
Well, now I have enough informations and options to choose in.
Well, not really multiple options. You will have to use the Origin
line for the full address. You can only use the others, to verify...
;)
Well, let me dig into and I hope in few time I'll release a nice tool
for the hpt tosser. ;)
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,050 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 46:05:36 |
| Calls: | 236,050 |
| Calls today: | 9 |
| Files: | 60,363 |
| D/L today: |
15,305 files (2,990M bytes) |
| Messages: | 289,538 |
| Posted today: | 6 |