Re: 422 Unprocessable Entity

Hello Andrew,

422 means the file doesn’t exist.  29150 doesn’t seem to be a supported
version.  29151 is though.

But, you should at least be on 29200 if not moving to 3 by now.

--
Joel



On Tue, Oct 3, 2023 at 7:36 PM Andrew Pozharsky via Snort-users <
[email protected]> wrote:

> Hello,
>
> Thank you for responding, and I apologize for the miscommunication. I
> substituted <oinkcode> for my actual oinkcode as I wasn’t sure whether such
> information should be kept private. I do have my oinkcode and it is being
> used. I’m currently working on upgrading our Snort version to the latest
> update as our current version is years behind and stopped working around 2
> years ago.
>
> Thanks,
> Andrew Pozharsky
>
>
>
> *From:* Vitalii Serhiiovych Horbatov -X (vhorbato - SOFTSERVE INC at
> Cisco) <[email protected]>
> *Sent:* Tuesday, October 3, 2023 3:12 AM
> *To:* Andrew Pozharsky <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: 422 Unprocessable Entity
>
>
>
> Hi Andrew!
>
> You need to substitute <oinkcode> In configurable link with your oinkcode
> that you can get from snort.org.
> Please check pulledpork README on github or any other manual (
> http://sublimerobots.com/2017/01/snort-2-9-9-x-ubuntu-installing-pulledpork/
> seems good).
>
> Thanks,
> Vitalii!
>
>
>
> *From: *Snort-users <[email protected]> on behalf of
> Andrew Pozharsky via Snort-users <[email protected]>
> *Date: *Sunday, 1 October 2023, 00:31
> *To: *[email protected] <[email protected]>
> *Subject: *[Snort-users] 422 Unprocessable Entity
>
> Hello,
>
> I am attempting to update Pulledpork with a new rule, though when I try to
> update I get:
>
> ** GET
> https://www.snort.org/rules/snortrules-snapshot-29150.tar.gz.md5?oinkcode=<oinkcode>==>
> 422 Unprocessable Entity
>
> Error downloading
> https://www.snort.org/rules/snortrules-snapshot-29150.tar.gz.md5?oinkcode=<oinkcode>:
> 422 Unprocessable Entity [ 422 ]
>
> And in my snort log I observe:
>
>
>
> My company has been using snorts for the past few years though we’ve done
> very little with it. The logs show that this issue started appearing around
> Dec 2020 and it could be that we have something outdated. Our current
> version is v0.7.3 and we do have an active subscription with its
> corresponding oinkcode.
>
> Any help will be appreciated.
>
> Thanks,
> Andrew Pozharsky
>
>
>
>
>
> *Disclaimer*
>
> The information contained in this communication from the sender is
> confidential. It is intended solely for use by the recipient and others
> authorized to receive it. If you are not the recipient, you are hereby
> notified that any disclosure, copying, distribution or taking action in
> relation of the contents of this information is strictly prohibited and may
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance.
> _______________________________________________
> Snort-users mailing list
> [email protected]
> Go to this URL to change user options or unsubscribe:
> https://lists.snort.org/mailman/listinfo/snort-users
>
>         To unsubscribe, send an email to:
>         [email protected]
>
> Please visit http://blog.snort.org to stay current on all the latest
> Snort news!
>
> Please follow these rules:
> https://snort.org/faq/what-is-the-mailing-list-etiquette
>


-- 
Joel Esler

_______________________________________________
Snort-users mailing list
[email protected]
Go to this URL to change user options or unsubscribe:
https://lists.snort.org/mailman/listinfo/snort-users

	To unsubscribe, send an email to:
	[email protected]

Please visit http://blog.snort.org to stay current on all the latest Snort news!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette